| Table of Contents |
|---|
Roadmap Focus
...
Why:
Understand how much of your team’s effort is going towards roadmap work vs maintenance and tasks.
Answer the question “How long do you think this will take?” with confidence knowing how focused you’ve historically been on planned work.
...
Group series by parent properties to represent your team’s roadmap parent type.
Filter out “Won’t Do” statuses via Advanced Filters
Utilize a pie chart and look at all work completed over the past 60 or 90 days.
Velocity
...
Why:
Understand if your team is consistently delivering based on their estimation and pointing.
...
Sprint Attainment (for Scrum Teams)
...
Why:
Understand if your team is correctly committing to planned work.
Determine if interruptions are coming into your sprints after the start.
...
Did we complete all of the issues committed to at the beginning of the sprint and meet our goal?
Threshold goals can vary, but a standard goal is between 80-90% committed work completed during the sprint.
Cycle Time
...
Why:
Understand if your team is consistently sizing and estimating work.
...
Series grouping to consider:
Story Points: Understand if the team is consistently pointing work of relative technical complexity and time.
Issue Type: Confirm the team has consistent definitions of work by issue type.
I.e. The smallest issue type (sub-tasks or tasks) should be work that is always completable within 2-3 days.
Aggregate by median to remove statistical outliers.
Filter out “Won’t Do” type states
Lead Time
...
Why:
Understand how quickly your team responds to high priority bugs, defects, and customer inquiries.
...
Filter out “Won’t Do” type issue/work item states.
Filter down to bugs, defects and/or customer requests.
Group by month or quarter.
Group series by priority/severity.
Aggregate by median to remove statistical outliers.
Issue Time in State
...
Why:
Analyze for bottlenecks
Finding median or average time in progress, wait states, etc.
For example, in progress states should often be under 24 hours. Make sure items aren’t bottlenecked waiting for QA resources, etc.
...
Defect/Bug creation over time - filter by backlog
...
Why:
Metric:
Settings to Apply:
Issue creation metric
By priority/severity
Filter to the relevant backlog of the team.
Bouncebacks
Why:
Metric:
Settings to Apply:
- Displays cards that have revisited previous states, like QA back to dev, or dev back to product requirements
.
Increase shows churn/uncertainty
Also sort by number of bouncebacks on cards. Good retro items
Coding days
Why:
Metric:
Settings to Apply:
...
Pull request response time
...
Why:
Metric:
Settings to Apply:
...
Refined backlog ready to work
...
Why:
Metric:
Settings to Apply:
Try burndown with filters to match team’s backlog
Pick an issue state that represents refined work.
By story points
Open defects by priority
...
Why:
Understand how quality is impacted by your focus on efficiency and speed.
...