Risks and Risk Mitigation - Sweater-Baron/safe-ride GitHub Wiki

  • The learning curve of outside resources is steeper than expected...
    • Since the main resources we’re using, i.e. Android Studio and Flask, are something at least one person on the team has experience with, we will seek out other members for help early on and find reliable online resources.
  • Misunderstanding Safe Rides requirements and wishes...
    • We will have clear goals in place that we have decided are discussed and decided are reasonable requirements for this length of product. We will also refer to our notes from the Safe Ride client meeting often to ensure we’re on track.
  • Difficulty establishing working connection between clients and server...
    • We plan on tackling this aspect of the project early on so we’re able to always be working with a MVP.
  • Not meeting the deadline due to unforeseen issues...
    • We will be minimizing this risk by always having some semblance of a MVP. This will keep us secure in the fact that even though we may not achieve all of the functionalities we had originally planned on, we will at least have a working deliverable by the deadline.