P17551: Sandia Instrumented 3D Printer
/public/

Planning & Execution

Table of Contents

Content related to this node should go in the Project Management directory. Several templates have been posted there for your reference.

Intellectual Property Considerations

Potential IP concerns will be discusses with Nick as the project progresses. There are no IP concerns at this time.

Team Setup

Member Role Responsiblities Strengths Weaknesses
Ryan Thorna Electrical Engineer
Mike Muldoon Mechanical Engineer
Jonathan Eames Electrical Engineer
Maseo Browning Electrical Engineer
Justin Rueb Project Lead
Jacob Lowe Computer Engineer

Team Values and Norms

Value Expectation
Communication The individual frequently replies to emails, phone calls, slack messages, and text messages quickly, usually within an hour. He frequently contributes well-thought-out ideas with clarity.
Punctual The individual is always early or on time to all group meetings and frequently completes work before the team's specified deadline.
Focus The individual is highly focused on the group tasks and puts forth his best effort to complete the project. Focus is not only on the issue at hand, but also the future of the project. The individual pays attention during meetings and makes valuable contributions.
Quality of Work The individual completes work at an exceptional level, beyond the basic requirements for tasks at hand , and is finished well before appropriate deadlines.
Productive/ Dedicated The individual completes all assignments with time to spare, and volunteers to help others with their assignments.
Honest/ Realistic The individual has a clear sense of the time it takes to do tasks, clearly communicates ability to complete tasks, and assures team members that work will be done.
Responsibility/ Reliability The individual accomplishes all (100%) of his assigned tasks by the team's specified deadline. The individual voluntarily assists in related matters.

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.

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

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

Other Team Resources

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

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

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