The main goal of lab this week is to determine
which concept your team will pursue for the remainder of the term. Once
this decision is made, your team should organize, allocate resources,
and begin working towards the assembly review and the technical
It is important to have your full team and your instructors participate in the concept
selection process, so it is strongly recommended that you wait until
this week's lab meeting before making a decision. If you feel that you cannot wait until your lab before making a decision, please make arrangements with your instructors so that they can participate in the decision meeting.
Advanced preparation for Lab #7
Read the assembly
model review (October 30 (red, green, blue, and yellow during class) or November 1 (pink, orange, purple, and silver during class)) and technical
review (November 14) descriptions so that you are familiar with
the upcoming milestones.
As a section:
If possible, meet with your section to discuss the mockup
review. What worked well? What did not? How will you do better next
time? If there are additional issues that should be be looked into before deciding on your project direction, work on them prior to the lab meeting.
Prepare a short but informative presentation about your opposite section's two concepts, highlighting strengths, weaknesses,
risks, and open issues. Be sure to work with the opposite section and have their agreement on the key points of your presentation. In addition to summarizing the sketch models and mockups, please try to outline thoughts about key tasks that the team will engage in to carry an idea forward to a product prototype. Remember FNAP!
As a team:
System integrators from both sections should meet to form an agenda
and devise a rational decision process with relevant criteria for
choosing the team's concept. Please read the G'DAY decision process and mediaton framework for selecting your team's product direction and making data-driven decisions. Prepare in advance!
Your team yodas will have been taking the lead on your team
code of values. Yodas will have received an email on Monday, October 14 that explains the process. Your team's draft was submitted on Friday by 9 PM (18th) for feedback from the communications instructions. The final version is due 5 PM Monday of this week. Your code of values will be printed, and it will be presented by your yodas at the start of this week's meeting. This will be discussed during class on Friday the 18th. Submission instructions will be on the home page.
Please email the course instructor your team's final product decision after the lab.
After your decision is made, your team should have a first version Gantt chart and task dependency matrices (or similar visualization that clearly shows milestones, key tasks, and timing) through the assembly review in your team area. Your white board may be used for this schedule.
Recommended Lab #7 Activities
In all remaining labs the two sections will work together. Make a point of intermixing the seating so that sections are not polarized on opposite sides of the room. Decide if the name cards are needed.
Begin with the standard meeting startup.
Your instructors will discuss your mockup review grades in next week's team meeting. They may also choose to defer the review of your design notebooks to next lab.
Your yodas will begin by discussing your team code of values.
Spend up to 20 minutes in total to present the short concept
summaries prepared before lab, reviewing the
team's four ideas and feedback from the mockup presentation. FNAP!
System integrators should propose the decision process they have
developed, and revisions should be made based upon input from the
team. If the sections are different in size, be sure that your decision process is perceived to be fair. It should not be possible for one section to simply out-vote the other. You want to make the best choice regardless of who has worked on an idea.
A Pugh chart or similar rational process should be used to help elucidate and compare the strengths and weaknesses of the concepts relative to your team's project criteria. Think carefully about risks associated with your product concepts and negotiate the product definition for the final alpha prototype.
Focus on the common goal of having the best-possible successful
project, and in making a timely decision so that your team can move
on to the next steps. You should make a choice on the basis of what
is the best option, not on an emotional level. Be willing to change your mind as new information becomes available.
It is hoped that
this experience will help you prepare for times when, as a project
manager, you will need to make critical decisions from a set of
alternatives. Be thorough but do
not belabor the process—begin by checking to see if there is
Be sensitive to team dynamics and focus on the merits of the concepts,
not ownership of the ideas. For example, make statements like: the
idea has significant technical risk rather than your idea
has significant technical risk; the widget fulfills an important
need rather than my widget fulfills an important need.
Paying attention to how things are said can make a significant difference.
Remember that consensus does not mean that every team member has the same opinion about what is the best direction to pursue. Consensus means that all team members agree that the direction has been chosen and that they will fully engage in helping the development effort succeed on the chosen direction.
Once a decision is made, celebrate team buy-in symbolically with
a YoWup! (view the instructions and an actual board meeting YoWup) This is derived from a Japanese tejime gesture symbolizing that all team members fully support the decision and are committed to advancing the project in its chosen direction. To perform the ritual, the team stands, chants Yo Wup! and simultaneously claps on the Wup. Creative interpretation of the chant is encouraged. If the chant is not sufficiently enthusiastic it should be repeated, or the team needs to further reflect on the decision.
Make a plan for the team's next steps (assembly
and technical review)
and allocate responsibilities. Think carefully about the best way
to bring all team members up to speed on the chosen concept and how to utilize your team effectively.
Divide tasks and assign responsibility for design issues that need
to be addressed. Make sure that there is a clear plan of how the product contract
and assembly model will be prepared for the deadline next week. Remember that the in-class assembly presentations are Wednesday and Friday next week.