Sprint Details Aide Purpose

Sprint Details Aide is a Chrome extension used as a complementary, UX improvement tool to Agile Teams who track Story Points (or effort of any kind) spent on a Story each day by the Team.

The Chrome Extension turns static field labels (i.e. 1,2,3,…15) into dates based on the Field Label names Starting with the word “Day”….. (These fields are case insensitive). Please, contact ryan@keybuildingblocks.com if your team is looking to scale to a new purpose; features can be added to make this more usable to a larger audience.

Get your DevOps Story Templates Setup for the Extension

  1. Create Sprint in Azure DevOps with accurate start and end dates for each sprint.
    1. See Microsoft’s instructions for Sprint management.
  2. Add the necessary fields to your User Stories.
    1. Fields where dates of the sprint 
  3. Your Team starts using the Sprint Details Aide Extension to see readable dates

Limitations of the Sprint Details Aide Chromium Extension

  • All the custom field labels where Dates are inserted must start with the word “Day”.

Why Teams Track Remaining Story Points/Effort

Story Points are primarily used for planning purposes; however, it can be advantageous to track remaining effort(points) per day on a user story. Other teams may track the effort spent on a story each day. Both teams use a very similar User Story or Product Backlog Item template with several hard-to-read labels representing days of a sprint.

These remaining or actual points spent on a story can be a Key Performance Indicator (KPI) metric in some Teams/Organizations for Sprint or Scrum Team Health.

When should we enter story points every day?

Rather than only entering story points during or before Sprint Planning, it may be:

(1) helpful for the Team to track their story point efforts worked on each day. This helps to better understand their estimated work versus their actual efforts. It is enlightening, for individual team members,  to see they have spent 3 days putting maximal efforts towards a problem originally estimated at 1 story point.

(2) necessary for Leadership, Scrum Master or Project Management to track daily work for Sprint reporting or analysis of improvements to be made in the Agile process (or even earlier, such as the need to improve your Team’s Demand intake model).

Why enter story points in a field per day rather than one field that consistently changes?

To generate more meaningful Sprint Health metrics and reports, it can be advantageous to create individual fields to track remaining effort each day, rather than using 1 field for progress each day.

The idea of having one field per day provides a deep, aged-data insight into what happens at every step of the sprint. This idea of aged-data is the value added to looking at the Team’s work. 

Shopping cart

0

No products in the cart.

Collection Launch Sale
Where should we send your 20% off code?
Limited time offer. Don't miss out!
    GET MY 20% OFF
    I agree with the terms & conditions
    No, I don't want deals!