InfoQ

News

Impediments To Your Value-Stream

Posted by Mike Bria on Apr 28, 2008 04:36 AM

Community
Agile
Topics
Delivering Value,
Agile in the Enterprise,
Agile Techniques
Tags
Business/IT Alignment,
Lean,
Retrospectives
Scrum defines an impediment as "anything keeping the team from being more productive" and clearly stresses that teams establish means to remove them as continuously as possible. Joe Little proposes an impediment's scope may be better established as being anything keeping the organization from delivering value.

In a post early in the week Little posed his thoughts on why velocity is an important metric to an agile team. In short he points out three items:
  • Defense: Velocity gives the team legitimate ammunition to say no (or yes) to managers and customers
  • Justification: Velocity metrics help manager's more comfortably accept explanations of why agile is important
  • Challenge: Velocity gives the team a bar by which to gauge efforts to remove impediments
Shortly thereafter Little took a deeper dive into the sub-theme of this third item: impediment hunting. He asks "What is the scope that defines what might be an impediment?", then goes on to challenge that the generally accepted agile view may be missing the mark.
By definition in Scrum, an impediment is anything that keeps the team from being more productivity. And I personally add that everything is imperfect, so by my definition everything is an impediment to some degree, and the trick is to identify the one or two biggest impediments today.

Scrum has also said that the scope is wide, including such diverse things as engineering practices and personal issues.

What I have not seen talked about much is the scope from an end-to-end Value Stream perspective. So, I would argue that anything that reduces the business value of what the Team produces (or the speed with which the value is realized) is an impediment.
Little follows with an example of a development team whose building software that their partner "implementations/install" team is not ready to install. In this case, the team's DONE, but zero true business value has been realized. Little's assertion is that the implementions hold-up is the most important impediment and that the development team would be wise to put some energy into seeing it removed.

What Little is saying hits on the fundamental premises of the systems-thinking characteristic of Lean software development made popular in recent years by Mary and Tom Poppendieck, Kenji Hiranabe, and others.  In short, the message is to prevent localized optimization by understanding your overall value-stream and removing impediments wherever they may land on it.

RelatedVendorContent

The Agile Business Analyst: Skills and Techniques needed for Agile

Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21

Agile Tool Evaluation Guide

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Reply

Exclusive Content

Rob Windsor on WCF with REST, JSON and RSS

WCF is not just for SOAP based services and can be used with popular protocols like RSS, REST and JSON. Join Rob Windsor as he introduces WCF 3.5 and its new native support for non-SOAP services.

Christophe Coenraets Discusses Flex 3, AIR, and BlazeDS

Christophe Coenraets discusses Flex 3, Flex Builder, AIR, BlazeDS, Adobe and open source, integrating Flex with existing applications, and integrating RIAs with search engines and browsers.

Debunking Common Refactoring Misconceptions

Danijel Arsenovski attempts to dispel some of the myths around refactoring and how it applies to .NET developers.

REST Eye for the SOA Guy

In this presentation, recorded at QCon San Francisco, CORBA guru Steve Vinoski explains REST from the view of someone who comes to SOA from a traditional, RPC-oriented background.

Choose Feature Teams over Component Teams for Agility

Feature teams are key to scaling agility for large teams. In an excerpt from "Scaling Lean and Agile Development," Larman & Vodde show how feature teams resolve traditional problems & raise new issues

Billy Newport explains Virtualization

Billy Newport talks about virtualization, eXtreme Transaction Processing (XTP) and WebSphere Virtual Enterprise. He discusses hardware, hypervisor, JVM, application and data virtualization.

Virtualization and Security

While virtualization provides many benefits, security can not be a forgotten concept in its application.

Introduction to Agile for Traditional Project Managers

This session is specifically aimed at traditionally trained project managers who are new to Agile, and who would like to be able to relate the PMI's best practices to their Agile equivalents.