Sprint 68 Review (2019-02-27)

  • POs present a review of Sprint goals
  • Dev team demo 'done' work contributing to those goals (no more reference to specific list of Jira tickets, and no more reference to work not 'done')
  • POs supported by Dev team provide narrative on why, and what, emergency work was brought into the Sprint and which committed-to tickets were moved out as a result
  • Stakeholders / Users invited to query / interrogate / applaud (after Sprint Review POs convert consensus inputs into backlog tickets, giving the option to consider them in the coming Sprint Planning)
  • POs present the roadmap
  • Stakeholders / Users invited to comment and advise on any changes that should be considered (after Sprint Review, POs coordinate amendments to the roadmap)

Availability

(assume Team Availability Calendar is up to date, otherwise, everyone was available for 9 days of the Sprint

Full team availability 9-day Sprint * 11 dev team members99 days

Simon

Ola

Ashley

Jay

Joanne

Paul

-9 days

-4 days

-5 days

-4 days

-3 days

-1 day

Total team absence-26 days




Sprint Goal / Priorities

Sprint Goal: As a user, I want to be able to log in and use the PPT, So that I can create and update placements on the planner.

The following list was the prioritisation output from Sprint Planning:

  1. Complete the Placement Planning Tool;
  2. Consolidating Admins UI to Angular 5;
  3. Improve performance / reduce errors and the requirement to ask users to clear their cookies / log off and log back in again



Contents

The following items to be shared by team members during this sprint review

key summary type assignee status business value story points (effort) priority (bv*sp)
Loading...
Refresh

Item

TIS Ref / Owner

Status

Description of work
Link. e.g. to working software https://apps.tis.nhs.uk/
(note: use Dev for obfuscated data)
Loom video of completed work https://www.useloom.com/




Knowledge transfer:

  1. Confluence housekeeping - especially deleting documentation that is out of date. Ongoing
  2. Dev standards (Dev meeting / series of meetings). Ongoing
  3. Pairing / Mobbing
  4. Git-commit messages
  5. Walk-throughs (prep as you go - links?). 
  6. Architectural level diagrams
  1. Andy Nash (Unlicensed)


  2. All Dev team
  3. All Dev team
  4. All Dev team
  5. All Dev team
  6. All Dev team

Ongoing












Resource Planning:

Andy Nash (Unlicensed) | Philip Wilsdon (Unlicensed)


Shortlisting Lead dev in Manchester and DevOps in London.

FSD (Joseph) in London starting on 1 April.

Current vacancies (including the above):

Manchester: Lead Dev, FED, Junior Dev

London: DevOps, FED