Assessing the Stories
In looking at the stories, the developers determined that the following risks were associated with the values that the customer assigned to the tasks. This matrix was created with the previous requirements:
| |
High Value |
Medium Value |
Low Value |
| High Risk |
Custom Reoccurrence Measurements can be Used when Creating Tasks (3)
Custom Reoccurrence Measurement Values can be Incremented on the Fly (3)
|
Custom Reoccurrence Measurements can be Managed (3)
Multiple Custom Reoccurrence Measurements can Map to One Value (2)
|
Tasks can be Viewed in a Calendar (3)
|
| Medium Risk |
A Progression Value is Tracked for Each Task (3)
|
Reminders can be Setup to Notify the User of a Task (3)
|
|
| Low Risk |
Tasks can be Saved (1)
Tasks can be Opened (1)
|
Tasks can be Deleted by the Delete Key (1)
|
Task Properties can be Edited (2)
|
From this, we can see we have a lot more risk than we did previously. From this, the users determined that the "Tasks can be Viewed in a Calendar" option will be cancelled, at least for now. We also determined that for the first iteration, we will use the following stories:
- Tasks can be Saved
- Tasks can be Opened
- Tasks can be Deleted by the Delete Key
- Task Properties can be Edited
This will be the first iteration period that we will progress to.
Also, from the estimates above, it will take about 25 weeks to complete, including the testing time. I have a feeling this is an inaccurate estimate, but do not adjust it at the present time. You calculate this value based upon the 1,2,3's above (1,2,3 weeks are the actual values), and from this, you estimate how long it will take. However, as you work on the project, the project manager edits the timelines constantly to reflect how the team is actually working, slowly making it a more complete picture of the application. You will see this as we progress with this application.