This week |
Weeks on
List |
Risk |
Risk resolution progress |
1 |
3 |
Insufficient upstream activities |
Project
hemsidan underhålls nu.
|
2 |
2 |
Takes to long
time to create the project. Maybe we won't have enough money to finish it. |
Konsult
på ecosoft
Konsult på b-seen
Konsult på TeacerAgenc
Konsult på Nebols Jobb.
|
3 |
3 |
Creeping requirements |
Version
1.0 used to gather high-quality requirements.
Se över konkurenters produkter.
Staged delivery approach will be employed to provide some ability to
change features if needed.
|
4 |
3 |
Abandonment of planning |
This top 10 risk list, so we are aware of the risk of abandoning the planning.
All project members have readed the Software Project Survival Guide.
|
5 |
3 |
Undermined motivation |
Telling
my self affirmationens.
Every time I feel bored work 45 minutes and rest for 15.
Or for real bored of death work 30 minutes and rest 30.
|
6 |
3 |
Requirements or developer gold-plating |
Vision statement specifies what is not included in software.
Design emphasis placed on minimalism.
|
7 |
3 |
Overly optimistic scedules |
We change our MS Project "Task" plan
|
8 |
3 |
Shortchanged quality assurance. |
We have our Change Control Plan.
We have all documents and all source code under Change Control.
|
9 |
3 |
Released software has low quality |
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.
|
10 |
3 |
Unachievable schedule |
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.
|