Top Ten Risks

1. Not meeting customer expectations.

2. Time constraints on work and contributions by team members, in making stage release due dates.

3. Poor coordination and communication between team members.

4. Poor communication between team and customer.

5. Familiarity and comfort with tools and coding/testing assignments.

6. Each team member understanding their assigned tasks and job duties.

7. Having a common understanding of the project progress, design, and future requirements.

8. Adhering to the class' coding style/standards and properly integrating code from each team member.

9. Using tickets, instead of weekly individual status reports, will not be as thorough and will be abused and reverted to old system.

10. Use SVN more correctly.

Last updated: April 10, 2008