InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Without a Defined Process, How Will We Know Who To Blame?

Posted by Deborah Hartmann Preuss on Sep 28, 2007

Sections
Process & Practices
Topics
Leadership ,
Agile ,
Change
Tags
Toyota Production System ,
Continuous Improvement ,
Criticism ,
Value & Metrics ,
Lean ,
Management
"A fundamental premise of the 'train-wreck' approach to management is that the primary cause of problems is 'dereliction of duty'" said Peter Scholtes in The Leader's Handbook. Under this "management by results" approach, fear of blame drives compliance and performance. Prompted by a discussion on the LeanDevelopment discussion group,  Mary Poppendieck posted a short article, Train-Wreck Management, on process, people and systems. In it she looked at Sholtes' book, Deming, the Toyota Production System (TPS) and how Lean provides an alternative to the culture of blame.

It's tempting to think that formalised collaborative approaches represent a change from "how things have always been done," but the predominant paradigm may not be as old as we think. From the beginning of Poppendieck's article:
As business grew and became geographically disperse in the 1800's, a way to run these businesses had to be found. But there were no models outside the church and the military, so investigators into the train-wreck disaster [of 1841, in New York state] looked to the Prussian army for a model. And there they found the classic organization chart - the one we know so well today. Scholtes calls it the "train-wreck" chart. It was revolutionary at the time.
So, is a heirarchical organisational structure the root of all evil? The article also included an interesting quote from Scholtes:
All of the empowered, motivated, teamed-up, self-directed, incentivized, accountable, reengineered, and reinvented people you can muster cannot compensate for a dysfunctional system.... A well-run organization with well-functioning systems allows people from top to bottom do work of which they can be proud.
Poppendieck's question: "So where does this leave us? Which is more important - process or people?" It looks like the answer might be "both." She concluded:
People like to use effective processes, and they also like to have control over their own environment. The Toyota Production System provides for both. [Taiichi] Ohno made it clear that people must be at the center of improving their own processes.
Apparently, while simply "empowering teams" doesn't seem to be the solution, neither does a focus on pure process, divorced from the people-driven "continuous learning" cycle. Scholtes suggested that corporate attempts to impose certified process improvement programs like ISO 9000 across large organisations may be missing the point. What's missing? Those "home grown," self-organizing aspects that would allow these approaches to evolve and improve teams in different and appropriate ways. From Scholtes' critique:
  • Assessment has a tone of paternalism and mistrust - it replaces internal motivation with external motivation.
  • [Process] certification is not equal to satisfied customers - you can do the wrong thing as long as you do it consistently.
  • A certified process is difficult to change - Ohno would be appalled.
Poppendieck's article is worth reading, particularly for those readers currently contemplating creation of a Lean or Agile Certification program or Agile PMO (Project Management Office).
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Non-co-located teams by Deborah Hartmann Posted
Carnival of Blame by Deborah Hartmann Posted
  1. Back to top

    Non-co-located teams

    by Deborah Hartmann

    I call them "dis-located" teams, sometimes :-)

    Isn't it interesting that this org-chart driven pattern came about in answer to: "business grew and became geographically dispersed..." ?

  2. Back to top

    Carnival of Blame

    by Deborah Hartmann

    I just came across this roundup on Kevin Rutherford's "silk and spinach" blog.

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.