P15044: Intelligent Mobility Cane
/public/Web-Facing Nodes/

Planning & Execution

This page contains information pertaining to group P15044's expected schedule.

Intellectual Property Considerations

Risk Management

Click the following link to view P15044's Risk Management Plan: Risk Management Plan

ID Risk Item Effect Cause Likelihood Severity Importance Action to Minimize Risk Owner
1 Planning: Customer Requirements not clear/defined Product is not designed to meet needs Customer contact not reliable, communication between parties unclear 3 2 6 Reduce: push for solid answers, if not given go with initial idea and keep pushing for feedback Allan/Marisa
2 Planning: Timeline was not accurately planned Missed deadlines Unknown steps, unforeseen problems 2 2 4 Reduce: Update plan and make benchmarking steps Justine/Andrew
3 Concept Development: Conflicting ideas on what the cane should do Wasted time Lack of communication 2 1 2 Transfer: Majority vote Ben
4 Concept Development: Do not have ability to use certain technologies/ unavailable to us Need to explore other options Budget, location 2 2 4 Accept: cannot control Team
5 System Design: Feasibility failure Wasted money, time Budget 3 2 6 Reduce: Research costs under budget to give room for unforeseen costs Justine
6 System Design: ideas do not work together Wasted time Mechanical/ Electrical/ Manufacturing problems 2 1 2 Reduce: Take into account different systems and their effects on one another Dan
7 Build: Parts are late, wrong parts ordered Missed deadlines Ordered in a rush, company mistake, parts lost during transit 2 2 4 Accept/ Reduce: If late, cannot control, but double check to make sure order is accurate Justine
8 Build: Parts Break Set back in schedule Low quality parts 1 2 2 Reduce: Consider ordering one extra Justine
9 Design Verification: Prototype does not do what it was built to do Big failure for team, goal not reached Rushed design process, unforeseen problems 2 3 6 Prevent/Reduce: Take into account all risks and don’t skip steps in the design process! Team
10 Team: Member does not do their work on time/ is sick or late Sets everyone else in the group behind, missed deadlines Scheduling conflicts, poor time management 1 2 2 Transfer: Team member will make sure to hand off work to another member in time to complete/ communication** Justine/Team
11 Team: Member drops out Down one person, need to re-distribute workload No longer needs class, death, illness 1 2 2 Accept: transfer team member’s role, and move on Team
12 Team: Conflict of ideas Wasted time Different mind sets, goals 2 1 2 Reduce: Have a team mediator, majority vote Team
Likelihood scale Severity scale
1 - This cause is unlikely to happen. 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.
2 - This cause could conceivably happen. 2 - The impact on the project is noticeable. We will deliver reduced functionality, go over budget, or fail to meet some of our Engineering Specifications.
3 - This cause is very likely to happen. 3 - 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.
Importance Action
Prevent Action will be taken to prevent the cause(s) from occuring in the first place.
Reduce Action will be taken to reduce the likelihood of the cause and/or the severity of the effect on the project, should the cause occur.
Transfer Action will be take to transfer the risk to something else.
Accept Low consequence risk may not justify action at all. If they happen, the team will accept the consequences.

Home | Planning & Execution | Team Values and Norms | Problem Definition | Photo Gallery