Team Meeting 6

Last updated: Oct 19, 2020 at 11:28am

Main Team Meeting Objective

The main goal of this week's team meeting is to make sure that a single, clear vision for the product is taking shape, and to ensure that things are coming together for the assembly and product contract presentations on Friday this week. Written assembly review feedback will be received by noon, Saturday.

The assembly materials need to be submitted by midnight, Thursday before the review. This material is posted online for review in advance of the in-class presentations. However, you should continue to refine your design up until your in-class presentation. If you have updated materials, you may resubmit them up until 3PM Friday.

Even though you will be concentrating on the overall architecture design and assembly, you will also still need to be doing physical models, tests and experiments at the same to time validate design details or resolve outstanding risks.

The technical review is coming fast (November 6), so critical parts should be ordered ASAP to ensure that they are received on-time. When ordering critical parts, please order more than you need! It is always a good idea to have a spare on-hand.

Preparation before Team Meeting 6


Your task force should prepare a short, well organized, status report for the tasks that you have been working on.

As a team:

Financial officers should prepare a budget status report for the team.

Options for product configuration and overall form should be prepared for discussion. If the models are in an electronic format, there should be a full scale plotted version that can be pinned up to support the discussion and editing during your team meeting. Send plotting requests to the TAs.

System integrators from both sections should meet to form an agenda and update the project schedule, covering tasks through to the technical review. The video lecture this week will cover scheduling practices in detail, but just try your best for the team meeting.

Prepare a draft product contract for discussion. Product contracts will be discussed in lecture 14 on Friday.

The information officers should be sure that everyone knows the Zoom link for participating remotely.

What's due

There are no graded deliverables due during the team meeting this week. Focus on preparing for the assembly review!

Begin with the standard meeting startup.

Acknowledge and point out the team's Code of Values, which will be posted in the team meeting room.

Financial officers should give a short budget update to the team.

System integrators should present an updated project schedule through to the technical review. Input should be obtained from team instructors and team members.

Review the current status of the design. This should include reports from different task forces. Review your draft product contract to ensure that all are on the same page. Revise, as necessary.

Discuss the overall product configuration, use storyboards, and form options using the materials prepared before the team meeting. Consider changes as appropriate and make sure that there is consensus about the direction of the product.

Spend as much of the team meeting time as is possible working. You will have access to both your team meeting room and lab spaces during your team meeting. Time is short. Remember that lead times on ordered parts can be substantial. Some task forces might be working on specific physical models or tests while others work out details of the product assembly and architecture.

Team instructors may want to meet individually with each task force to review progress and help with design issues.

Additional Notes

On Tuesday of this week, 7-8:30 PM, there is a tutorial on interacting with users that will be quite helpful for your final product. Everyone is encouraged to attend. You do not need to have attended the first part in order to attend the second part. At least two people from each team should attend.

Kindly Report a Bug