P20512: Wearable Interactive Advertising
/public/

Planning & Execution

Table of Contents

Intellectual Property Considerations

Intellectual property will be assigned to the customer, Matthew Morrison, as was agreed on by all team members prior to beginning the project. The customer has stated that all of the team members will be named as inventors for whatever is created, but the intellectual property will belong to him alone. Confidentiality has been requested by the customer by all team members, particularly when it comes to contacting competitors or companies with technology that we wish to implement.

Team Setup

  1. Project Manager/Team Leader: Catherine Daly
    • In charge of maintaining the overall flow of the project, ensures that everyone stays on task, and keeps discussion flowing between the team members.
  2. Archivist: Susan Margevich
    • Takes the meeting minutes and keeps track of documentation/assignments in the team Google Drive and on Edge.
  3. Purchasing Manager: Chase Alberti
    • Takes care of the money and the buying of items for the project and keeps track of the budget.
  4. Test Engineer: Isabela Caetano
    • In charge of the testing of software and hardware, ensures that the product is mechanically and technologically sound, and verifies the designs.
  5. Communications/Facilitator: Michaela Fahey
    • In charge of communicating with the customer and ensures that every team member is having their voice heard.
  6. Lead Engineer: Peter Todoro
    • In charge of a majority of the hardware design elements and communicates with lead programmer and other team members to discuss what is needed and what is possible.
  7. Lead Programmer: James Smith
    • In charge of a majority of the software design elements and communicates with lead engineer and other team members to discuss what is needed and what is possible.

Team Values and Norms

Team members are expected to be:

  1. Punctual
    • Team members will be ready to participate within 5 minutes of the planned meeting time (i.e. all members should be set up and ready for 2pm class by 2:05 at the latest).
    • If a team member is going to be late or absent, other team members will be notified as soon as possible via the team's method of communication, GroupMe.
  2. Thorough
    • Team members will complete given tasks thoroughly so no other member has to re-do the work. If any member feels they cannot complete a task on their own, they should reach out for help from other teammates.
  3. Respectful
    • Team members will avoid condescending attitudes, listen to other team members while they speak, don’t personally attack anyone else, etc.
    • Team members will give credit to other people’s work, whether it be another team member’s or an outside source.
  4. Realistic
    • Team members are encouraged to speak their minds regarding the project, but should be realistic regarding budget, time, and expertise constraints. Team members should also be open to being told that their ideas are unrealistic.
  5. Open-minded
    • Team members should be open to ideas that are not their own, be willing to discuss ideas that are not their own, and able to take constructive criticism on their own ideas.
  6. Professional
    • Team members should ensure that they act appropriately for any given situation. It is fine to goof around a little during team meetings so long as the direction of the team is not massively diverted, but meetings with the customer or with class professors should maintain a higher level of professionalism.

Project Plans & Schedules

Purpose

Ensure timely delivery of all required work products, identify prerequisite tasks with owners, ensure special resource needs are met.

Inputs and Source

  1. Team members
  2. MSD I schedule and deliverables
  3. Key technical focus areas identified by customer

Outputs and Destination

  1. Team task assignments and deadlines
  2. Project review

Schedule

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 | Customer Handoff & Final Project Documentation