360 reviews with the team, OKRs, amount of input the person has on the team. How influential are they at helping get working code out the door. Agile shines a light on the fact that performance isn’t a quantative thing in knowledge work especially when embedded in a team. Its the same reason they stay away from sizing in hours, to get away from quantative judgements. Reviews should be how the person feels they could help the team better either by focusing inward and setting up skills they want to improve or outward by mentoring or being more active in the team.
What review metrics are most effective for Agile?
Reviews do allign closely with the agile manifesto, but what kind of metrics can be effectively related for Agile development?
Agile metrics help agile development teams and their management measure the development process,
gauging productivity, work quality, predictability, and health of the team and products being developed.
A key focus of agile metrics is on value delivered to customers – instead of measuring “what” or
“how much” we are doing, we measure how it impacted a customer.
Some of the Agile Core Metrices
- Effort & Schedule
- Productivity - Velocity based
- Sprint Burndown Performance Indicator
- Release Burnchart Performance Indicator
- Release Slippage Risk Indicator
- Story Point Effort Performance Indicator
- Scope Management
- Scope Volatality
- Running Tested Features