Iteration 1.0A
Planning
| Release | Iteration | Start Date | End Date | Planned Stories | Planned Story Points | Actual Stories | Actual Story Points |
|---|---|---|---|---|---|---|---|
| 1 | 1.0A | 26/11/2013 | 06/12/2013 | 5 | 12 | 3 | 8 |
User Stories selected for development in this iteration
| Ref | Title | Story Points | Iteration | As a . . . | I want . . . | So that . . . | Status |
| 1 | Import from Hunter | 5 | 1.0A | Procurement Officer | data imported from Hunter | I only have to enter contract data once | Done |
| 28 | View supplier | 2 | 1.0A | Staff User | to see supplier details | so that I can get the information I want without contacting Procurement | C/Fwd |
| 29 | View contract | 2 | 1.0A | Staff User | to see the contract details | so that I can get the information I want without contacting Procurement | C/Fwd |
| 39 | Polopoly proxy | 1 | 1.0A | Procurement Officer | staff & the public to be able to view contract/supplier info via our procurement polopoly pages | all of our 'buying' info is in one place | Done |
| 5 | User admin | 2 | 1.0A | Procurement Officer | to manage who has access to the admin system | I can give my staff access to update records but keep non-authorised users out | Done |
Review & retrospective (learning points)
Attendees - Craig Henderson (Product Owner), Mike McMonagle (Agile mentor), Jonny Mayo (Developer), Martin Jones (Developer), Dawn Nicholls (Project Manager)
- Review of delivered User Stories
- Retrospective (how did we do?)
- Team seems to be working well together, Procurement Office have been responsive to requests for info.
- Only 3 of the 5 planned stories delivered due to time lost to automated deployment issues