Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  • 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 * 9 dev team members81 days
Andy, Yafang, Jay, Pepe, Ola, John, Simon!
Total team absence this Sprint-? days (double check Team availability calendar)




Sprint Goal / Priorities

Sprint Goal: 

As an Admin
I want Dev team to start work on fixing Placements and ESR issues ahead of August round
So that we have improved reliability within TIS

Additional committed work:

  1. Anything commited to for the Sprint not related to Placements or ESR

Live Issues:

  1. Any LiveDefect tickets added to the Sprint

Work Done Demos

ItemDemoDemo - from Prod URL ideally
1.

2.


3. 


4. 


5. 

6.


7.


8.

9.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.