Risk Management

The risk management categories are as follows:

  • ID: Number used to reference risk
  • Description: Brief description of the risk
  • Responsible Party: Indicates who is in charge of handling the risk.
  • Risk Analysis: The risk analysis has two numbers representing the ranking of the consequence of the risk and the likelihood that the risk will be realized.  A chart of these consequences and likelihood can be found below the table of risks.
  • Area of Impact: Time, cost, quality, other
  • Handling Strategy: How the risk will be handled?
  • Status: What is currently being done to handle the risk
IDDescriptionResponsible PartyRisk Analysis (Consequence x Likelihood)Area of ImpactHandling StrategyStatus
1No Mobile PlatformMohakN/ATechnical,Schedule,
Cost
Check Status with sponsor regularly,
Set final deadline for platforms to arrive.
Email list of MPs to sponsor.
Meet with sponsor.
Purchase test platform.
Closed
2Inadequate Mobile PlatformShivam3x5TechnicalReview platform needs
Only select adequate platform
Closed
3Unsuitable Smartphone InterfaceDorothyN/ATechnical, ProgrammaticFrequent and extensive testingClosed
4Subsystem IncompatibilityPranavN/ATechnical, Schedule, Cost, Programmatic
Research on ROS to ensure compatibility.
Software architecture to ease integration.
Carry out low level cross compatibility tests.
Closed
5Too Many RequirementsShivamN/ASchedule, ProgrammaticTrimmed requirements.
Separated mandatory from desirable.
Appointed PM.
Begin big weekly scrums.
Created Kanban cards.
Closed
6Inaccurate Parking Lot and ObstaclesRicha1x1ProgrammaticAnalyze parking lots IRL.
Scale to match mobile platform.
Closed
7ROS Related IssuesPranav5x1TechnicalArduino/ROS testing.
Android/ROS testing.
ROS-ROS serial communication.
Closed
8SBC and Platform IncompatibilityMohakN/ATechnical, Schedule, Cost, ProgrammaticTest MinnowBoard Max borrowed from Team CClosed
9MinnowBoard Max Processing Power LimitationsMohakN/ATechnical, ProgrammaticTest SBC thoroughly to investigate other possible problems. Research alternative, more powerful SBCsClosed
10Closing Bluetooth Port Dorothy2x5TechnicalHardcode port number into script. Close port by keystroke on SBC side. Close port when app closes on Android sideClosed
11Mobile Platforms don't arrive on timeShivam4x5Technical,Schedule,CostCheck Status with sponsor regularly,
Talk to Prof. Dolan regarding
additional platform.
Closed
12Data latency in subsystemsTeam4x4TechnicalEarly and Extensive TestingClosed
13Interference in Bluetooth
and multiple Xbees
Dorothy, Richa4x3TechnicalEarly identification and fixing requirements accordinglyClosed
14Components arriving lateTeam3x5Schedule, Cost, ProgrammaticOrder many extras, ordering well in advance, contingency plans and immediate actionClosed
15Dependence on Oculus Prime ROS packagesPranav3x3Schedule
Technical
Alter system design accordingly as
soon as loopholes or dead-ends are
identified
Closed
16Dependency of localization on mapping capabilities and parking lot complexityMohak3x2Programmatic, TechnicalKeep design of parking lot as simple
and “feature rich” as possible
Closed
17Multiple points of hardware related failure in perception
and communication
Shivam, Richa3x4Programmatic TechnicalIncremental integration and testing
during development
Closed
18Inconsistencies in
communication and planning logic
Richa4x1TechnicalIncremental integration and testing
during development
Closed
19Navigation Issues in Parking LotShivam, Pranav4x3TechnicalExtensive Testing, Modification of Nav. StackClosed