Intellectual Property Considerations

Limited use agreement to allow Kids Miracle Making Club, Inc. to use outcome, team retains ownership.

Project will be in public domain as many technologies used are already in the public domain. Additionally, the Robotic Art Assistant has a goal to help students with varying abilities draw, paint, and participate in art class alongside their peers. We plan to keep most of the project in the public domain, so the information is available to most educators and students. 

Team Setup

Team Roles

Project Manager: Andrew Pasek

Guides the team through the project, coordinate team schedule and risk management

System Engineer: John Owens

Defines the interface between sub-systems, track engineering requirements, coordinate integration of sub-systems

Facilitator: 

Coordinate peer evaluations, ensure team member opinions are heard, mediate disputes between team members

Purchasing: Allison Morgan

Submits purchasing requests, tracking team budget, track shipping/inventory

Communication: Dylan Lebedin

Schedules meetings with client, coordinate information, note taker during client meetings

Documentation: David Nwokolo

Ensures all documentation is complete and well written

Team Skills

Team Values and Norms

Team Values

Honesty

Each member of the team will give accurate updates about their individual progress and alert the team to shortcomings or road blocks they encounter.

Respect

Each member of the team treats others as equal colleagues. No team member's ideas are dismissed. 

Punctuality

Each member of the team will be present and active at the team meetings. If a member cannot make the scheduled time, a message should be sent in the team slack group prior to the meeting.

Accountability

Each member of the team is accountable for the work they are assigned. It is the team member's responsibility to complete the work and to respond to questions asked by the team.

Thoroughness

Each member of the team will complete their assigned tasks such that work does not have to be edited by or re-done by another member of the team. 

Escalation Process

Facilitator→ Team Discussion→ Team Guide → Individual Department Coordinator → Course Coordinator

Team Norms

Team Standup

Each team member will complete a standup on each day the team will meet. The standup will be completed at least 30 minutes before the start of the meetings. The following questions will be answered during the standup:

  1. What did I do since last class?
  2. What will I do next?
  3. What is in the way of getting my work done?
  4. Will I be in class or remote today?

Project Plans & Schedules

Trello: https://trello.com/b/2vqqw7nJ/p21068-tasks

https://docs.google.com/spreadsheets/d/1KmjMadTV5KbVxw-ieAmoUcFkUw015Voho2FbI4hJ_PI/edit

BOM

The live document is located here.

Risk Assessment and Growth Curves

The team is still early in the design process and therefore only has a small set of risks identified. More risks will be added and current risks reassessed as the design progresses

Likelihood Scale:

1- This cause is unlikely to happen

3- This cause could conceivably happen

9- This cause is very likely to happen

Severity Scale:

1- The impact on the project is very minor. We will still meet deliverables on time and within budget, but it will cause extra work

3- The impact on the project is noticeable. We will deliver reduced functionality, go over budget, or fail to meet some of our requirements

9- The impact on the project is severe. We will not be able to deliver, or what we deliver will not meet the customer's needs. 

Other Team Resources

Meeting Schedule

  • Monday 2:30-5 pm - MSD Design Floor Table 17
    • Zoom meeting with Art
  • Wednesday 2:30 - 5 pm - MSD Design Floor Table 17
  • Thursday 9 - 11 am - MSD Design Floor Table 17
    • In person meeting with Art

Planned Build & Test Space

  • The team will consider space/storage in the MSD Design Center as the project progresses and building/testing space is needed.

Meeting Minutes, Notes, & Actions

Team Meeting Notes

Review Notes

Peer Reviews

Peer Reviews will be submitted via myCourses and then discussed as a team. The views will not be posted on the Confluence page. Any team actions or retrospectives will be posted on the corresponding review notes page.

A template peer review can be found at: https://docs.google.com/spreadsheets/d/1oWg0BF-9P2NtdkTal8TOQFEt1RvVE2TrLwIDXDdjrZE/edit#gid=1261804498

Communication

External Communication

  • As the Communication Lead, Dylan will handle customer communication
  • Customer communication will occur via email
    • CC team members on emails
  • Any reviews or client meetings will be conducted over Zoom
    • Link to confluence wiki page through email at least 24 hours prior

Internal Communication

  • Communication within the team will occur through the general Slack channel: p21068-robo-art
  • Standups will occur on each class day before 1:30 pm in the Slack channel: p21068-standup
  • Other slack channels will be added if/as needed
  • Guide is part of Slack communication on daily basis.
  • For roadblocks, bureaucratic challenges the guide will be individually contacted for guidance

Project Reviews

Preparation, notes and actions, etc. Refer to Gate Review page, as well.

  • Aucune étiquette