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.

Interview: Johanna Rothman on Schedule Games and other Organizational Dysfunctions

Posted by Deborah Hartmann Preuss on Mar 13, 2008

Sections
Process & Practices
Topics
Agile ,
Leadership
Tags
Management ,
Planning ,
Book
Johanna Rothman is an organizational consultant and coach, author of several books for managers in technical environments, and co-creator of the AYE (Accelerate Your Effectiveness) conference. Deborah Hartmann interviewed Johanna Rothman at Agile2007 about her third book - and discovered that there are names for some of the the scheduling games we all groan over, when they surface in our organizations: including Bring Me A Rock, Queen of Denial and Pants on Fire!

Rothman's books come from hard-won experience:
What I focus on is risk: whether it is risk in the people that you have in the project, risk in how you manage the people on the projects, or the risk in the projects themselves. And that’s what I do; help people see it help people manage it. Some of it is coaching; there are certainly workshops and training. I do assessment to really see what’s going on and what are the causes. Because you can have many number of symptoms that come from very different root causes. And you want to know what is causing it here and now.
Her third and latest book, Manage It. Your Guide to Modern Pragmatic Project Management, presents strategies for helping less-than-Agile organizations benefit from some common-sense practices used by Agile teams, including iterative and incremental development, even if they are resistant to whole-hog implementation, or for other reasons cannot implement a fully Agile approach:
Because: there are many organizations where the whole pattern doesn’t fit, where either the people won’t work in an Agile way, or they say: “No, get out the garlic and the crosses, the Agile people are hackers”. I don’t want to fight with everybody and I don’t want to label. I want to help people do what’s most effective for them.
That being said, it's hard not to notice  that the strategies she offers would address some Agile teams' problems, too!
That was why I put the schedule games chapter in, because I think if people have a name for something, even if it’s a team who says: “Oh, our VP Joe is playing “Bring me a Rock” or “Queen of Denial” – which is yet another schedule game – at least you have a common vocabulary. And having a fun name, with cartoons (I actually had a cartoonist draw some cartoons for that chapter), I think helps people get a little prospective on it.
Her chapter on "Recognizing and Avoiding Schedule Games" includes multiple strategies to try when these games surface within teams or organizations. Teams implementing Agile often find themselves faced with these games, and enormous energy can be spent trying to combat, adapt to, or circumvent them. Her list of games includes:

6.1  Bring Me a Rock
6.2  Hope Is Our Most Important Strategy
6.3  Queen of Denial
6.4  Sweep Under the Rug
6.5  Happy Date
6.6  Pants on Fire
6.7  Split Focus
6.8  Schedule Equals Commitment
6.9  We’ll Know Where We Are When We Get There
6.10  The Schedule Tool Is Always Right
6.11  We Gotta Have It; We’re Toast Without It
6.12  We Can’t Say No
6.13  Schedule Chicken
6.14  90% Done
6.15  We’ll Go Faster Now
6.16  Schedule Trance

"Schedule Games" is just one area covered in this book. The table of contents includes:
  • Starting a Project
  • Planning the Project
  • Using Life Cycles to Design Your Project
  • Scheduling the Project
  • Estimating the Work
  • Recognizing and Avoiding Schedule Games
  • Creating a Great Project Team
  • Steering the Project
  • Maintaining Project Rhythm
  • Managing Meetings
  • Creating and Using a Project Dashboard
  • Managing Multisite Projects
  • Integrating Testing into the Project
  • Managing Programs
  • Completing a Project
  • Managing the Project Portfolio
Listen to the interview to hear where the book came from and how it can benefit a broad range of organizations: Johanna Rothman: Agile Risk Reduction for Traditional Teams
  • 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!

You should listen to Johanna by Guy Nirpaz Posted
  1. Back to top

    You should listen to Johanna

    by Guy Nirpaz

    Me and my team had the pleasuere to meet with Johanna in various occasions. The influence this woman has on our success is amazing.

    Not only she's doing a great job at writing book, she's also very pragmattic and anti-dogmatic.

    I advise on reading her books and listen to what she has to say, as I personally learned a lot.

    Guy

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.