Planning & Execution
Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use pdf's for display whenever possible so that information is easily viewable without the need to download files and open applications. (Your EDGE file repository should still contain original editable files).
Content related to this node should go in the Project Management directory. Several templates have been posted there for your reference.
All template text and instructions must be removed prior to the Week 3 Problem Definition Review
Intellectual Property ConsiderationsOur customer has granted the team sole intellectual property rights for this project. Therefore, anything that we do that can be under the umbrella of intellectual property belongs solely to us.
|Member||Engineering Role||Project Role||Skills||Contact|
|Lainey Celeste||Mechanical Engineer||Project Manager, Leader||Leadership, Organizationemail@example.com|
|Scott Couwenhoven||Mechanical Engineer||Lead Analyst||Math Modeling, Systems Designfirstname.lastname@example.org|
|Scott Mann||Electrical Engineer||Hardware Engineer||PCB Design and Layout, Electrical Designemail@example.com|
|Trevor Sherrard||Software Engineer||Software Architect||Software Design and Implementationfirstname.lastname@example.org|
|Harrison Keats||Electrical Engineer||Treasurer||PCB Design and Layout, Electrical Designemail@example.com|
|Joseph Mantione||Mechanical Engineer||Lead Designer||Mechanical CAD, Structural Designfirstname.lastname@example.org|
Team Values and Norms
- Ensure positive and meaningful interactions between group members, guides, and subject matter experts.
- Ensure that the values and norms the group stands by are clearly spelled out, agreed upon, and communicated to all relevant stakeholders
Project Plans & Schedules
Overview: A Project Plan that provides an overview on the anticipated schedule for the remainder of MSD 1.
For a complete and in-depth project plan, vist the live document here.
Risk Assessment and Growth Curves
- Facilitate anticipation, avoidance, abatement and accommodation of problems.
- Assess team process capability to drive risk importance total to zero by project end.
Other Team ResourcesThere are a variety of other resources that our team will require for completion of the project. Our Planned Meeting area as it stands now is the MSD Design Center. As for the design and build space we will be using the ME Computer Lab to create our model and eventually the Machine shop to design and build our prototype. Also, Dr. Kolodziejs Lab or the Robotics Lab are available to us for use if needed. 3D Printers may also be utilized in the Brinkman Lab.
Once we have built the beginning of a prototype, we will need a testing area where we can submerge the device underwater. This area will either be the RIT Public pool or the dive pool in Henrietta, depending on the availability of the pool and the capabilities of the device at the time.
As the phases continue and we build a full working prototype, our team will be required to enter an actual lake for the testing the device. Our team will require scuba diving training to successfully retrieve the device and ensure that it is not lost underwater.
- Full list of available RIT courses is available here. If you have an external customer, they may require additional training.
Meeting Minutes, Notes, & ActionsThe outcomes of our initial customer interview can be found here: Link
PurposeProvide feedback that enables improvements in effectiveness and efficiency of individuals and the whole team.
- Instructions and EXAMPLE must be deleted before the Problem Definition Review.
- Identify an owner for this document.
- Each team member will assess each of their team mate per the criteria established in the Values and Norms section.
- Each member will acknowledge excellent behaviors of their fellow team members and provide constructive recommendations to improve the team effectiveness and/or efficiency. (plus/delta recommendations)
- Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.
Inputs and Source
- Team members.
- Template and Example.
- Reference doc.
Outputs and DestinationReview form that is shared with Guide at the end of each cycle. All peer reviews are done using the myCourses peer2peer tool, and teams will discuss the results with their guide after each phase.
Through our team norms, our team has established that clear and frequent communication is desired for effective individualized work. It is our expectation that whenever someone is editing EDGE, going to be late to a meeting, starting work on an assigned group task, or finishing an individualized task, then that will be communicated with the rest of the group. Slack is our main method of communication, while emails will be reserved for communication with our advisor or customer.
Based on our customers preferences, interactions with the customer will be limited to a bi-weekly or as-needed basis, with the exception of sending pre-reads for design reviews. Pre-reads will be sent no later than 1 business day prior to the review. Pre-reads will be sent as a PDF document, with Review Details, link to EDGE, and Additional Remarks. Because our customer is a professor at the college, we will be working with his schedule to ensure that he can attend all design reviews. As such, reviews will only be taking place within regular business hours, Monday through Friday.
Lainey, the Project Manager, will be the main point of contact between the MSD team and our customer. Communication with the customer will be done primarily on email, with in-person meetings or reviews scheduled via email first. She will be responsible for sending the pre-reads, as well as scheduling any interviews with the customer - however the rest of the MSD team will be cc'ed on all communications for transparency.