Reimagining ALM

| by Jaume Jornet Follow 0 Followers on Jul 17, 2013. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Sam Guckenheimer proposes in his recent keynote at ALM Summit 3 to reimagine the application lifecycle management (ALM) to enable continuous feedback on software projects with a metric based on how long it takes to drive an experiment and obtain validated learning from it.

Guckenheimer, Group Product Planner of the Microsoft Visual Studio product line and author of several books on application lifecycle management, in order to incorporate continuous business improvement to our improvement cycle proposes to add the measurement to what he exposes as the two basic metrics for continuous flow in application lifecycle management:

  • Cycle time, as the time one feature takes to arrive from product backlog to production
  • And Mean time to repair, the time it takes to resolve an issue at production from when it was detected until it’s fixed.

On his keynote, Guckenheimer discuss how the underlying idea ‘Stop doing Product Development, start doing Customer Development’ on books like ‘The Four Steps to Epiphany’ by Steve Blank, and specially the publication of ‘The Lean Startup’ book by Eric Ries, changed the way we talk about Lean. According to author previously we used to talk Lean as the Toyota tradition started by Taiichi Ono, and nowadays we define Lean in a whole different way, as the Lean Startup business practices based on ‘Build. Measure. Learn’.

Starting from what he calls the Agile Consensus - trustworthy transparency, reduction of waste and focus on the flow of value - as the way to teach companies better product development, he provides six simple steps that will allow organisations to incorporate ‘Build. Measure. Learn.’ on their projects:

  1. Make business hypothesis a testable experiment
  2. Define experiment as Minimum Viable Product (MVP)
  3. Build measurement into MVP
  4. Measure the results
  5. Gain validated learning
  6. Persevere or pilot.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you