Software delivery metrics

Like Print Bookmarks. May 05, 10 min read by Charlie Ponsonby. However, you may prefer to build your own bespoke metrics. Related Sponsored Content. Related Sponsor Free your apps. Simplify your ops. Author Contacted. Better Scrum through Essence. Introducing the Ionic 6 Component Framework. Moldable Development by Example. Differentiable Programming in Kotlin. Becoming a Better Tech Leader with Coaching. View an example Enter your e-mail address.

Select your country Select a country I consent to InfoQ. Hello stranger! Get the most out of the InfoQ experience. Tell us what you think. Email me replies to any of my messages in this thread. Community comments. Watch thread. Close Your Reply. Quote original message. Close OK. Information Security.

Data Integrations. Azure DevOps. Use cases overview. Planked is used in a variety of use cases: Reducing risk and improving effectiveness Effective Agile Governance Increasing team engagement. Case studies. Tracking and replicating high performing engineering teams Plandek at a financial software business.

Scaling up a new in-house delivery capability Plandek at Preqin. Customer Success Support. Customers include. Value Stream Metrics Today. Latest from our blog. See all blog posts Plandek launches LiveView to help teams optimise sprint performance Read. Other resources. Our mission. The application of data science to the challenge of optimising software delivery. Read our full mission. Join our team and help engineers deliver great software.

Plandek works with a network of trusted partners. Learn more. Blog How software delivery metrics can enhance engineer skill development and career progression. By Kerry Seaton — Agile Success Manager at Plandek The role of a software engineer in a delivery team, regardless of which methodology the team is working to, has 2 purposes.

Improving on traditional software engineering career progression Most organisations will have a career progression framework for the engineering community and it may have a step by step guide on what needs to be done to progress up through the ranks. Specific metrics to help software engineers career and skills development Key metrics for development can include reports such as Code Cycle Time , where you can drill into the time it takes to create and merge a pull request.

Not just delivery metrics: Plandek paints an overall picture of SDLC Plandek is more than just delivery related metrics. To find out more, book a demo or sign up today. Other blog posts. Plandek launches LiveView to help teams optimise sprint performance Read more. Implementing value stream metrics within a Value Stream Management framework Read more. Plandek Agile delivery metric of the week: Escaped Defects Read more.

Reporting as a Delivery Manager Read more. Plandek announces partnership and re-seller agreement with The Adaptavist Group Read more. Top 5 DevOps metrics that make an immediate impact Read more. Engineering metric of the week: Ticket Complexity Read more. Top 5 Value Stream metrics for teams and managers Read more. Top 5 Agile metrics for teams and managers Read more. Metric of the week: Speeding Transitions Rate Read more. Metric of the week: Deployment Frequency Read more.

Plandek metric of the week: Sprint Target Completion Read more. Plandek metric of the week: Delivery Lead Time Read more. Metric of the week: Flow Efficiency Read more. Read more. The vital importance of traceability in your software delivery Read more. Is this the most powerful Jira dashboard available to you? How to build an insight-driven delivery organisation and rapidly reduce Cycle Time Read more.

Using Plandek analytics and reporting to track and radically improve dependability, velocity and quality case study Read more. Plandek grows its U. Think again. Are you breaking down your stories enough?

The key questions you should be asking of your sprint metrics Read more. Plandek accelerates technology leadership with launch of Plandek NextGen platform Read more.

Another key area to consider in any diagnostic is the wellbeing of the teams themselves. Stressed teams are both a symptom of and a potential cause of problem projects.

As such there are several key people-oriented metrics to consider:. An inability to manage the backlog of work and estimate accurately are among the most common causes of problems in Agile software delivery — if teams are unable or unwilling to expend the time to plan future workload and estimate accurately - timing and capacity planning become very unreliable and short-term goals become very difficult to meet.

Analysis of backlog health metrics often provide a good proxy for likely estimation problems. Project delivery relies on the dependability of the scrum teams delivering the software. If individual teams are unable to reliably deliver their sprint goals typically a two-week commitment , then it is highly unlikely that longer term project goals often involving multiple teams and sprints , can be accurately met. Team dependability is a key building block of successful projects and hence a key focus in project recovery.

There are several metrics that are important to review in this regard. There are a number of DevOps metrics that help explain changes in Deployment Frequency which may also be reviewed. Another area worthy of investigation is the teams' approach to managing stories and tickets. It is a common feature of problem projects that tickets are ill-defined and tend to balloon in size.

This may be because certain individuals become siloed, working to solve engineering problems alone which in itself is a major red flag that needs identifying and resolving. Whatever the circumstance, overly complex stories are usually a recipe for quality and timing problem, as they not only introduce complexity for engineers but the whole delivery team through QA and release. It is a common scenario in problem projects that the delivery team start to generate bugs at such a rate that they generate excessive unplanned work to resolve them.

This is therefore a key area of analysis in problem project diagnosis. Important metrics to consider include:. Stakeholders moving the goal posts or changing the scope during the project is a very common source of angst. This may be hard to identify without time consuming investigation, but some simple metrics to consider here are:. Similarly, it is common for process delays to emerge from delayed inputs from stakeholders — e.

This is another area which is hard to measure quantitatively, but can be assessed through sustain delays in the delivery process e. A common frustration with problem projects is the lack of meaningful progress reporting.