P20011: Articulating Toilet System
/public/

Planning & Execution

Table of Contents

Content on this page details the planning stages of our project. The documents include our plans for use of intellectual property, team values, risks, our project plan, among others. For more detail, each section includes links to relevant documents relating to the topic highlighted in the section header.

Intellectual Property Considerations

Per the customer's request the team will be placing all project information in the public domain

Including

  1. Product Name
  2. Any models associated with the product
  3. Any / All technologies for chair lift/lower
  4. Any / All Manufacturing Processes
  5. Any other information deemed pertinent by the customer

Team Setup

Roles Overview

The team determined roles for all members in order to ensure that the project runs smoothly throughout its entire duration. Roles were agreed upon based on past experiences as well as the strengths and weaknesses of individual team members.

Assigned Roles

Team Roles Documentation

For a detailed description of each role please visit Project Roles

Team Values and Norms

Overview

We developed a set of values and norms for our team to operate by in order to set standards for all team members working on the project. These norms include team member expectations as well as protocol for handling conflicts

Team Values

  1. Team members will treat each other with respect
  2. Team members will arrive at meetings with a positive attitude
  3. Team members will complete all assigned work by the date required
  4. Team members will be present at all team meetings
  5. If for any reason a member cannot complete work or attend meetings they will contact the rest of the team members immediately.
  6. If conflict arises team members will remain calm and work through the conflict without outburst.

Values and Norms Documentation

For a detailed list of team values and norms visit Values and Norms

Project Plans & Schedules

Purpose

The project plan identified acts as a guideline to the activities to be completed by the MSD team. The teams main method of task organization is through Monday.com where tasks are given precedence and an owner

When creating the project plan, the team worked to identify milestones that would need to be accomplished at each phase of the design. It is understood that this list will likely grow and that the tasks will each have an owner, a team assigned to it, and a time frame that it is expected to be completed by

P20011 Project Schedule

P20011 Project Schedule

P20011 Project Schedule

P20011 Project Schedule

A full time scaled list of activities completed in weeks 1-3 can be found Here

Risk Assessment and Growth Curves

Purpose

The Purpose of assessing the risks of this project was to facilitate a conversation and identify opportunities for project delay. Through assessment of first phase risks the team was able to identify anticipation, avoidance, and accommodation methods for the various risks of this project.

As this project progresses our team will strive to identify risks during each phase of the project adding to the risk matrix linked below.

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

Click here to view our risk assessment

Other Team Resources

1. The team will meet for team meetings outside of Xerox whenever possible. If this space is unavailable the team will meet in the library on the 4th floor. If neither space is available the team will meet in the MSD design center.

2. The current protype for this project is located in the livability lab, the team will strive to test and build in this space but in the case that this is not possible the team will locate a second test space.

3. All team members will be trained for lab safety and human testing procedure.

Meeting Minutes, Notes, & Actions

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

Meeting minutes are maintained on google drive by Kristina Klishko. After each design review, all files will be uploaded to the EDGE for that module.

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

The best point of contact for Doug is via phone - text or call is appropriate

It is expected that the team will communicate with the customer on a when- needed basis. This will be deteremined by the team throughout the design process

Design Review Availability

Review Number Date Customer Available?
Review 1 September 10 Yes
Review 2 October 8 & 10 ?
Review 3 November 12 ?
Review 4 December 5 ?

24 hours before these review dates the customer will be contacted with a pre-read document. All documentation will be sent to the customer via email and this will be sent by Kristina K.

All Team members will be CC'd on ALL project emails, and Art North will be CC'd on all documents going to the customer. Art will also be included on emails as needed

Team will communicate with each other via slack, there is no expected communication schedule however whenever pertinent project information is available

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