P19014: Portable Upright Walker
/public/

Planning & Execution

Table of Contents

Intellectual Property Considerations

Our team is not planning on pursuing a patent for the project unless the in class patent consulting committee feels it is worthwhile to pursue a patent. If a patent is pursued, then we will each share twenty-five percent of the patent ownership. However, we will be keeping design information as confidential as possible.

Team Setup

Purpose

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

Roles

Rachel Taylor

Robert Nash

Alison Kahn

Ryan Guidi

Inputs and Source

  1. Claimed Skills
  2. Claimed Expertise

Outputs and Destination

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

Team Values and Norms

Purpose

The purpose of the team values and norms are to establish expectation that all of our team members for the Upright Walker MSD project are aware of. This way we have a list of values and associated peer grading scheme to hold each other to high standards.

Our team includes: Alison Kahn, Rachel Taylor, Rob Nash, and Ryan Guidi Reference documentation is within public node of EDGE under Problem Definition Guide: Russell Phelps

We agree to be:

Rubric for Peer Review:
Values and Norms Peer rubric

Values and Norms Peer rubric

Inputs and Source

  1. Team members.
  2. Reference doc.
  3. Guide.

Outputs and Destination

Incorporate when considering team plus/delta recommendations during Peer Review

Project Plans & Schedules

MSD Week 3 to 7 Plan:
MSD Week 3 to 7 Plan

MSD Week 3 to 7 Plan

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

Non-Exhaustive list of Risks:
Risk Assessment Draft:
Draft of Risk Assessment Table

Draft of Risk Assessment Table

Draft of risk assessment table here

Other Team Resources

Meeting Space:

Planned Build & Test Space

Meeting Minutes, Notes, & Actions

Meeting minutes can be accessed here:

Peer Reviews

Purpose

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

Instructions

To be added after Design Review
  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

Communication points we’ve accomplished:

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