Andrew Meyer at Inquiries into Alignment provides a useful corrective to the faith that we project management types put in our industry standards and frameworks (post here). He hits on a lot of topics that are only alluded to in our project management “bibles”:
[P]rojects often pull people from different departments together to work on a project. While that is what the project requires to be successful, what does that mean for the people pulled from the different departments? Is the project of primary importance to them or is what’s happening in their department of primary importance?
Now, I believe Andrew that has set up a bit of a straw man here. I’m not sure that it is the responsibility of the PMBOK Guide or PRINCE2 to elaborate some of these topics fully (I’ll leave Agile aside for the moment). At least in the case of the PMBOK Guide, it is only a guide to the project management body of knowledge. While a guide should reference the need to ensure business alignment, only so much content “meat” can be expected from such a guide.
My take is that firms should not count on generic standards to cover some of these topics — one’s firm-specific methodology should elaborate the questions Andrew suggests (and more):
What is the business environment your company is working in?
How is that environment changing?
What is happening inside the business?
What is the state of the project?
Where does it need to go?
What needs to happen to get it there?
Filed under: Business Case, Methodology, Portfolio Management, Program Management, Project Management, Strategy Management Tagged: | Andrew Meyer, business alignment, Inquiries into Alignment, PMBOK Guide, PRINCE2