P17487: Kontiki Kiln Heat Recovery System

Planning & Execution

Table of Contents

Meet the Team

Abby Higgins

Leah Matczak

Eta Santoro

Kelsey Thompson

Thane Vollbrecht

Our team

Our team

Team Values and Norms

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).
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.
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-mission-values
Each team member will contribute an equal share to the success of the project.

Risk Assessment and Growth Curves


  1. Facilitate anticipation, avoidance, abatement and accommodation of problems.
  2. Assess team process capability to drive risk importance total to zero by project end.


  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

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

Risk Management Template

Other Team Resources

Your team may have other resource requirements. With your customer and guide, your team should identify:

Meeting Minutes

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 | Integrated System Build & Test with Customer Demo | Customer Handoff & Final Project Documentation