Risks

Risks

Initial Risks and Mitigations

1. Difficulty understanding the specification
2. Rely on Client’s domain knowledge
3. Utilize pair programming to disseminate knowledge
4. Real jobs and life events take precedence
5. Keep calendar up to date and team informed
6. Anticipate individual work and personal life loads and plan accordingly
7. No experience with loadable software tools
8. Rely on Client’s domain knowledge
9. Utilize pair programming to disseminate knowledge
10. More features and school artifacts than the schedule and available resources permit
11. Divide work between pairs to balance artifacts and code
12. DO-178B constraints
13. Utilize pair programming to keep high coding standard
14. Use SCM system to track commits to stories
15. The standard is still early in its life-cycle
16. Utilize Client’s close contact to fix developing problems
17. Gaps in tool knowledge, license knowledge, etc.
18. Utilize school resources to understand constraints
19. Continually be aware of license
20. Utilize pair programming to maximize domain knowledge

New Risks

Third Party Tools

A new risk was identified, unfortunately not until it was an issue. Currently the project relies on several third party tools, GitHub, Pivotal Tracker, TeamCity, etc. Prior to the first release we experienced outages in several of the tools, fortunately none during a critical time. However, on the weekend of the first release, we had an outage that did affect our ability to deliver a non-critical document in the timeframe we desired. While this was not a critical issue, its occurrence prompted us to identify this as a risk.

Issues

We have discussed our risks at the end of each iteration. While we have seen life events, the spec's newness, and our lack of experience affect the project, nothing has been beyond the scope of our mitigation plans.