P17421: Robocomposter 2.0
/public/

Planning & Execution

Team Roles

Charlie Friedman: Team Lead/Purchasing/Mechanical Engineer

I am a fifth year, dual degree student in the mechanical engineering program with a Master’s focus on thermal/fluids engineering. I have four completed co-op’s over the past 4 years working with Wegmans Food Markets, Sikorsky Aircraft, Toyota Motor Manufacturing and Engineering, and Lockheed Martin. Additionally, I served as a research assistant in the Sustainable Energy Lab at RIT. I will assure the team completes all deadlines, delivers work per established standards, complete all purchasing requirements, and perform most hardware changes to the prototype.

Dante Gonzales: Webmaster/ Computer Engineer

I am a fifth year student in the Computer Engineering. I completed a co-op for Kodak Alaris as an Operating Systems engineer in Rochester, NY. I am tasked with maintaining the Edge website and developing the code base for the interface between the hardware and microcontrollers.

Emir Ljuca: Communications/ Electrical Engineer

I am a fifth year Electrical Engineering student. I have worked in three different companies including SRC Tec as a engineering intern, DRT Boeing as a firmware engineer, and RIT for research in photonics. I have worked under the IEEE student section and worked on the micro mouse competition team at Onondaga Community College. I am tasked with interfacing with the sensors to provide data for the user. Along with this I will be working on the raspberry pi, arduino, and designing and testing the electronics needed.

John Maguire: Documentation/Electrical Engineer

I am in my final year at RIT as an Electrical Engineering student. I have completed two different co-ops at Critical Link and the NATO Communications and Information Agency. I am tasked with ensuring the wiring for the system is correct as well as formatting documentation in order to be prepared for proper presentation

Team Values and Norms

Accepted Norms of Performance: Peer Assessment Rubric
Value Unsatisfactory Meets Expectations Exceeds Expectations
Communication Is difficult to reach via phone, text, or e-mail. Takes longer than a week to respond to inquiries. Responds to e-mails and group chat conversations in 2 or fewer days. Sometimes troublesome to reach via phone or text. Responds quickly to e-mails and group chats. Will acknowledge phone calls and texts if unable to contribute or answer at the moment.
Contribution Contributions during meetings are infrequent or irrelevant. Little effort is put into assigned tasks requiring large revisions from other team members. Contributes to meetings with standard information. Assigned tasks are done with expected quality requiring few major revisions or team intervention. Contributes well researched, quality information along with insightful problem solving. Quality of assigned tasks generally exceeds expected quality.
Leadership Never takes charge of a situation. Always in the background. Periodically leads a task or assignment, but only when required. Routinely exhibits strong leadership skills, including knowing when to step back and let another leader take charge.
Participation Missed 2 or more meetings without communicating with the group / coordinating absence. When at meetings, does not engage with the group and is focused on other tasks. Missed 1 meeting without an excuse, or missed an excessive number of meetings with an excuse. Mostly focuses and participates in meetings, but will occasionally focus on something else in meetings. Missed no meetings or coordinated / excused absences infrequently. Ensured impact of absence is minimized and doesn't set group back. Always focused on the task at hand and ensures team members are as well.
Respect Belittles others in meetings and focused on people instead of problems. Doesn't follow team decisions and may cause setbacks for team. Generally has a poor attitude. Generally respectful to other teammates, tries to focus on issues instead of people. Will follow the team decision though at times may seem unhappy about it. Always acts professionally and tactfully toward teammates. Goes out of their way to give assistance and support to other teammates. Always gets behind team decision, and helps spread a positive attitude.
Task Support Neglects to help out teammates even when specifically tasked. Rude or unresponsive when given tasks. Willing to help out teammates when asked but unwilling to take an equal share in task completion. Waits for others to take ownership of tasks before taking initiative. Always takes steps to assist teammates, even when unasked or unprompted. Each member confirms their assignmed tasks at the conclusion of every meeting such that there is no uncertainty about assignments.
Timeliness Submits more than 3 assignments late without notification. Submits 1-3 assignments late without notification Submits all assignments on time, communicates if anything came up and coordinates to ensure tasks get done.

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