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.

Leadership is not Obsolete for Self-Organizing Teams!

Posted by Deborah Hartmann Preuss on Nov 27, 2007

Sections
Process & Practices
Topics
Leadership ,
Agile ,
Teamwork
Tags
Management ,
Value & Metrics ,
Lean ,
Agile2007 ,
Kaizen ,
Toyota Production System
In this popular talk from Agile2007, The Role of Leadership in Software Development, Lean software thought leader Mary Poppendieck reviewed the last century's managment theories, including Taylor, Toyota and Deming, and went on to talk about "the matrix problem", alignment, waste cutting, planning, standards and other topics including the role of measurement: "cash flow thinking" over "balance sheet thinking".

It is generally acknowledged that Japanese innovations in management raised the bar for manufacturing internationally in the 1980s:
“Only after American carmakers had exhausted every other explanation for Toyota’s success – an undervalued yen, a docile workforce, Japanese culture, superior automation – were they finally able to admit that Toyota’s real advantage was its ability to harness the intellect of ‘ordinary’ employees.”
-- Gary Hamel, “Management Innovation,” Harvard Business Review, February 2006
Poppendieck, formerly a process control engineer, participated in the change from statistical process control to Lean-style manufacturing processes at 3M. Her experiences there of excellent teamwork, improved productivity and continual improvement spurred her on to develop a similar approach for software development, resulting in her first book with husband Tom, called Lean Software Development: An Agile Toolkit.

Laughingly calling this her "controversial talk," Poppendieck skipped her usual intro-to-Agile slides and dove directly into her current research on leadership. Starting with Frederick Winslow Tayor's assumtions (circa 1900) that "workers will do as little as possible, and workers do not care about quality," she traced changes in management theory through Charles Allen's industrial on-the-job training in the '20's (exported to Japan after the second world war), the Toyota Production System (springboard for the ideas of Lean Manufacturing and Lean Product Managment today), and Charles Deming's formulation of Systems Thinking in the '80s.



Poppendieck summarized this history into three styles of leadership: 1) Old “Dictator” Style: “Do it my way…”; 2) 1980s “Empowerment” Style: “Do it your way... ”; 3) Lean Style: “Follow me…and let’s figure this out together.”

Within the Toyota Production System, the role of the leader is:
  1. to act as a teacher;
  2. to get each person to take the initiative to solve problems and improve his or her job; and
  3. to ensure that each person’s job is aligned to provide value for the customer and prosperity for the company
The section on standards was quite entertaining: the Lean idea of standards is subtly different from what many assume in North America. Rather than defining the performance threshhold (perform up to this standard, and you're OK), it is seen as the minimum threshhold: if you are still only meeting this standard in a month, then you've not improved, you are a "salary thief"! According to Taiichi Ohno, standards only serve as a baseline for improvement:
There is something called standard work, but standards should be changed constantly. Instead, if you think of the standard as the best you can do, it’s all over. The standard work is only a baseline for doing further kaizen. It is kai-aku [change for the worse] if things get worse than now, and it is kaizen [change for the better] if things get better than now. Standards are set arbitrarily by humans, so how can they not change?

When creating Standard Work, it will be difficult to establish a standard if you are trying to achieve ‘the best way.’ This is a big mistake. Document exactly what you are doing now. If you make it better than it is now, it is kaizen. If not, and you establish the best possible way, the motivation for kaizen will be gone.
The leader's job is to help people follow standards which they themselves made, and to guide them in continually improving their work, thereby evolving and updating their own standards.

View the InfoQ video of Mary Poppendieck's 90-minute talk from Agile2007: The Role of Leadership in Software Development.
  • This article is part of a featured topic series on Agile
It's would be nice to have it as mp3 file by Andrey Izmaylov Posted
Re: It's would be nice to have it as mp3 file by Floyd Marinescu Posted
Re: It's would be nice to have it as mp3 file by Niels Tindbæk Posted
Re: It's would be nice to have it as mp3 file by Floyd Marinescu Posted
  1. Back to top

    It's would be nice to have it as mp3 file

    by Andrey Izmaylov

    It's would be nice to have it as mp3 file

  2. Back to top

    Re: It's would be nice to have it as mp3 file

    by Floyd Marinescu

    Hi Andrey, we plan to do this soon, look out for it in January.

  3. Back to top

    Re: It's would be nice to have it as mp3 file

    by Niels Tindbæk

    That sounds great - i'm really looking forward to being able to download the content.

  4. Back to top

    Re: It's would be nice to have it as mp3 file

    by Floyd Marinescu

    Unfortunately this has been pushed back, instead we're gonna fix our videos in general by migrating to a new platform that will solve our runtime problems people have complained about.

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.