P16005: Motorized Standing Wheelchair 2
/public/

Planning & Execution

Table of Contents

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%20Management 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 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

Purpose

  1. Facilitate team coordination and identify lacking capabilities.
  2. Establish good practice of structured, coordinated documentation.

Instructions

  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. The team should arrive at consensus on a leader.
  3. Assign responsibility for other important non-design roles and functions, such as facilitator, purchasing, EDGE help, customer PIC, etc. One member should take ownership of this document and ensure it is completed and loaded on EDGE.
  4. Capture relevant skills and experiences of each team member.
  5. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. Skills - team and guides.
  2. Expertise - SMEs.

Outputs and Destination

Document of team capabilities and resources that can be accessed later.

Team Values and Norms

Team Values

Punctual
Each team member will be prompt and arrive at the team meetings on time. If an unexpected conflict comes up, the absent team member will notify at least one team-mate prior to the expected absence. An absent team-member should confirm that a team-mate has received their message (in person, voice mail, email, etc).
Thorough
Each team member will complete their tasks thoroughly and completely, so that the work does not have to be re-done by a peer on the team. If a member does not know how to complete a task, feels overwhelmed, or needs assistance then the member notifies peers, and seeks assistance either from a peer, the faculty guide, a faculty consultant, or another person.
Accurate
Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow.
Professional and Ethical
Each team member gives credit where credit is due. All work completed includes citations to appropriate literature, or sources of assistance. If a team member has gotten assistance from a publication or individual, then that assistance or guidance is fully documented in the reports prepared. Each team member is honest and trustworthy in their dealings with their peers.
Demonstrates the core RIT values of SPIRIT http://www.rit.edu/overview/vision.html
Committed
Each team member will contribute an equal share to the success of the project.

Team Norms: Peer Assessment Rubric

Accepted Norms of Performance: Peer Assessment Rubric
Value Needs Improvement Meets Expectations Exceeds Expectations
Punctual The team member has had one or more unexcused absences or tardy arrivals. The individual could and should have done a better job at notifying (in advance) a peer of the absence or tardiness. The team member was prompt and present at every team event, or any absences were excused in advance. If there was an unexcused absence or tardiness, the team member disclosed the reason after the fact and it was decided upon as a valid excuse by the team. The absent member caught up with a peer as soon as practical and got caught up. Not only is the team member always prompt and present, but the member clearly plans ahead for excused absences and external conflicts. This team member works with the peers on his/her team to make sure that the information flow from the member to and from the peers is smooth even in such cases.
Value Needs Improvement Meets Expectations Exceeds Expectations
Thorough The team member made some progress towards the task assigned, but not as much progress as should have been accomplished. The work may be done but the supporting documentation is incomplete. The team member is getting behind on the tasks that need to be completed. The team member needs to make up the missed work during the next evaluation period. The team member has made solid progress towards the task assigned. The task is complete, and is well done, though it may need some additional work and refinement to be fully complete. If the task was in fact too time consuming, the team member completed as much as would be expected. The task has been completed fully, and is in essentially finished form. The other team members can readily check the work submitted since there is clear documentation. Not only is the work done, but everyone on the team recognizes that the task is complete with little or no need for additional effort.
Value Needs Improvement Meets Expectations Exceeds Expectations
Accurate The work completed by the member contains many errors that must be corrected. While the basic approach to problem solving may be okay, a large majority of the work needs to be re-done in order to be useful to the team. The work completed by the member contains a few errors that must be corrected. The basic approach to problem solving is good, and the errors are relatively minor and could be readily corrected through normal peer review and checking. The work was corrected through consultation with the team members or faculty guide. The team member completed the task with virtually no errors or omissions. The work was accurate, and can be easily scaled to other applications or tasks that the team may encounter.
Value Needs Improvement Meets Expectations Exceeds Expectations
Professional and Ethical The team member has overlooked some references or consistently fails to cite sources and conduct individual tasks. The team member may have made some off-color remarks or been offensive to a team-mate or other individual. The team member needs to clean up his/her act. The team member behaves responsibly and fully documents sources and collaborators on all work. The team member is a role model for others, and behaves in a professional and ethical fashion even under very trying and difficult circumstances.
Value Needs Improvement Meets Expectations Exceeds Expectations
Committed The team member is carrying less than their fair share of the work load. The team member is carrying their fair share of the workload. The team member is carrying more than their fair share of the workload.

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.

For the latest updated version of the schedule, click on the following link: Schedule as of 9/9

Schedule as of 9/9

Schedule as of 9/9

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

Risk Management

For a the latest updated list of risks and risk mitagation, click on the following link: Risk Management
Risk Management

Risk Management

To view the latest updated version of the Risk Assessment chart, click on the following link Risk Assessment

Risk Assessment

Risk Assessment

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

Project Reviews

Preparation, notes and actions, etc. Refer to Project Review page, as well.

Home | Planning & Execution | Imagine RIT

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

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