Docs::Risks

Risk	Chance	Plan
No devops experience setting up test plan for our environment.	1.00	Extra time will be budgeted to setting up testing environment.
Callback registering added as last minute feature. May cause implementation issues.	0.20	Team will have to be aware of this during development and inform the rest of the team/sponsors as issues arise.
Libraries we are using may have unknown bugs.	0.01	Discussions with the project and faculty sponsor or technology change based on the severity of the bug.
Project documentation becomes becomes a lower priority or is ignored until later in the project.	0.30	Project documentation will be updated as needed over the course of the project.
Team becomes too focused on project and misses class deadlines.	0.25	Team will frequently check or record somewhere easily accessible the extra project deliverables.
Currently there is a high level of delegation of tasks within the team. What would happen if one of the team members becomes incapacitated for a significant amount of time (e.g. a week)?	0.75	Team meeting will include brief summaries of what people have been working on. Ideally no one person will be the only person who can work on a project area.
Working with XML may be more difficult than we thought.	0.15	Potential problems with XML or any system should be brought up and discussed with the team as they arise. Faculty and project are both technical and can be used as means to work through these problems.
Lack of effort with end of year approaching. Ex, missed deadlines, forgetting to log hours on activity tracker, etc.	0.10	Have a detailed plan for assigning tasks for following up on their completion. Team will make an effort to hold other team members accountable.