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

Project Team Sizing Heuristics

Nice heuristic --- rule of five for project team sizing. Its good to have a starting framework of roles for projects and modify to the situation. ...

... "When building your next project team think in terms of five and you'll be able to maximize your business and technical capability to deliver a solution on time and on budget. " ...

Via POWERBUILDER DEVELOPER'S JOURNAL: Project Team