InfoQ

News

Leadership is not Obsolete for Self-Organizing Teams!

Posted by Deborah Hartmann Preuss on Nov 27, 2007

Community
Agile
Topics
Teamwork ,
Leadership
Tags
Value & Metrics ,
Lean ,
Management ,
Kaizen ,
Agile2007 ,
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.

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.

It's would be nice to have it as mp3 file by Andrey Izmaylov Posted Nov 28, 2007 3:11 PM
Re: It's would be nice to have it as mp3 file by Floyd Marinescu Posted Nov 28, 2007 4:46 PM
Re: It's would be nice to have it as mp3 file by Niels Tindbæk Posted Dec 23, 2007 8:51 AM
Re: It's would be nice to have it as mp3 file by Floyd Marinescu Posted Jan 21, 2008 2:21 PM
  1. Back to top

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

    Nov 28, 2007 3:11 PM 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

    Nov 28, 2007 4:46 PM 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

    Dec 23, 2007 8:51 AM 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

    Jan 21, 2008 2:21 PM 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

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.