Beta This is new guidance. Complete our quick 5-question survey to help us improve it.
Measuring and reporting progress
Good reporting helps senior responsible officers (SROs) and service managers make decisions and give feedback when necessary. It should show a clear view of progress without creating any extra work for the team.
Meeting the Digital Service Standard
- setting clear and measurable goals
- communicating progress regularly and clearly
- being able to adapt quickly to changing circumstances
Measuring and reporting progress in agile
Measuring and reporting progress are built into agile ways of working so service teams will continuously produce the data you need. This includes:
- continuous planning - setting a vision, goals and objectives, developing a roadmap and tracking progress against them
- visual management - team walls and a backlog open to everyone
- face to face meetings - standup, show and tell, retrospectives for the team and the rest of the organisation
If you think you need extra reporting, make sure it’s really necessary and adds value. Too many reporting requirements become counterproductive as the team has less time to spend on delivery work. This is especially important for you to transition from one phase to another without the team losing momentum.
Reporting when you have more than one team
If you’re working with more than one team on a service, having some consistency in how they report means you can more effectively:
- see progress
- support service teams
- make informed decisions
- communicate with the rest of your organisation (and the public) about the service
Don’t try to force more consistency than is practical because the circumstances of each team will be different.
The following guides have more information on governing agile teams:
- Published by:
- Agile delivery community
- Last update:
Guidance first published