Iteration 1.0B
Planning
| Release | Iteration | Start Date | End Date | Planned Stories | Planned Story Points | Actual Stories | Actual Story Points |
|---|---|---|---|---|---|---|---|
| 1 | 1.0B | 09/12/2013 | 19/12/2013 | 5 | 9 | 4 | 6 |
User Stories selected for development in this iteration
| Ref | Title | Story Points | Iteration | As a . . . | I want . . . | So that . . . | Status |
| 4 | Add extra info | 3 | 1.0B | Procurement Officer | to add extra detail to the basic data from Hunter | the info is more relevant/useful to UoE users | C/Fwd |
| 7 | Hide contracts/suppliers | 1 | 1.0B | Procurement Officer | to be able to restrict access to certain contracts/suppliers | we can protect sensitive information from staff and/or the public | Done |
| 21 | Quick search | 1 | 1.0B | Staff User | a quick search (single field) | it's nice & easy to find stuff | Done |
| 28 | View supplier | 2 | 1.0B | Staff User | to see supplier details | so that I can get the information I want without contacting Procurement | Done |
| 29 | View contract | 2 | 1.0B | Staff User | to see the contract details | so that I can get the information I want without contacting Procurement | Done |
Review & retrospective (learning points)
Attendees - Craig Henderson (Product Owner), Mike McMonagle (Agile mentor), Martin Jones (Developer), Dawn Nicholls (Project Manager)
- Review of delivered User Stories
- Supplier/contract search logic now clarified, resulting in 2 new stories
- Retrospective (how did we do?)
- Story 4 was not started and will be carried over to iteration 1.0C
- Issues with Polopoly proxy on Test - Mike thinks he knows what the issue is and will look at this