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.

The Role Of Leadership - Agile 2007

Posted by Ben Hughes on Aug 17, 2007

Sections
Process & Practices
Topics
Change ,
Teamwork ,
Agile
Tags
Coaching and Mentoring ,
Self-organizing Team ,
Patterns and Practices ,
Conferences
Mary Poppendieck spoke with her usual energetic style yesterday at Agile 2007 on the role of leadership in software development, walking the attendees through a brief history of production management.  Mary walks through understanding the problem domain of effective leadership, and providing plenty of supporting quotes:
We get brilliant results from average people managing brilliant systems. Our competitors get average results from brilliant people working around broken systems. - Fujio Cho, Chairman Toyota Motors
Mary went on to talk about the application of lean management principles, using related case studies to demonstrate their application in the real world, including the importance of committing to plans, keeping teams fully utilized through preservation of learning and measuring the effects of change.

Mishkin Berteig blogged the presentation in detail, providing some insightful commentary. You can pick up a copy of the slides here, InfoQ will be presenting the video of the talk later this year.



Update: Mary's slides have been posted on the conference site.
  • 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!

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

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.