Team Guide to Metrics for Business Decisions
Team Guide to Metrics for Business Decisions
Minimum price
Suggested price
Team Guide to Metrics for Business Decisions

This book is 90% complete

Last updated on 2019-10-02

About the Book

Team Guide to Metrics for Business Decisions is the second guidebook in the new collection from Skelton Thatcher Publications.

Learn how metrics can help your software team answer questions like “How fast are we going? What should we do next? Where’s the bottleneck?” Deliver software more effectively with greater certainty.

The ‘Team Guide’ collection is designed to help teams building and running software systems to be as effective as possible. Guides are curated by experienced practitioners and emphasise the need for collaboration and learning, with the team at the centre.

About the Authors

Mattia Battiston
Mattia Battiston

Mattia is originally from Verona, the city of love and home of Romeo of Juliet. He is a software developer and team leader with a great passion for learning and continuous improvement.  

His focus is to help teams strive to get better, using Kanban, Lean, Agile, and of course a lot of data and metrics.

He's been interested in everything to do with Agile since the beginning of his career in 2008. He loves attending and speaking at conferences and meetups for sharing experiences and learning from each other.

Chris Young
Chris Young

Chris has been a computerist since age 12 when he was introduced to the magic of the Commodore PET. He works with engineering and

management teams with the aim of getting the best results possible for all involved.

The role and value of metrics in this came from discovering the Lean/Kanban community around 2010 which got him measuring things in earnest.

He is an active member of the Lean/Agile/DevOps community speaking at Meet Ups and conferences across Europe including GOTO Berlin, Agile Cambridge, CukeUp and QCon.

Bundles that include this book

Team Guide to Software Operability
Team Guide to Metrics for Business Decisions
Team Guide to Software Testability
Team Guide to Software Releasability
Suggested Price
Bundle Price

About the Contributors

Manuel Pais
Manuel Pais

Manuel Pais is an independent DevOps and Delivery Consultant, focused on teams and flow.

With a diverse experience including development, build management, testing and QA, Manuel has helped large organizations in finance, legal, and manufacturing adopt test automation and continuous delivery, as well as understand DevOps from both technical and human perspectives.

Manuel is co-author of the Team Guide to Software Releasability book and lead editor for the remaining books in the Team Guide series.

Table of Contents

  • Team Guides for Software
  • Foreword
  • Introduction
    • What is covered in this book
    • All the time in the world
    • Value, quality and operational metrics
    • How to use this book
    • Get Started!
    • Feedback and suggestions
  • 1. Throughput: How fast are we going?
    • 1.1 Why should I care about throughput in my team role?
    • 1.2 What’s the problem with velocity and story points?
    • 1.3 What is throughput?
    • 1.4 Use throughput for short term predictions
    • 1.5 Use throughput to validate experiments
    • 1.6 Use throughput for long term predictions
    • 1.7 Debunking some myths
    • 1.8 Public resources
    • 1.9 Get started!
    • 1.10 Summary
  • 2. Lead Time: How long will this take?
    • 2.1 Why should I care about lead time in my team role?
    • 2.2 What is lead time?
    • 2.3 Measuring lead time
    • 2.4 Use lead time to make predictions
    • 2.5 Use lead time to answer business questions
    • 2.6 Use lead time for continuous improvement
    • 2.7 Use lead time to answer “What should we work on today”?
    • 2.8 Debunking some myths
    • 2.9 Public resources
    • 2.10 Get started!
    • 2.11 Summary
  • 3. Metrics for Quality: How do we know this works?
    • 3.1 Why should I care about metrics for quality in my team role?
    • 3.2 What do we mean by quality?
    • 3.3 Use quality metrics to identify the needs of various groups of people
    • 3.4 Use quality metrics to discover who is affected by quality
    • 3.5 Use quality metrics to identify and reduce Failure Demand
    • 3.6 Use quality metrics to tell compelling stories to the right people
    • 3.7 Debunking some myths
    • 3.8 Get started!
    • 3.9 Summary
  • 4. Forecasting and Planning: When will it be done?
    • 4.1 Why should I care about forecasting in my team role?
    • 4.2 The common way of estimating in agile teams
    • 4.3 How long will this feature/project take?
    • 4.4 Answering business questions with probabilistic forecasting
    • 4.5 Forecasting tips & tricks: how to improve your forecasts
    • 4.6 Estimate vs forecast: benefits of forecasting
    • 4.7 Debunking some myths
    • 4.8 Public resources
    • 4.9 Get started!
    • 4.10 Summary
  • 5. Metrics for Flow: Where is the bottleneck?
    • 5.1 Why should I care about flow in my team role?
    • 5.2 What is flow
    • 5.3 Use a cumulative flow diagram to answer: Is work flowing well?
    • 5.4 Use net flow to answer: Is our process balanced?
    • 5.5 Use flow efficiency to improve the end-to-end process
    • 5.6 Public resources
    • 5.7 Get started!
    • 5.8 Summary
  • 6. Metrics for Value: Is this worth doing?
    • 6.1 Why should I care about metrics for value in my team role?
    • 6.2 What are metrics for value?
    • 6.3 Provide a foundation of operational and quality metrics
    • 6.4 Measure usage: is anyone using it?
    • 6.5 Use the Pirate Metrics: AARRR
    • 6.6 Make your customers part of the decision-making process
    • 6.7 Expect to keep learning and adapting
    • 6.8 Debunking some myths
    • 6.9 Get started!
    • 6.10 Summary
  • Terminology
  • References and further reading
    • Introduction
    • Chapter 1 - Throughput
    • Chapter 2 - Lead Time
    • Chapter 3 - Metrics for Quality
    • Chapter 4 - Forecasting and planning
    • Chapter 5 - Metrics for Flow
    • Chapter 6 - Metrics for Value
  • About the authors
    • Mattia Battiston
    • Chris Young
    • Why we wrote this book
  • Conflux Books

About the Publisher

This book is published on Leanpub by Skelton Thatcher Publications

Developing and running modern software systems requires teams of motivated and well-trained people. The Team Guide series from Skelton Thatcher Publications takes a team-first approach to software systems with the aim of empowering whole teams to build and operate software systems more effectively. Part of Conflux Books.

Authors have earned$9,522,389writing, publishing and selling on Leanpub,
earning 80% royalties while saving up to 25 million pounds of CO2 and up to 46,000 trees.

Learn more about writing on Leanpub

The Leanpub 45-day 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub