P17310: RIT Observatory Telescope Dome Controls
/public/

Planning & Execution

Table of Contents

Intellectual Property Considerations

This project does not specifically relate the invention or innovation of a new product or service and does not require claims of intellectual property. All IP that may already exist with this project shall remain with RIT and all others originally involved with said IP.

Team Setup

Placeholder

Team Values and Norms

Team Values and Norms

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.

Risk Assessment and Growth Curves

Purpose

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

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

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

Risk Management Template


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