| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Files spread between Dropbox, Google Drive, Gmail, Slack, and more? Dokkio, a new product from the PBworks team, integrates and organizes them for you. Try it for free today.

View
 

April 26 PM ThinkTank Discussion

Page history last edited by Danny Mittleman 9 years, 10 months ago

 

  1. General Discussion
    1. Enterprise Social Networking - Jimmy Prathan (PM)
      1. This is a test.
    2. 123
    3. Hello
    4. Knock Knock
      1. who is there
    5. I am Dave Hodgson, PM for cloud computing and SAAS chapter
    6. What
    7. Hi this is Daniella Here. My group is working on Virtual Meeting Management Tools and Techniques
    8. Jeeri Reddy - PM Ideation and Brainstorming
    9. Hi -- Ioan Jones. Collaboration in Virtual Worlds
    10. Hi I am Qasim, working on Data & Taxonomy Governance project
    11. My name is Marisha our topic is adoption and diffusion of Groupware
    12. Hi, this is Ann, I'm a PM for Collaboration Theory and Practice
    13. I'm Erik Wallin stand-in PM for the Collaboration Engineering team.
      1. Hi EriK, I'm Ann. PM for collaboration theory and practie. I have a question for u. As some content of my chapter may relate to your chapter, do u include the 7 layers model of collabolation to your chapter?
    14. Alright so what are you guys thinking as far as deliverables
      1. How about a due date for everyones outline
    15. My thoughts for schedule are that tasks should be broken down
    16. I am sitting in for my PM , but we currently creating our outlines and posting them to Wiki.
      1. we did the same
    17. Collaboration Engineering has posted a preliminary outline to the Wiki.
    18. 1. Identify Chapter Outline 2. Distribut work Among team members 3. Delivery from team members from team membeers
      1. 4. Peer Review 1 5. Consolidation 6. Overall review 1 7. Final Review
      2. 8. Presentation
    19. Has anyone set a deadline for their team as to when the outline should be complete.
    20. Cheri Goosby, I am the PM for Virtual Project Management
    21. We planned on filling in the outline with the current chapter text as our next step.
    22. Collaboration in Virtual Worlds has an outline complete
    23. We're starting work on our changes this week
    24. My PM wants our final deadline to be complete by next week along with some research about the topic
      1. Our outline is due next week
    25. Collaboration Engineering had a deadline of last Saturday to build consensus for our chapter outline.
    26. cloud computing and SAAS has completed their outline as well
    27. Hello, I John Wolfram - PM for the Business Case chapter
    28. Can we agree that a chapter outline is the first deliverable?
    29. If we can agree on this, we can set a due date for the outline.
    30. danny talking: I suggest that you may want to divide up into the different tasks and focus in those areas. If one or a few people could assume lead in each area, you might be able to surface a recommended approach for each. I recognize this is tough with a limited voice channel.
    31. Sounds like most groups have the outline complete. How about the end of this week (Fri, 30 April)?
    32. Erik Wallin-Collaboration Engineering: April 30th is fine.
    33. I will have to run this past my team and the PM, as stated before our outline is not due until May 5
    34. John Wolfram - Business Case - April 30 is fine.
    35. Agreed\
    36. Virtual meeting management should have it completed by this sunday
    37. Here is what I came up with
    38. Someone said the outline isn't due til May 5th... is that something Danny established or is that a deadline your team set for itself?
      1. My team
    39. This is what Qasim and Marry came up with: Tasks: Dates: 1. Identify Chapter Outline - 4/29/10 2. Distribut work Among team members 5/3/10 3. Delivery from team members from team members 5/17/10 4. Peer Review 1 5/21/10 5. Consolidation 5/24/10 6. Adjustments 5/30/10 7. Overall review 1 6/2/10 8. Final Review 6/4/10 9. Adjusments 6/7/10 10. Presntation/Submission 6/14/10
      1. This looks about right.
    40. Erik Wallin-Collaboration Engineering: May 5th was an agreed upon due date for a specific team.
    41. Check out Project Managers Weekly Schedule for ideas on how to organize your Project
    42. Outline should be in by Sunday this week (May 1st)?
      1. I beleive you mean Sunday May 2.
    43. Ideation and Brainstorming outline is posed under our tab
    44. Outline due Sunday May 2; is that what we landed on?
      1. I vote "Yes" on this.
      2. yes
    45. Sat or sunday is fine. It should def be this weekend so there is a clear point for all the teams to move forward
    46. Please lets agree to May 2
    47. Ann - Collaboration Theory: Did your outline include 7 layers model of collaboration?
    48. John W - Business Case - Agree
    49. Erik Wallin-Collaboration Engineering: May 2nd is fine.
    50. Ann: Hi Erik, did your outline include 7 layers model of collabolation?
    51. Erik Wallin-Collaboration Engineering: No, we did not cover the 7 layers model in our chapter. We thought that fell more into the theory chapter.
    52. Its a miracle, I got into Think Tank
    53. Erik Wallin-Collaboration Engineering: Our outline is here: http://pm440.pbworks.com/Chapter_2_Final_Outline
    54. cloud computing outline is http://pm440.pbworks.com/Cloud+Computing+and+SAAS+-+Working+copy
    55. Erik Wallin-Collaboration Engineering: Are we done with this discusson?
    56. Has anyone decided on the exact location to post our outlines collectively on PBworks?
    57. Erik, I read your outline, and u mention about the pattern of collaboratio which is included in the 7 layers model of collabolation, so i think this topic should include in your chapter
  2. Interim deliverables
    1. Tasks: Dates: 1. Identify Chapter Outline - 4/29/10 2. Distribut work Among team members 5/3/10 3. Delivery from team members from team members 5/17/10 4. Peer Review 1 5/21/10 5. Consolidation 5/24/10 6. Adjustments 5/30/10 7. Overall review 1 6/2/10 8. Final Review 6/4/10 9. Adjusments 6/7/10 10. Presntation/Submission 6/14/10
      1. this plan looks good. see if there is buy in or need for adjustment -danny
      2. Our last class is 6/7. 6/13 is graduation
      3. this is reasonable
      4. Erik Wallin-Collaboration Engineering: We can work with these dates.
    2. the QU people are suggesting saturday night 5/1 for getting outlines posted. They say: this gives weekend time for outline and also weekend time to react to what is out there. -danny
    3. This make sense.
  3. PBWorks use standards
    1. Marry and I think long as its centralized we should be ok...as far as the standards are confirmed we can agree to disagree
    2. Tollgate review process - Weekly team review and sign-offs
      1. What is a tollgate review?
    3. Repositories should be based on chapter outlines.
    4. Erik Wallin-Collaboration Engineering: Are we creating a Wiki page for each section or are we creating a single Wiki page for the entire chapter?
    5. Its probably easiest if each group posts their outline under their repository, and then go look at the other ones
  4. Reporting Standards
    1. Tollgate review process - Weekly team review and sign-offs+
    2. Is everyone posting copies of meeting notes and meeting agenda's under their project directory in PBWorks?
      1. For now, we have been keeping the agendas and minutes off of PBworks. Google docs is our "working" repo for that right now.
  5. Candidate Schedule
    1. Tasks: Dates: 1. Identify Chapter Outline - 4/29/10 2. Distribut work Among team members 5/3/10 3. Delivery from team members from team members 5/17/10 4. Peer Review 1 5/21/10 5. Consolidation 5/24/10 6. Adjustments 5/30/10 7. Overall review 1 6/2/10 8. Final Review 6/4/10 9. Adjusments 6/7/10 10. Presntation/Submission 6/14/10
  6. Questions for danny about process
    1. My suggestion is to move forward as best you can through the issues in instructions at left. I realize this is a leaderless team and that our process channels are limited. I am homing we can find some value in this process. -danny
  7. Project Managers Weekly Schedule
    1. One section per week with reseach with a few week in the end for catch up
    2. Each person does there own reseach and writes a 2 page paper per week (M-Th). Firdays and the weekend are used to put the section together
    3.  

Comments (0)

You don't have permission to comment on this page.