Is Getting Rid of All Projects a Good Idea?
In the session kill all projects at the XP Days Benelux 2013 conference, Paul Kuijten questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.
InfoQ: Your XP Days session is titled "Kill all projects". Isn't that a harsh statement to make?
Paul: I don't think so. It is intended to provoke some different thinking. My aim for the session was to clarify how well "doing projects" fits with product development in a complex environment, and to see if we can come up with alternative ways, keeping the benefits, and getting rid of the flaws.
InfoQ: If we stop doing projects, does that also mean that we do not need project managers anymore?
Paul: Yes. As a matter of fact, I now work with a very large organization that just got rid of the job title project manager. They have teams, they have products, and these are directly driven by business needs. Does this mean that these people they used to call project manager don't have any skills that the company still needs? Not at all. They typically transition to another role, depending on their skill set.
InfoQ: Can you mention some of the good practices for managing projects that can be valuable for agile teams?
Paul: Managing the what, the how, the money and the timelines is still very much necessary. There are tons of good practices in what we call project management. Almost all of them are very applicable if you are doing product development without projects. The practices we mainly want to get rid of are the ones misused for predictive and command and control management. We have found these are very closely tied in with "doing projects". And then there are things that a project organization in our experience isn't concerned enough with, mainly having to do with people, quality and value. That's why I think it is worth thinking about how to do development without "doing projects"
InfoQ: If we kill all projects, How do you fund your product development?
Paul: The typical way organizations fund their product development now is through budgets. A budget is about the dumbest instrument that you could use. It locks you into an annual cycle in which you resist anything you didn't foresee a year ahead. How agile is that? Furthermore, if people didn't need the budget they requested by the end of the year, they will spend it anyway, because otherwise you get less budget next year. More and more companies are funding their development in an iterative and incremental way, judging every investment by its own merits. The most pressing example of this would be something called "beyond budgeting". It's in many ways "agile for financial controllers". Svenka Handelsbanken has been doing this for many years now, and with astonishing results.
Ops with contraints
Mike Hartington Jul 26, 2015