P19037: Skreppa Modular Shoe
/public/

Planning & Execution

Table of Contents

Intellectual Property Considerations

Regarding Intellectual Property (IP), the team has agreed that it will be taken into consideration and will be owned by the members of the project group. Considerations for IP are listed below but are not limited to the noted items. Exceptions are listed below denoting where IP will not be considered.

Patents: Shoe Connection Mechanism, Modular Shoe concept

Trademarks: Skreppa Logo & Name

Copyrights: Skreppa Designs

Exceptions: Any novel method on waste processing will be left open to the public domain. This is to encourage others to actively utilize the process to widely cut down on any waste our society produces.

Team Setup

Mickey Evans

Major: Industrial Engineering

Role: Project Manager

Valuable Skills

Nick Amato

Major: Mechanical Engineering

Role: Purchasing Manager

Valuable Skills

Lydia Yeckley

Major: Mechanical Engineering

Role: EDGE Help, Customer Point of Contact

Valuable Skills

Haley Gallagher

Major: Biomedical Engineering

Role: Human Expert

Valuable Skills

Jerry Adamski

Role: Project Guide

Valuable Skills

Team Values and Norms

Purpose

The purpose of Norms & Values for a successful MSD team is to have guidelines in case problems arise in regards to inter-team relations. This section should be referred to in any situations of uncertainty about expectations, responsibilities, decisions, etc.

Expectations for Members

All member will demonstrate professionalism, be on time to meetings or will notify other members if they will be late or absent. The expectation will be that team members will produce work to the best of their ability and if they are not able to, tell someone or raise awareness to other group members before the due date. In addition, when possible, keep the project as fun as possible.

Roles & Responsibilities

Roles will be taken on as needed to focus on capturing specific skills of individuals with which they have expertise. Roles will also be taken on as needed to fulfill graduation requirements.

Balancing The Distribution of Work

Weekly actionable measures will be spelled out and distributed to each of the team members. As a team, we will come up with a completed list, what hasn’t been completed, and a what needs to get done for the upcoming week during our weekly meeting time. From this list, the team will distribute work “equally” as needed to complete the required deliverables.

Honoring The Strength Of The Individual

All members of the team possess unique traits and skills that they will be able to bring to the project. Team members are expected and encouraged to work to their strengths but are also expected to have a hand in all facets of the project to promote the well-rounded nature of the project.

Decisions By Consensus

As a TEAM we will have to make major decisions for our project. All team member opinions and thoughts will be taken and considered to ultimately make a TEAM decision on major and large issues at hand. Before any final decisions are made, the TEAM will consult the guide, Jerry Adamski, for further analysis and opinion before a final decision is made.

Team Member Communication

Communication will take place through e-mail, online messenger applications, face-to-face, phone calls and text messages, Google Drive, Trello, when2meet, and any other online resources that allow a messenger or “posting” interface. All members are expected to respond to any messages within a reasonable timeframe to keep updated and all members on the same page.

Guide Communication

Communication with our guide, Jerry Adamski, will be done during class hours with all team members present. If communication with the guide is needed outside of class, each team member has the guide’s personal contact information.

Conflict Resolution

In order to resolve any conflicts that may arise, the team will implement a step by step process that will lead to an efficient and positive solution. If the disagreement is between two or three team members, the remaining individual(s) will hear both sides of the argument separately and mediate the situation from there. If a solution could not be reached, team members should seek out the team guide, Jerry Adamski, for guidance. If the disagreement is between all members, the team should directly seek assistance from Jerry to efficiently find a solution before any time is lost.

Continual Improvement

As a team, it has been agreed that we will self reflect on the work completed each week, in addition to a weekly team check in outside of the MSD meeting times. During these times, the team will focus on each completed task, what was learned, and what can be improved upon.

Philosophy

During the development process for the Skreppa Modular Shoe, there are vital philosophies that should be adhered to:

Inputs and Source

  1. Mickey Evans, Nicholas Amato, Haley Gallagher, Lydia Yeckley.
  2. Jerry Adamski.

Outputs and Destination

Incorporate when considering team plus/delta recommendations during Peer Review

Project Plans & Schedules

Schedule (Sept - October)

Schedule (Sept - October)

Schedule (October - December

Schedule (October - December

Schedule Layout (Sept - October)

Schedule Layout (Sept - October)

Schedule Layout (October - December)

Schedule Layout (October - December)

You can also download an Excel or PDF version of the schedule below:

Excel

PDF

Inputs and Source

  1. Mickey Evans, Nicholas Amato, Haley Gallagher, Lydia Yeckley.
  2. Template and Example.
  3. Reference doc.
  4. Jerry Adamski

Outputs and Destination

  1. Team task assignments and deadlines.
  2. Project review.

Risk Assessment and Growth Curves

Inputs and Source

  1. Mickey Evans, Lydia Yeckley, Haley Gallagher, Nick Amato
  2. Risk Assesment Document Template
  3. Risk Assesment Photo Template
  4. Customer Requirements
  5. Engineering Requirements

Outputs and Destination

Risk Management Matrix

Risk Management Matrix

Other Team Resources

Planned Meeting Space: MSD Room for class, Erdle Commons or Gordon Atrium for meetings outside of class time.

Planned Test Space: MSD Room

Meeting Minutes, Notes, & Actions

MSD I

Problem Definition Phase

8.30.18

9.2.18

9.4.18

9.6.18

9.11.18

9.12.18

Systems Level Design Phase

9.18.18

9.20.18

9.25.18

9.27.18

10.2.18

10.4.18

Preliminary Detailed Design Phase

10.16.18

10.18.18

10.23.18

10.25.18

11.1.18

11.6.18

MSD II

Peer Reviews

Inputs and Source

  1. Mickey Evans, Nicholas Amato, Haley Gallagher, Lydia Yeckley.
  2. Template and Example.
  3. Reference doc.
  4. Jerry Adamski

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

Project Review #1 - September 13th, 2018

Project Review #1 Presentation

Project Review #1 Notes

Project Review #2 - October 11th, 2018

Project Review #2 Presentation

Project Review #2 Presentation Notes

Project Review #3 - November 7th, 2018

Project Review #3 Presentation

Project Review #3 Presentation Notes


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