User Stories

As a Tech Fleet Agile Coach, I want to make more informed decisions about how much work our Agile Coach pilot team can take on each week so that we can finish what we commit to.

Background

We are at the point in our backlog where we’re ready to start measuring the amount of work we’re committing to and finishing. This ticket deals with a process for measuring velocity through planning poker.

Problem to Solve

Today, the Agile Coach pilot team may have poor outcomes because the team makes judgments themselves about how much work we can take in in Agile Coach Pilot work.

Task Goals

1. Help Agile Coach teammates make more informed decisions about how much work is too much work in one sprint during our pilot.

Task Scope

1. Play planning poker
   1. Estimate previous work from sprint 1 to 3
   2. Estimate sprint 4
2. Determine historical average velocity
3. Track on a page in Notion

Expected Outcomes for the Ticket

1. Average velocity for Agile Coaching team based on sprints 1 - 3

Listed Acceptance Criteria

1. Play planning poker and determine the average historical velocity for all previous tickets we worked on
2. Track the sprint velocity average on Notion
3. Determine our current velocity on sprint 4 and make a call about whether it’s too much work