Partial Commitments to Projects Create Unpredictable Projects - No Fluff Just Stuff

Partial Commitments to Projects Create Unpredictable Projects

Posted by: Johanna Rothman on April 15, 2009

There’s a discussion on a mailing list about a partially committed-to project: there aren’t enough people on the project, the people don’t have the time to do the work because they are interrupted all the time by support of previously released applications. The only people available are part-time people who are not available when the rest of the team is available.

Management has not committed to the project, nor to the team. In a spirit of generosity, let’s assume management is running too fast to think. If you have management like this, see if you can get them to sit still to remember their math. When a project is fully committed-to, each person on the project can supply an entire person’s worth of effort to the project. If you have 8 people, that’s 8 people’s worth of effort. But if you have 8 people, and each can supply only a half a person, you can get a maximum of 4 people’s effort minus the context switching cost. Adding more people who are only part time increases the number of communication paths (which decreases what any given person can do because of the time needed for communication) and decreases the total number of people available, because each person does more context switching.

Partially-committed projects are not projects you can predict anything about. Yes, they have people assigned to them. Yes, they even make some progress. But how can you predict anything about the project? You can’t use velocity, you can’t use the rate at which anything has been done, because you can’t tell if that rate can be repeated in the future. You can’t use an informal way to count features or phases, because your past project behavior is not predictive of future behavior.

If you want more predictable projects, the management team or some other leadership body must make decisions about whether to commit to a project or not. That’s what the project portfolio is all about. Without a portfolio, you have unpredictable projects. With a portfolio, you have a chance of predictability.

But what’s worse is the implicit message management says to the team. “This project is not important enough for us to commit to. But we want you to.” Not a good message.

Johanna Rothman

About Johanna Rothman

Johanna Rothman, known as the “Pragmatic Manager,” offers frank advice for your tough problems. She helps leaders and teams learn to see simple and reasonable things that might work. Equipped with that knowledge, they can decide how to adapt their product development.

With her trademark practicality and humor, Johanna is the author of 18 books about many aspects of product development. She’s written these books:

  • Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility
  • Become a Successful Independent Consultant
  • Free Your Inner Nonfiction Writer
  • Modern Management Made Easy series: Practical Ways to Manage Yourself; Practical Ways to Lead and Serve (Manage) Others; Practical Ways to Lead an Innovative Organization
  • Write a Conference Proposal the Conference Wants and Accepts
  • From Chaos to Successful Distributed Agile Teams (with Mark Kilby)
  • Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver
  • Agile and Lean Program Management: Scaling Collaboration Across the Organization
  • Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects, 2nd edition
  • Project Portfolio Tips: Twelve Ideas for Focusing on the Work You Need to Start & Finish
  • Diving for Hidden Treasures: Finding the Value in Your Project Portfolio (with Jutta Eckstein)
  • Predicting the Unpredictable: Pragmatic Approaches to Estimating Project Schedule or Cost
  • Manage Your Job Search
  • Hiring Geeks That Fit
  • The 2008 Jolt Productivity award-winning Manage It! Your Guide to Modern, Pragmatic Project Management
  • Behind Closed Doors: Secrets of Great Management (with Esther Derby)

In addition to articles and columns on various sites, Johanna writes the Managing Product Development blog on her website, jrothman.com, as well as a personal blog on createadaptablelife.com.

Why Attend the NFJS Tour?

  • » Cutting-Edge Technologies
  • » Agile Practices
  • » Peer Exchange

Current Topics:

  • Languages on the JVM: Scala, Groovy, Clojure
  • Enterprise Java
  • Core Java, Java 8
  • Agility
  • Testing: Geb, Spock, Easyb
  • REST
  • NoSQL: MongoDB, Cassandra
  • Hadoop
  • Spring 4
  • Cloud
  • Automation Tools: Gradle, Git, Jenkins, Sonar
  • HTML5, CSS3, AngularJS, jQuery, Usability
  • Mobile Apps - iPhone and Android
  • More...
Learn More »