Are You Measuring What's Done or What's Left?

Johanna at Managing Product Development asks, Are You Measuring What's Done or What's Left? I'm at PNSQC this week. I gave my metrics talk yesterday, and something occurred to me: in traditional projects, we're used to measuring what's been done. In agile projects, we measure what's left to do. I just realized yesterday that the difference in how we measure makes a difference in how people feel about the project. The more you measure what's left, the more you can see the end of the iteration or the end of the project. It's also a lot clearer to see how many more iterations it will take if management decides to add more features. I'll be modifying my measurements--even for not-specifically-agile projects--to reflect what's left to do, not what's done.

Steve Johnson

Steve Johnson

Steve Johnson was a founding instructor at Pragmatic Institute, a role he held for more than 15 years before he left to start Under10 Playbook. In his return to Pragmatic Institute, Steve supports the complete learning path for product teams, ensuring they are fully armed for success. 

Over the course of his career, Steve has helped thousands of companies and tens of thousands of product professionals implement product management processes. He has worked in the high-tech arena since 1981, rising through the ranks from product manager to chief marketing officer. Steve has experience in technical, sales and marketing management positions at companies that specialize in both hardware and software. In addition, he is an author, speaker and advisor on product strategy and product management.

(0) Comments

Looking for the latest in product and data science? Get our articles, webinars and podcasts.