Top 10 Risks Enumeration

1
Identified By: John
ID: Realistic constraints set on time spent working on project
Exposure: High
Members at risk: All
Note:
We are students and this is an industry level project, this is one 3 credit course, exceptional amounts of time are being spent on this project which may affect other areas of group members lives and academic health.

2
Identified By: Christina, Anam
ID: Broken Code in the Repository
Exposure Level: High
Suggested Handling: do
- regular updates (pulls) so that developers are always working with the most up-to-date code
- only make “sane” check-ins
- all code must be checked against smoke test prior to check-in

3
Identified by: John
ID: Large Volume of Homework/Midterms (esp. same time frame as a deliverable)
Exposure Level: High
Members at risk: all
Suggested Handling:
- regular mini-milestones set outside of due dates
- subset of team take the lead during certain parts of the semester

4
Identified by: Josh, John, William
ID: web view on android app
Exposure level: high
Members at risk: android team web team
Suggested Handling:
- figuring out how to sync up log in on web view inside android app

5
Identified by: Christina, John
ID: Filling out activity log
exposure level: high
Members at risk: All
Suggested Handling:
- ensure good communication and document time spent on project

6
Identified by: Ken
ID: Database Change
Exposure level: low
Members at risk: Ken
Suggested Handling:
- ensure an understanding of how the database will store varying instances

7
Identified by: Josh, John
ID: Compatibility issues with older browser versions
Exposure level: low
Members at risk: anyone dealing with mobile browsers
Suggested Handling: test on all browsers, set default image asking to use chrome or update browser (if page is not supported)

8
Identified by: Ken
ID: Encryption/Security
Exposure Level: med
Handling:
- implement at android app level and database level
- don’t use plain text for passwords
- maybe ensure admin accounts have stricter password requirements

9
Identified by: Christina, Anam
ID: Time Consumed by Defects
Exposure: High
Handling:
- learn from mistakes!
- document what allowed a defect to go undiagnosed and what could have been done to prevent from happening
- modify testing and reviews as necessary (debug the process, not just the code)
- “litter” code with assertions and do not be too concerned about efficiency of assertions because they do not exist in production code!

10
Identified by: John
ID: Modularity and Abstraction
Exposure: High
Handling:
- use of specifications, especially preconditions (these will also help with assertions, peer reviews, mocking)
- make code that is reusable (avoid redundancy)
- use of interfaces/high-level contract (changes made in one place, not everywhere)