The Final Top 10 Risks List

Automated regression testing is behind schedule

The test cases have been assigned, but a lot of work still remains.

Team members need to stick to the schedule.

N/A

Too many defects

We currently have 25 open defects, with a couple being added each day.

Team members should stop hunting for new defects

Start fixing all defects assigned to them.

Web documents not being listed as being updated

With so much being updated each day, it is important for everyone to know what has changed.

Each team member should update the 'what's new' link every time they update the website.
Remember to update the paged you worked on also.

N/A

Dead Week approaches

Many of us have significant assignments to do ouside of this class. If you find yourself stressed:

Make sure you are eating. Skipping meals won't help keep you awake for an all-nighter.
Get as much sleep as possible (even if that means taking cat naps between class breaks).
Go outside, get some fresh air, watch the clouds get gray and start to pound rain on your head, and then go back inside and get more work done! :-)

Build broken because of too many features integrated

With so many defects to fix, we need to do up our 'daily' build schedule to every day.

The new schedule hasn't been estimated correctly

All of us went over schedule last week and most of us will probably do so again this week.

If time runs out, we need to make a list of defects we can fix and which we can't fix in time for the release.

No user feedback

We haven't had user feedback in a while now and the acceptance test is less than a week away.

Have user liason ask for feedback on the current build so that the user has an idea we will provide him for the acceptance test.
Log the user feedback and see if our defect list cooresponds to it.

Altering of the Design

A few of the change requests require alteration to the design.

Make sure these changes don't break the rest of the design.
Be sure to update the design docuements.

Developers don't want to quit

They want to develop, not fix defects.

The integration plan is done/complete. No new features should be added.
Have the manager assign defects as specific action items with due dates.

N/A

Unplanned disasters

With so much going on, it would be a shame to lose it all.

Save often.
Don't install/reinstall Windows, motherboards, etc.
Know the campus lab hours (we can get a key for 256 too).

This Week	Last Week	Weeks on List	Risk	Risk Resolution Progress
1	2	1	Automated regression testing is behind schedule	The test cases have been assigned, but a lot of work still remains. Team members need to stick to the schedule.
2	N/A	0	Too many defects	We currently have 25 open defects, with a couple being added each day. Team members should stop hunting for new defects & Start fixing all defects assigned to them.
3	10	2	Web documents not being listed as being updated	With so much being updated each day, it is important for everyone to know what has changed. Each team member should update the 'what's new' link every time they update the website. Remember to update the paged you worked on also.
4	N/A	0	Dead Week approaches	Many of us have significant assignments to do ouside of this class. If you find yourself stressed: Make sure you are eating. Skipping meals won't help keep you awake for an all-nighter. Get as much sleep as possible (even if that means taking cat naps between class breaks). Go outside, get some fresh air, watch the clouds get gray and start to pound rain on your head, and then go back inside and get more work done! :-)
5	1	1	Build broken because of too many features integrated	With so many defects to fix, we need to do up our 'daily' build schedule to every day.
6	8	2	The new schedule hasn't been estimated correctly	All of us went over schedule last week and most of us will probably do so again this week. If time runs out, we need to make a list of defects we can fix and which we can't fix in time for the release.
7	9	2	No user feedback	We haven't had user feedback in a while now and the acceptance test is less than a week away. Have user liason ask for feedback on the current build so that the user has an idea we will provide him for the acceptance test. Log the user feedback and see if our defect list cooresponds to it.
8	7	3	Altering of the Design	A few of the change requests require alteration to the design. Make sure these changes don't break the rest of the design. Be sure to update the design docuements.
9	6	2	Developers don't want to quit	They want to develop, not fix defects. The integration plan is done/complete. No new features should be added. Have the manager assign defects as specific action items with due dates.
10	N/A	0	Unplanned disasters	With so much going on, it would be a shame to lose it all. Save often. Don't install/reinstall Windows, motherboards, etc. Know the campus lab hours (we can get a key for 256 too).

	Top 10 Risks - Weeks 9 & 10