He raises some very interesting issues I agree with. Software development can be a part of a project, but a project always has a broader scope of activities, so limiting yourself to only development leaves out some aspects. And before we go this way, let me just start now : yes, it is important for a PM to know software development practices. Not to perform them personally, but to be able to communicate intelligent about the subject: “where are the risks, is he or she bullshitting me… ?”

It might seem that we are splitting hairs here. Perhaps we are, but it is important in my opinion, even if it is just a mental exercise for a Project Manager to think about what his profession is all about (see WTF: Project Management Theories?). In the decade that lies before us, change is the only constant factor, you are not going to make it as a PM being just from whatever camp you might think of. It is not a discussion about “agile or plan-driven” it is “agile and plan-driven and everything in between”.

But I love the term “agile”… and we can use it properly for PM:

If you are talking about “agile project managers”, this would be the key aspect of my definition. A project manager that has a lot of mental models about projects available, and can adopt his mindset according the situation without problems, is what I call a true “agile” PM. As with any social situation, a group of interacting stakeholders is a very complex system. You are never going to come up with one this-size-fits-all model that is usable. The only shot PMs have is being fluent in more than one mental model. (my posting)

Perhaps I should coin the term Resilient Project Management.

Agile PM Is Not Project Management is a post from: Project Shrink.