Iteration 1.0C
Planning
| Release | Iteration | Start Date | End Date | Planned Stories | Planned Story Points | Actual Stories | Actual Story Points |
|---|---|---|---|---|---|---|---|
| 1 | 1.0C | 06/01/2014 | 17/01/2014 | 9 | 12 | 5 | 8 |
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.0C | Procurement Officer | to add extra detail to the basic data from Hunter | the info is more relevant/useful to UoE users | Done |
| 9 | Keywords | 2 | 1.0C | Procurement Officer | to manage keywords or tags against contracts and suppliers | I can manage what comes back in users' search results | C/Fwd |
| 20 | Advanced search | 1 | 1.0C | Staff User | to search an advanced search against key contract fields (e.g. supplier, contract title, start/end dates, product/service etc) | I can find information quickly & easily | C/Fwd |
| 24 | Supplier search | 1 | 1.0C | Staff User | to search by supplier | I can see if they're on the approved list & for which products | Done |
| 34 | Multiple supplier links | 0.5 | 1.0C | Procurement Officer | to add multiple links against a supplier | I can point users to more detailed information | C/Fwd |
| 35 | Multiple contract links | 0.5 | 1.0C | Procurement Officer | to add multiple links against a contract for further information | I can point users to more detailed information | C/Fwd |
| 44 | Limit search results | 1 | 1.0C | Staff User | search results limited to suppliers with contracts (& vice versa) | I only see relevant data | Done |
| 45 | Limit Hunter extract | 1 | 1.0C | Procurement Officer | to see only Hunter contracts with status "contracted" | I only have to manage live contracts in Buy@Ed | Done |
| 46 | Style & design | 2 | 1.0C | Staff User | the design to be simple & intuitive | information is easy to find | Done |
Review & retrospective (learning points)
Attendees - Craig Henderson (Product Owner), Mike McMonagle (Agile mentor), Martin Jones (Developer),Jonny Mayo (Developer), Dawn Nicholls (Project Manager), Anne Finnan (Support Rep)
- Review of delivered User Stories
- Supplier & contract searching and results pages in Polopoly
- Admin screens for maintaining supplier & contract supplementary data
- Retrospective (how did we do and what would we like to do differently next time?)
- Technical issues with Polopoly / SVN / 503 errors have slowed progress
- Lost 2 days to sickness (days will roll over)
- Agreed to discuss selected stories in more detail at planning meetings in order to identify high-level design implications and verify estimates
- Actions
- Anne to start on Deployment Checklist
- Team to work towards a live deployment of 30th Jan
- Dawn to speak to Dev Tech about EASE on the public part of test site as this will prevent Procurement from testing
- Craig's team to start testing next week and to collate issues/change requests
- Dawn to create 2 new User Stories - restricting Hunter import to 'liked' contracts and highlighting inactive contracts on the admin contracts screen
