Hakkiri does multiple levels of analytics and metrics to help enable you to focus on the right areas of improvement. The delivery scores give a look at different dimensions of execution and scores them in a traditional 5 star system for easy consumption.
Planning
Purpose:
- To give a sense of how well teams are doing at planning and backlog management
Factors that impact this score:
- Sprints planned into the future
- Amount of refined/groomed backlog that is ready for execution
- Descriptions on stories and epics
- Sprint Goals
Things you can do to improve the score:
- Work with the team and refine more stories with estimates
- Create sprints for future iterations and assign stories to them
- Ensure you have clear descriptions on Epics and Issues
- Set a goal for a Sprint that drives the planning/priorities of the Sprint
Execution
Purpose:
- To give a sense of how well teams are reliably delivering on their commitments
Factors that impact this score:
- Teams delivering on their commitments
- How well sprints stick to their time box
- Executing on very long sprints
Things you can do to improve the score:
- Ensure sprints stop on their scheduled date and don't run over
- Stay focused on your sprint deliverables and strive to meet them
- Minimize roll over of issues from one sprint to the next
- Limit work in progress -- better to get fewer issues completely done than a lot in progress
Quality
Purpose:
- To give a sense on the overall bugs in backlogs and how much focus is on reducing them
Factors that impact this score:
- How much the backlog is made up of bugs
- How the team is balancing fixing bugs vs working on stories
Things you can do to improve the score:
- Review the bugs in your backlog, ensure they are valid and not duplicated, close otherwise
- Spend a few sprints (or period of time) focusing on bug burndown
Process
Purpose:
- Effective processes enable teams to deliver and coordinate with minimal friction. They facilitate delighting customers through reliable delivery of high quality software.
Factors that impact this score:
Scrum Teams:
- Consistency of start and end dates for sprints
- Consistency of sprint duration
- Sprints run 2 weeks or less
All Teams:
- Utilization of Epics to group work
Things you can do to improve this score:
- Utilize consistent sprint start and end days. It is recommended to utilize Tuesday or Thursday to minimize ceremony disruption due to Holidays and extended weekends.
- Do not plan sprints longer than 2 weeks. More than 2 weeks typically does not give enough opportunities to adapt to new information.
- Ensure issues are assigned to Epics in the backlog.
Overall
Purpose:
- To give an overall score across all of them
Factors that impact this score:
- The Planning, Execution, Quality and Process scores
Things you can do to improve the score:
- Improve the Planning, Execution, Quality, and Process scores
Comments
0 comments
Please sign in to leave a comment.