P18363: Player Piano 2
/public/

Planning & Execution

Table of Contents

Content related to this node should go in the Project Management directory. Several templates have been posted there for your reference.

Intellectual Property Considerations

Is your team considering filing for a provisional or non-provisional patent? Does your project's financial support carry any IP requirements? Are there select elements of your project that your customer has required that you keep confidential?

There is an excellent set of short videos for reference at https://www.youtube.com/playlist?list=PLmNrnoyQ30KvvBuMJXaPjdFjq-Jm6ghqE

Team Setup

Name Discipline Contact
Kristina Hinova Mechanical Engineer kvh8880@rit.edu
David Custer Mechanical Engineer dwc3529@rit.edu
Jared Loewenthal Electrical Engineer jal4064@rit.edu
Tuyen Nguyen Electrical Engineer thn9901@rit.edu
Kevin Davison Computer Engineer kjd2060@rit.edu
Edward Maskelony Computer Engineer exm8563@rit.edu

Team Values and Norms

Values
  1. Punctuality towards class and meetings
  2. Respectful to group members, sponsors, and guides
  3. Check Slack at least once a day, minimum; advise more often
  4. Along the same note, just generally be in contact through email and Slack
  5. Spend however much time is required out of class to accomplish goals
  6. Take specific ownership of tasks
  7. Persevere through stressful times of the project without causing too much friction.
  8. Use common sense

Norms

  1. Show up to class by 2, make every effort to make the meeting times; if you can’t, let someone know either before hand while we’re planning or if you can’t make it due to unforeseen circumstances. If you’re late to class or whatever try to at least have a good reason.
  2. We’re expected 3 hrs. Per week outside of class for work - this is definitely adjustable based on what is needed
  3. We tend to divide work ahead of time; speak up and take something, try to maintain a balance of what work is being done so everyone is kind of doing their part. The ownership portion should be done while we’re dividing work, in person, rather than waiting til later.
  4. Generally be acceptive towards ideas from other members regardless of your feeling towards it; if you think it’s a bad idea, be respectful in disagreeing, specifically give reasons as to why you disagree.
  5. If someone asks a question in Slack try and answer it. Just generally speak up and answer; if you can’t right that second then just say something like ‘Hey I don’t have time to answer this right now but can in a little bit’.

Project Plans & Schedules

Purpose

Ensure timely delivery of all required work products, identify prerequisite tasks with owners, ensure special resource needs are met.

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. This document will be inspected at all project reviews.
  4. MSD I & II: Work breakdown structure should be used to construct Gantt charts, schedule, etc. Each revision is numbered and dated.
  5. Each milestone/Project Review is enabled by a listing of all of the required prerequisite deliverables. These enablers each have owners, due dates and a common understanding of how good is "good enough" for each deliverable.
  6. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. Team members.
  2. Template and Example.
  3. Reference doc.
  4. Guide.

Outputs and Destination

  1. Team task assignments and deadlines.
  2. Project review.

Risk Assessment and Growth Curves

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.
public/Photo Gallery/risks_table.PNG
Click here to download the requirements document: Risks Document

Outputs and Destination

Completed form to be revisited at all project reviews.
Risk Management Template

Risk Management Template

Other Team Resources

We will be utilizing the RIT construct to 3D print parts for our product, as well as sound monitoring equipment such as sound level meters borrowed from the Electrical Engineering Technology Department. Planning, building, and testing is all done in the Senior Design Center.

Meeting Minutes, Notes, & Actions

MSD I & II. Maintain a record of team/guide meetings. This includes discussion, action items, decisions made, and work assigned.

Peer Reviews

Purpose

Provide feedback that enables improvements in effectiveness and efficiency of individuals and the whole team.

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. Each team member will assess each of their team mate per the criteria established in the Values and Norms section.
  4. 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)
  5. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. Team members.
  2. Template and Example.
  3. Reference doc.
  4. Guide.

Outputs and Destination

Review 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.

Communication

Project Reviews

Preparation, notes and actions, etc. Refer to Gate Reviews page, as well.

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation