Provide visibility into team velocity
Problem to solve
Situation: When I'm working on a release plan making prioritization tradeoffs or trying to communicate to internal or external stakeholders regarding when features X, Y, Z could feasibly be done...
Motivation: I want to provide a reliable answer for when my team can likely deliver on X, Y, or Z...
Force: I'm anxious because I'm setting an expectation with a stakeholder and if it is wildly inaccurate, it will result in a negative charge of the "trust battery."
Force: I feel like I'm flying blind because there is no way to reliably answer this question backed by quantitative data that I can trust.
Expected Outcome: So that I can set realistic expectations with stakeholders, build trust, and make appropriate prioritization tradeoffs.
Product managers, project managers, directors, scrum masters, agile coach, product owner, developers (understanding their team velocity as input into iteration planning)
Our Customer's Real Use Cases
Needs to be a way to have a team velocity, as a scrum master be able to go through and say “This feature requires ~100 points of work, we can do 25 points per sprint, will take 4 sprints (8 weeks) – you want it done in 6 weeks, will either require to be simplified or increased resourcing.”
Need burn-down chart/progress status of sprints, features, initiatives, and milestones.
During sprint planning, need a way to see what my team’s velocity has been last several sprints to have a good idea of how much we should be planning for upcoming sprint
Need an easy way to see how much I’m assigning to each team member during sprint planning (team members aren’t interchangeable – sprint can have user stories less than velocity, but if user stories are only doable by one team member then the work can’t get done).
During sprint, need tool to check in during daily stand ups, quickly see current state and progress.
Need to be able to answer questions around “which teams/members are working on this feature?”, “are we still on track to meet this milestone?”, “we want to add this new feature, how will that slow down other development?”, “This team is needed for another project, how will that effect timelines on this project?”, etc...
Permissions and Security
What does success look like, and how can we measure that?
What is the type of buyer?
- Starter or Premium