Table of Contents
|
Behind every successful project is strong project planning and comprehensive documentation. Our team will strive to follow our project plan and communicate effectively.
Please feel free to look around our Project Management directory. This is where we will store information related to planning and execution of our project.
Intellectual Property Considerations
Our team has decided to leave all intellectual property with the sponsor or in the public domain. Less than ~10% will need to be kept confidential.Team Setup
- Brandon Pak
- Role: Project Manager
- Major: Industrial and Systems Engineering
- Role Description: Plans the scope of the project, ensures team members are adhering to established processes, performs "checks" on project plan and team members
- Skills:Project management, R and Minitab(statistical computing software), Statistical Quality Control, Root cause analysis
- Alex Corvino
- Role: Facilitator
- Major: Mechanical Engineering
- Role Description: Insures the interpersonal aspects of the team, ensures meetings and running efficiently, escalates conflicts to the guide
- Skills: Matlab/Simulink, data analysis and collection, Microsoft Office, 3D modeling software such as Creo
- Brent Sorensen
- Role: Communications
- Major: Mechanical Engineering
- Role Description: Main liaison between team and guide/customer/design review attendees
- Skills: Strong in 3D Modeling Software - most experienced in Creo, strong with data analysis and collection, comfortable with machining - mills and lathes, comfortable with hand held power tools and soldering, experience with Matlab and Simulink, worked for Biomass Controls in the past
- Liam Smith
- Role: Lead Engineer
- Major: Electrical Engineering and Computational Mathematics
- Role Description: Makes sure interfaces are properly managed, primarily responsible for coordinating systems integration
- Skills: MATLAB, Simulink, Java, C, Python, math analysis and modeling, EE theory, soldering/wiring, microcontrollers
- Shahzain Haq
- Role: Purchasing
- Major: Electrical Engineer
- Role Description: Maintains the BOM and handles any purchases made by the team
- Skills: MATLAB, VHDL, Critical thinking, Mathematics and Physics skills, circuit analysis, Electrical theory and machinery, Control machinery.
Project Roles
Member | Subsystem Team | Responsibilities |
---|---|---|
Brandon Pak | Project Management | Risk Response Matrix, Team Organization |
Alex Corvino | ME System Integration | Feasibility of System Integration Components |
Brent Sorensen | ME System Integration and ME Data Acquisition | Designing Integration Fixtures and Data Acquisition |
Liam Smith | EE Data Acquisition | Prototyping, Component Selection |
Shahzain Haq | EE Data Acquisition and Purchasing | Test Plan Organization, Documentation Reviewer |
Document Owners
Link to the Document Owner list can be found here
Team Values and Norms
Values
Punctual:Each team member will be prompt and arrive at the team meetings on time. If an unexpected conflict comes up, the absent team member will notify at least one team-mate prior to the expected absence. An absent team-member should confirm that a team-mate has received their message (in person, voice mail, email, etc).
Thorough:
Each team member will complete their tasks thoroughly and completely, so that the work does not have to be re-done by a peer on the team. If a member does not know how to complete a task, feels overwhelmed, or needs assistance then the member notifies peers, and seeks assistance either from a peer, the faculty guide, a faculty consultant, or another person.
Accurate:
Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow.
Professional and Ethical:
Each team member gives credit where credit is due. All work completed includes citations to appropriate literature, or sources of assistance. If a team member has gotten assistance from a publication or individual, then that assistance or guidance is fully documented in the reports prepared. Each team member is honest and trustworthy in their dealings with their peers.
Demonstrates the core RIT values of SPIRIT http://www.rit.edu/overview/vision.html
Norms
Meetings:
Will be determined/scheduled at the end of the previous meeting or over the group chat. If something unexpected happens, message the group before the meeting time.
Unfinished Work:
If unable to finish task or do not know how to do a task, let team know as soon as possible to get help or for someone to take over the task. Lack of communication can cause the whole team to suffer.
During Meetings:
Team members are engaged in activity/task. Will call out people who are not focused. With a long list of deadlines and tasks, we don’t have time to waste.
Documentation:
Document everything. Copy the logbook work into the corresponding Google Doc. This will help when we need to create final deliverables.
Editing Docs:
Create comments on doc, have at least one other team members review work. If you have an large edit to make, discuss before making any changes. Large edit includes changes to content, or contradictory views.
Project Plans & Schedules
Risk Assessment and Growth Curves
Meeting Minutes, Notes, & Actions
Peer Reviews
Peer reviews will be held after every design review. Team members will fill out how they think themselves and other teammates performed overall, one strength each team member brought throughout each phase, and one delta area that the team member can work on to improve the team dynamics.Communication
- Primary customer point of contact: Tom Trabold
- Preferred method of communication: email, tatasp@rit.edu
- Secondary customer point of contact: Harsh Gulati, hg4794@rit.edu
- Communications Officer: Brent Sorensen
- All team members will be cc'd in the communications with the customer.
- Team guide will be cc'd when necessary.
- Within Team Communication
- Preferred method is the GroupMe chat
- Secondary method is email
- Team Guide will be emailed when necessary
- Preferred method is the GroupMe chat
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