Agile practice | agile indicators to improve group predictability

Write it at the front ：

When deciding what to measure , First of all, there must be a The goal is . The second is how to measure the achievement of this goal , Here we are going to talk about 「 indicators 」.

In terms of agile development , Customer and team support for agile development 「 Predictability 」 Pay special attention to . because Without a stable and predictable team, there can be no predictable project , Especially when there are multiple dependencies between teams .

In every sprint （sprint） Be able to keep your promise at the end , Delivery on schedule , This is what our team and customers are happy to see . from 「 Predictable agility indicators 」 Set out to , This paper focuses on how to ensure the stable output of the team and set achievable goals 5 A direction . here , Let's call this 5 An agile indicator .

Let's see if our team ：

• sprint （sprint） The expected delivered functions are provided before the start ？

• The delivered code has been rigorously tested and repaired ？

• Hope to use sprint to arrange work ？

• Confident in providing expect Released features ？

• A stable iteration period is formed ？

We use the following agility metrics to answer these questions ：

indicators 1>>  Completion rate of stories and points

• Number of stories actually delivered / The number of stories promised

• Points actually delivered / Promised points

This indicator helps the team evaluate and develop a sprint plan .

「 The story 」 Small ,「 sprint 」 The preparatory work should be as detailed as possible , This is what we want . If not , This error should be within 10% within .

indicators 2>>  Speed and yield changes

• Recent speed / Average speed

• Recent production / Average production

This indicator helps the team better measure their output . This indicator can help the team manage risks and dependencies before sprint , Avoid over commitment , The error should be controlled within 20% within , The deviation of speed should be smaller and smaller over time .

indicators 3>>  Lead time

• WIP（ In the products ） Ratio to output

The more work in progress , With input The increase in costs , The output will be less , It also becomes a challenge for developers . Our goal is to start from “ Be ready ” To “ deliver ” Should not exceed 4 Zhou , It is best to Two weeks or less .

indicators 4>>  Team member availability

• Actual number of people available / Expected number

Stability is crucial to an agile team , When team members are pulled into multiple teams or cannot work as planned , The team is also unlikely to 「 Proceed as originally planned 」. Agile teams need to be reminded of this , And control this change In the planned 10% within .

indicators 5>>  Release confidence

• Evaluate the team's confidence in achieving goals through internal perspectives and records

We can use consensus voting to evaluate team confidence ：「1」 Show no confidence ,「5」 Very confident . The final score can record the current internal confidence of the team in achieving the goal .

If a team is heavily dependent , The agile project manager can vote ; If you lack a skill or a role , The team should consider the impact of this situation on a successful release , best Use burnout chart To track project progress .

In addition to the above 5 In addition to the two main indicators , Agile teams can also use 「 Quality indicators 」： Build frequency 、 Destroy build 、 Code coverage 、 Defect rate or technical debt, etc ; perhaps 「 product indicators 」： Remaining functions 、 Release function size, etc ; perhaps 「 Value indicators 」： Value realization time, etc . Use agile metrics responsibly , It can make the whole team master the ability to meet expectations , And improve the work in real time .

Learn more about agile development 、 project management 、 Industry trends and other news , Pay attention to our [LigaAI@oschina Or click on LigaAI- A new generation of intelligent R & D cooperation platform , Apply online to experience our products .