Scalable Project Discipline
Should we classify projects by size and scale project discipline using size (cost / effort) as the meter for project discipline? I've seen that more often, since investment size (cost / effort) at risk warrants discipline to improve likelihood of success.
But how about situations when various size projects (including small ones) are critical to business success and either time or quality of the deliverable is the key business driver. Business critical projects are worthy of a disciplined method of delivery.
Or, should we ignore size, etc. and achieve a level of PMO maturity that operates at such an efficient level of productivity and project volume throughput that the project management discipline is optimal across the full portfolio?
What do you think? ...
... "there must be a dividing line between projects that are complex and critical enough to require a full, rigorous methodology, and those projects that are simple and routine enough to be managed with minimal project overhead. The question is: Where is that line? " ...
Via TechRepublic: Project size classification determines rigor
Labels: business-impact, costs, discipline, maturity-model, pmo, productivity, rigor, risk-management, scalability, sizing
posted by Frank M @ 8:05 PM, Read More...
2 comments
links to this post
