Sample Top 10 Risks List
Team Name

This page maintained by the Risk Manager

This week

Last week

Weeks on List

 Risk
(priority)
 Risk resolution progress

1

1

5

 Creeping requirements
(120)
  • User interface prototype used to gather high-quality requirements.
  • Requirements specification has been placed under explicit change control.
  • Staged delivery approach will be employed to provide some ability to change features if needed.

2

5

5

 Requirements or developer gold-plating
(190)
  • Vision statement specifies what is not included in software.
  • Design emphasis placed on minimalism.
  • Reviews have checklist item to check for "extra design or implementation."

3

2

4

 Released software has low quality
(230)
  • User interface prototype developed to assures users will accept software.
  • Disciplined development process is used.
  • Technical reviews are used on all requirements, designs, and code.
  • Test planning assures all functionality will be covered by system testing.
  • System tests are performed by independent testers.

4

7

5

 Unachievable schedule
(280)
  • Project avoids making schedule commitment prior to completing requirements specification.
  • Upstream reviews are used to detect and correct problems when it is least expensive to do so.
  • Schedule is reestimated several times over the course of the project.
  • Active project tracking assures that any schedule slips will be detected early.
  • Staged delivery allows for delivery of partial functionality even if whole project takes longer than expected.

5

4

2

 Unstable tools delay schedule
(390)
  • Only one or two new tools are used on this project; remainder have been used on previous projects.

6

-

1

 High turnover
(420)
  • Project vision encourages developer buy-in.
  • Active, detailed project planning creates clear expectations.
  • Periodic reestimation supports revised plans to account for changes in scope without massive overtime.
  • Productivity environment supports high developer productivity, high motivation, and high retention.

7

3

5

 Friction between developers and customers
(480)
  • User interface prototype aligns developers and customers on same detailed vision.
  • Staged deliveries provide customers with evidence of steady progress.

8

6

5

 Unproductive office space
(645)
  • Will move development to off-site environment with private offices after completing user interface prototype.
  • Still need budget approval for conducting project off-site.

Retired Risks

Weeks on List

Date Retired

 Risk Risk Resolution

2

1/20/03

 Backup of Files The team has decided to have the whole project backed up by the CVS administrator every Friday so that the project files would be at most one week old if file loss occurs. In addition, it's advised that all team members should also back up their own work daily.

4

2/03/03

 Power Outage         Team members will take extra precautions when working on their individual assignments.

5

2/03/03

 Quality Assurance All team members are expected to refer to the SQAP for references on what to do for their particular assignments and how to do them. Various guidelines have been created for individual tasks to ensure utmost quality.

3

2/03/03

 Log Books It has become apparent that all team members are turning in their log books on time and correctly; Therefore, this risk has been resolved.

5

2/03/03

 Rapid changes in Requirements Our "plan of attack" was indeed improved so we do not need to perform any major revisions to our software development process and schedule.

Document History

Date

Author

Description




This material is copied and/or adapted from the Survival Guide Website at www.construx.com/survivalguide/. This material is copyright © 1993-1998 Steven C. McConnell. Permission is hereby given to copy, adapt, and distribute this material as long as this notice is included on all such materials and the materials are not sold, licensed, or otherwise distributed for commercial gain.