Iteration 1.0C

Planning 

ReleaseIterationStart DateEnd Date

Planned

Stories

Planned

Story Points

Actual

Stories

Actual

Story Points

11.0C06/01/201417/01/201491258

 

User Stories selected for development in this iteration  

RefTitleStory PointsIterationAs a . . .I want . . .So that . . .Status
4Add extra info31.0CProcurement Officerto add extra detail to the basic data from Hunterthe info is more relevant/useful to UoE usersDone
9Keywords21.0CProcurement Officerto manage keywords or tags against contracts and suppliersI can manage what comes back in users' search resultsC/Fwd
20Advanced search11.0CStaff Userto search an advanced search against key contract fields (e.g. supplier, contract title, start/end dates, product/service etc)I can find information quickly & easilyC/Fwd
24Supplier search11.0CStaff Userto search by supplierI can see if they're on the approved list & for which productsDone
34Multiple supplier links0.51.0CProcurement Officerto add multiple links against a supplierI can point users to more detailed informationC/Fwd
35Multiple contract links0.51.0CProcurement Officer to add multiple links against a contract for further informationI can point users to more detailed informationC/Fwd
44Limit search results11.0CStaff Usersearch results limited to suppliers with contracts (& vice versa)I only see relevant dataDone
45Limit Hunter extract11.0CProcurement Officerto see only Hunter contracts with status "contracted"I only have to manage live contracts in Buy@EdDone
46Style & design21.0CStaff Userthe design to be simple & intuitiveinformation is easy to findDone

 

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