Sprint reports - key to successful release plans

ashwini's picture
Technical Architect, Srijan
Beginner

Sprint reports are touchy subject. Many of us had misfortune of being on a project where these reports/metrics/stats are used as a weapon/blame game, pitting one team against another or justifying mandatory weekend work or provide lack of visibility to stake holders.

Getting the accurate sprint reports with correct metrics in the project development cycle (especially during the initial sprints of release plan) definitely strengths any team's chances to achieve the project deliverables on time and keep our customers happy.

So how you'd beget the visibility of your project to your team and stake holders(PM/Clients/Sponsors)?

Our session would be focused on below paramount points; It would be a story with comparison, examples and demos:

  1. Why sprint reports are required?
  2. Making the best use of early reports; probing team and clients with questions to get the realistic/transparent view of the product.
  3. Define clear dark areas in the scope; calling them out early. Show the clients the zeal of the scope and plan with transparency.
  4. refine the scope again. Rinse, Repeat!
  5. How it is different from JIRA reports? with one bring all together.
  6. Examples of different product teams using different pattern of sprint reports.
  7. How to become more realistic, transparent and mature with release plans and continuous improvement.

 

What level of knowledge should attendees have before walking into your session?

  • The session is open for beginner. However the session should be open for everyone.

Take Away for attendees:

  1. How to prepare realistic sprint report?
  2. Provide more transparency to stakeholder and team.
  3. How to refine scope based on sprint reports?
  4. More mature approach towards the realistic release plan.