Intellectual Property Considerations

This device is intended for release into the public domain upon completion. 

Team Setup

Team MembersRolesSkills
Hannah HusarekProject Manager
  • Organization
  • Planning
  • Leadership
  • Effective communication

Jared Moore

Documentation/Purchasing
  • Strengths Expert
  • Data analysis
Chad WakeMechanical Lead
  • Fluids Expert
  • Controls
Gina WilsonDesign Lead
  • Creo Expert
Kaylie McEntireCommunications/Facilitator
  • Technical Writing
  • Autodesk Fusion 360
  • Effective communication

Team Values and Norms

Purpose

Define the team's expectations of its members and used as the basis for peer reviews.

Team Values and Norms

Escalation for Addressing Issues

  • Discuss among team members to hold members accountable
  • Larger or recurring issues- bring in guide (Steve Pellow), work with guide and team members to address issues/reach a solution 

Potential Failure Modes

This is a live document and will continue to evolve as the semester goes on and team values and norms change. 

Project Plans & Schedules

As a team we are working off a Google Jamboard to keep track of active tasks. We are also populating a Gantt chart in order to keep track of tasks long term. These documents will both be added onto and improved throughout both the semester and the project as a whole.

Risk Assessment and Growth Curves

Purpose

  1. Facilitate anticipation, avoidance, abatement and accommodation of problems.
  2. Assess team process capability to drive risk importance total to zero by project end.

Instructions

  1. Instructions and EXAMPLE must be deleted before the System-Level Design Review.
  2. Identify an owner for this document.
  3. This document will be inspected at all project reviews.
  4. Consider technical, logistical, and resource related risks.
  5. Importance is calculated as the product of likelihood and severity.
  6. Create a projection graph of the total importance over time showing how that approaches zero near the end of MSD2.
  7. Update this chart and graph at the end of each cycle.
  8. Considering the purpose, the team should anticipate potential failure modes associated withe construction and use of this document.

Inputs and Source

  1. Team members.
  2. Template and Example.
  3. Reference doc.
  4. Customer Requirements.
  5. Engineering Requirements.
  6. System and Detail Designs.
  7. Procurement, Production, and Assembly plans.
  8. Test plans.
  9. Overall Process.

Outputs and Destination

Completed Risk Management Template found in Project Management Documents.  Must be revisited at all project reviews.

Other Team Resources

Our team will be meeting in the MSD Design Center. We also expect to build and test in the MSD Design Center, with any necessary fabrication occurring in the ME Machine Shop. Use of the ME Machine Shop requires Shop training (this is also done as part of MECE 104, taken in the first year of the Mechanical Engineering sequence). Use of the MSD Design Center requires general lab safety training.

Meeting Minutes, Notes, & Actions

During MSD I we have been compiling our meeting minutes in a Google Doc in our shared Google Drive.

Peer Reviews

Peer Reviews are private and are shared amongst team members on the team google drive. 

Communication

  • Customer point of contact- Kaylie
    • Preferred method of communication is email.
    • Expected frequency of communication- once a week
    • Customer availability for each of the 5 reviews- will be determine the week before the scheduled review
  • Team member to handle customer communication- Kaylie
    • Team expectations for cc on customer emails- team members and guide will be cc on all customer emails or the emails will be forwarded to group members. 
    • Expectations for how/when pre-read documentation will be shared with customer- the pre-read will be sent out at least 24 hours before the review. 
  • Expectations for within-team communication
    • Preferred method of communication- During class→ in person or over zoom Outside of class → slack
    • Expectations for how/when to include guide in communication- when have questions about specific assignments or to give updates on current set milestones
    • Team expectations for cc on within-team messages- all team members will be cc'ed on all inter-team messages

Project Reviews

Problem Definition Phase Review

Systems Level Design Phase Review

Preliminary Detailed Design Phase Review

Detailed Design Phase Review




  • Aucune étiquette