|
Phase-Out Analysis and Lessons Learned
|
|
Project/Task:
Overall
Team Performance Lessons Learned
|
Date:
30 November 2007
|
|
Team Name:
Team
Perfect 10
|
Members:
Ali,
Susan, Ellie, Zack, and Paul
|
|
Subtask
|
What Worked
|
What Didn’t Work
|
Ways to Improve
|
|
Distributed
Work
|
Dividing
Up Tasks – they were evenly distributed
|
Sometimes
the content was inconsistent
|
We
could use templates for content format; we could spend more time working as a
group
|
|
Assembled
Presentations
|
Have
one person in charge of each presentation format; getting group feedback on
presentation before presenting
|
Sometimes
the content format was inconsistent; sometimes group members were late
submitting content
|
We
could use templates for content formats; we could work on submitting content
on time
|
|
Assembled
Wiki
|
Having
one person checking the quality; Having wiki meetings the day before they
were due
|
Content
wasn’t always uploaded at the time of the meeting; format was sometimes
inconsistent
|
We
could set a deadline for uploading wiki content before meeting, so that we
could spend the meeting making the content consistent
|
|
Put
together Project Documentation
|
Having
one person in charge of the documentation for each week; assigning in advance
so that we knew who was responsible each week
|
Not
having a program to create schedules and WBS (until Ali rocked it out)
|
Put
Ali in charge of formatting from the beginning; having access to appropriate
software
|
|
Performed
Presentations
|
Having
the presentations e-mailed to group in advance so that we could prepare individual
work
|
We
always ran out of time (until the last one!)
|
We
could have rehearsed the presentations
|
|
Incorporated
Presentation Feedback into the wiki
|
Some
group members edited content based on feedback
|
Some
group members did not edit content
|
We
could establish a rule for editing content based on the feedback in our team
charter; we could review the feedback in our wiki meetings
|
|
Target Analysis:
How well did the project/team do…
|
|
In achieving goals and meeting project
objectives?
The
group performed well.
|
|
At meeting deadlines and the final
completion date?
We
were on time with overall submittals, but group deadlines were sometimes not
followed.
|
|
At monitoring and staying within project
budget?
We
had no budget, except for coffee at Bollo’s (and Ali and Ellie and Susan each
got parking tickets)
|
|
At communicating with stakeholders?
When
required, we contacted industry professionals and the professor.
|
|
Resources
Assessment: were the allocated resources appropriate, sufficient, and efficiently
used?
The internet was
convenient. At times the previous
team’s wikis lacked appropriate information, and sometimes the assignment
sheets were vague (taking entire class periods to clarify).
|
|
Lessons Learned:
what
are the key lessons that can be applied to future projects?
- Start the project before you think you need to
start
- Rehearse presentations to avoid going over time
- Use templates to show consistency in
presentation and wiki content
- Incorporate presentation feedback to ensure
accuracy of the wiki
- Make sure that we understand the assignment
components and expectations
- Do not park in downtown Blacksburg metered spots
|
