Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Strategy
Cutting down on Knowledge Areas
If you had a very simple project with no criticality or even strict constraints on time, budget, scope or quality, what are the five (of ten) project management knowledge areas you could do without and still have a pretty successful project?
Sort By:
Page: 1 2 next>
I don't think you can run a project without giving some consideration - even if it's half a page or one hour worth of effort - to all the knowledge areas
...
1 reply by Sante Vergini
Feb 05, 2020 2:43 PM
Sante Vergini
...
Yes that seems to be the consensus.
Procurement is an easy one to jettison, Sante, if there is no third-party work involved but otherwise I dont think any of the others can be jettisoned.

What you would do is scale how heavy the approach to each is...
...
1 reply by Sante Vergini
Feb 05, 2020 2:46 PM
Sante Vergini
...
Hi Kiron. I agree with Procurement being the obvious one.
Think you can run a project with just Section 4, Integration management. It's 7 processes are the backbone of every project (maybe except of knowledge management).
I agree with Deepesh.
Dear Sante
Interesting your question

Thanks for sharing

I don't think I can "discard" any area of ??knowledge

If you subcontract the execution of the project you will need at least 6 areas of knowledge
...
1 reply by Sante Vergini
Feb 05, 2020 2:47 PM
Sante Vergini
...
Perhaps some can be joined together under a common group. i.e. "cost" and "procurement" under "finance" for example.
I will write what I do today and I was in charge to define for my current work place. We have a project clasification from tier 1 (top) to tier 5 (bottom). Our focus of attention is Project Integration Management. What we do is not cutting areas is to adapt and "making flexible" the governance process which will impact on deliverable generation and control gates execution. Obviously, as @Kiron mentioned, if you do not have something to adquire Project Procurement will not be included just to take an example. But we prefer to put all them in the table and having a checklist to select what to include or not from knowledge area to process that belongs to them.
...
1 reply by Sante Vergini
Feb 05, 2020 2:48 PM
Sante Vergini
...
That's a good approach Sergio, taking elements from a framework that works.
Feb 04, 2020 11:27 PM
Replying to Deepesh Rammoorthy
...
I don't think you can run a project without giving some consideration - even if it's half a page or one hour worth of effort - to all the knowledge areas
Yes that seems to be the consensus.
Feb 05, 2020 12:01 AM
Replying to Kiron Bondale
...
Procurement is an easy one to jettison, Sante, if there is no third-party work involved but otherwise I dont think any of the others can be jettisoned.

What you would do is scale how heavy the approach to each is...
Hi Kiron. I agree with Procurement being the obvious one.
Feb 05, 2020 4:27 AM
Replying to Luis Branco
...
Dear Sante
Interesting your question

Thanks for sharing

I don't think I can "discard" any area of ??knowledge

If you subcontract the execution of the project you will need at least 6 areas of knowledge
Perhaps some can be joined together under a common group. i.e. "cost" and "procurement" under "finance" for example.
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I'm not afraid to die, I just don't want to be there when it happens."

- Woody Allen

ADVERTISEMENT

Sponsors