Straightening out your value stream

The value stream is the set of actions that take place to add value to a customer from the initial request to delivery. The value stream begins with the initial concept, moves through various stages for one or more development teams (where Agile methods begin), and on through final delivery and support.

Value streams are what they are, you don’t specify them. There are several ways to change them, however, including changing:

  • what goes into them
  • how people collaborate
  • the order of the work (e.g., test-first)
  • how teams are organized, the size of the work done
  • the amount of work being done by the people in the value stream

The idea is to remove handoffs, delays and handbacks in the value stream. Doing so will lower cycle times and increase process cycle efficiency resulting in quicker time to market and realization of value.

Handoffs, handbacks, holdups and multi-tasking- discovering impediments without value stream mapping

Back in 2006, I would always incorporate value stream mapping into the training or engagement. Over the years, however, as Scrum teams have become predominant, I have found doing to to be of less value. Not because value stream mapping isn’t important – it is, but because people don’t seem to be able to do it well.

Continue reading “Handoffs, handbacks, holdups and multi-tasking- discovering impediments without value stream mapping”

What role do value streams play in your approach?

To be clear, I am referring to Lean’s (not SAFe’s) definition of the value stream – the set of actions that take place to add value to a customer from the initial request to delivery. The value stream begins with the initial concept, moves through various stages for one or more development teams and on through final delivery and support. You can’t define value streams – they are what is. You can, however, map them, define a “to be” value stream and you can improve them.

Continue reading “What role do value streams play in your approach?”