6 Powerful Agile Metrics


Presentation Description

What is agile? It is an approach to software development that requires a huge dependence on collaboration between self-organizing cross-functional teams, developers and costumers. What makes the agile development stand out from other approaches to software development is that it focuses on how each team works and how they work together. This promotes the utilization of practices and framework for every team. This method of development is aligned to the four foundational values of the Agile Manifesto and its 12 principles. Some of the metrics you need to consider for agile development are escaped defects, sprint burndown, velocity, failed deployments, lead time, and cycle time.


Presentation Transcript

slide 1:

Powerful Agile Metrics Smoothstack Agile http://sstack-agile.com/

slide 2:

AGILE METRICS According a Smoothstack agile metrics are an important part of an agile development team. They help measure development process monitor productivity work software quality as well as predictability and health of products and development team.

slide 3:

Here are 6 of some of the metrics you need to consider for agile development.

slide 4:

ESCAPED DEFECTS This helps identify the number of bugs after a build or release enters production. This metric should always be considered. Bugs after production always cause problems. • Why it is powerful: Production bugs especially if frequent are a problem in the agile process. Just like in lean manufacturing we should “stop the production line” and discover what’s wrong.

slide 5:

SPRINT BURNDOWN Scrum teams organize development into time- boxed sprints. This metric is usually presented as chart. It tracks the number of completed story points and ensures the team will complete the sprint scope in a given time. • Why it is powerful: Makes it instantly clear how much value a sprint has already delivered and how close we are to completing our commitment to customers.

slide 6:

AGILE VELOCITY This measures the average story point completion of a team over several past sprints. This is a powerful metric because it can be used to predict how effective a team can be in upcoming sprints. • Why it is powerful: Velocity is powerful because it’s a result metric – how much value was actually delivered to customers in a series of sprints. Be careful not to compare velocity across teams because story points and definition of done can vary between teams.

slide 7:

FAILED DEPLOYMENTS This allows agile teams to access the overall number of deployments to either testing and production environments or both. This also determines whether or not the sprints or releases are ready for production. • Why it is powerful: Especially when applied to production environments this metric can provide a clear indication that sprints or releases are production ready or not.

slide 8:

LEAD TIME Lead time measures the total time of a story from the point it enters the backlog until the sprint end and release to the customer. It measures the total time for a requirement to be realized and start earning value – the speed of your value chain. • Why it is powerful: In a sense lead time is more important than velocity because it measures the entire agile system from end to end. Reducing lead time means the entire development pipeline is becoming more efficient.

slide 9:

CYCLE TIME This will help you measure the time or average speed a team does a task from start to its completion. Cycle time lets you identify arising bottlenecks quickly. Normally cycle times should be around half the sprint length. • Why it is powerful: A very simple metric that can raise a red flag when items within sprints across your entire system are not moving forward.

authorStream Live Help