Table of Contents
|
Content related to this node is in the Project Management directory.
Intellectual Property Considerations
Our project requires minimal creation and, in turn, protection, of any original intellectual property. Since this is the case we as a team agreed that any IP generated would be assigned to the team as a whole.Team Setup
Anna Dorman
Role: Project ManagerDescription: Maintaining documentation consistency and integrity, ensuring that the team follows processes, coordinate project scheduling and risk management
Eric Deal
Role: Lead EngineerDescription: Interface requirements between subsystems and tracking cross-subsystem engineering requirements
Brenna Lewis
Role: FacilitatorDescription: Coordinate peer evaluations, serve as an objective party to keep work on track, ensure that each team member's opinions are heard, and mediate disputes
Ryan Fairbanks
Role: Communicator and PurchasingDescription: Point of contact between team and guide, customer, design review attendees, Maintain BOM, Handle purchases
Team Values and Norms
Purpose
Define the team's expectations of its members and used as the basis for peer reviews.Our team met to discuss our expectations for the semester as well as the expectations of each member's conduct within the team. This ensures consistent and satisfactory evaluation relative to a consistent set of expectations.
This can be found on the following link 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.Risk Assessment and Growth Curves
Purpose
- Facilitate anticipation, avoidance, abatement and accommodation of problems.
- Assess team process capability to drive risk importance total to zero by project end.
Revision #3 of Risk Management Form.
Peer Reviews
Peer Reviews will be completed by each member at the end of each phase and will be available here once finished.Communication
- Establish customer point of contact
- Establish preferred method of communication
- Establish expected frequency of communication
- Determine customer availability for each of the 5 reviews
- Identify a team member to handle customer
communication
- Establish team expectations for cc on customer emails
- Set expectations for how/when pre-read documentation will be shared with customer
- Establish expectations for within-team communication
- Establish preferred method of communication
- Establish expectations for how/when to include guide in communication
- Establish team expectations for cc on within-team messages
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