Project Management Central

Please login or join to subscribe to this thread

Topics: Earned Value Management, Risk Management, Scheduling
In your planning of project, what is the level of detail you go to?
Network:102724



For planning a project you do start with a high level schedule or with a more detail approaches.

To what Level of detail do you go?

Does it goes to the packages detail?
Sort By:
Page: 1 2 3 4 5 <prev | next>
Network:102724



Dec 21, 2017 2:42 PM
Replying to Sergio Luis Conte
...
The worst thing organizations can do to achieve its objectives is to divide the projects into internal and external. Is the first step to fail.
Sergio,

I will have to disagree, internal and external projects are different by nature. Doesn't mean they don't have to be well manage in both case.

An external project you provide the client a price, a timeline, quality etc. and if put in a contract. You can't change it because you didn't include something in a package and if it is major you may lose benefit or profit in that case.

In an internal project same situation might increase cost, cancel the projet or get the PM fire.

Why you consider a bad thing to distinguish the two projects context?
...
1 reply by Sergio Luis Conte
Dec 21, 2017 5:37 PM
Sergio Luis Conte
...
Are the same. You always have a client, a contract (the project charter is a contract), a price (somebody must paid for the project). The worst thing some organizations done is to consider a difference on it. That is basic to survive in the actual world. The project is created to put strategy into action. The objective must be one and only one. It has no sense to make a difference. When initiatives fail most of the reasons are when you make this type of distinctions.Mainly when this types of distinctions are made related to the project team.
Network:1481



For larger and complex projects there are dependencies between people, and timings have greater odds of impacting others. So, it depends but in general start with high level and decompose when you have more information.
...
1 reply by Vincent Guerard
Dec 21, 2017 7:11 PM
Vincent Guerard
...
Anish,

You decompose before you engage in the contract?
Network:1612



Dec 21, 2017 4:40 PM
Replying to Vincent Guerard
...
Sergio,

I will have to disagree, internal and external projects are different by nature. Doesn't mean they don't have to be well manage in both case.

An external project you provide the client a price, a timeline, quality etc. and if put in a contract. You can't change it because you didn't include something in a package and if it is major you may lose benefit or profit in that case.

In an internal project same situation might increase cost, cancel the projet or get the PM fire.

Why you consider a bad thing to distinguish the two projects context?
Are the same. You always have a client, a contract (the project charter is a contract), a price (somebody must paid for the project). The worst thing some organizations done is to consider a difference on it. That is basic to survive in the actual world. The project is created to put strategy into action. The objective must be one and only one. It has no sense to make a difference. When initiatives fail most of the reasons are when you make this type of distinctions.Mainly when this types of distinctions are made related to the project team.
...
1 reply by Vincent Guerard
Dec 21, 2017 7:15 PM
Vincent Guerard
...
Sergio,

Understand you point and agree, but still feel there is a difference at some level on the two context.
Network:95594



Dec 21, 2017 4:30 PM
Replying to Vincent Guerard
...
Rami,

Your answer is clear, possibly the way I formulated the question was not.
Cheers Vincent :-)
Network:102724



Dec 21, 2017 5:19 PM
Replying to Anish Abraham
...
For larger and complex projects there are dependencies between people, and timings have greater odds of impacting others. So, it depends but in general start with high level and decompose when you have more information.
Anish,

You decompose before you engage in the contract?
...
1 reply by Anish Abraham
Dec 21, 2017 8:41 PM
Anish Abraham
...
No, only after signing the contract.
Network:102724



Dec 21, 2017 5:37 PM
Replying to Sergio Luis Conte
...
Are the same. You always have a client, a contract (the project charter is a contract), a price (somebody must paid for the project). The worst thing some organizations done is to consider a difference on it. That is basic to survive in the actual world. The project is created to put strategy into action. The objective must be one and only one. It has no sense to make a difference. When initiatives fail most of the reasons are when you make this type of distinctions.Mainly when this types of distinctions are made related to the project team.
Sergio,

Understand you point and agree, but still feel there is a difference at some level on the two context.
...
1 reply by Sergio Luis Conte
Dec 22, 2017 5:51 AM
Sergio Luis Conte
...
At the end is a decision to take about the way you will perform actions (tactic). I pushed my way of thinking into each organization I worked mainly because I have to work on initiatives that today you can find with names like digital transformation, blockchain implementation, business on demmand, etc.
Network:1481



Dec 21, 2017 7:11 PM
Replying to Vincent Guerard
...
Anish,

You decompose before you engage in the contract?
No, only after signing the contract.
...
1 reply by Vincent Guerard
Dec 22, 2017 8:37 AM
Vincent Guerard
...
Anish,

Would decomposing before contract reduce your risk? What is the nature of you project?
Network:295



In my opinion you plan what you know and try to forecast the later fauture to the best you can. So, do deteiled planning for a time-window of max 2-3 months, the rest is high level driven by overall targets and roadmaps. Planning is ongoing revolving excercise: Inspect and Adapt based on transparency on hand. Planning is a team excercise.
...
1 reply by Vincent Guerard
Dec 22, 2017 8:40 AM
Vincent Guerard
...
Peter,

Planning with detail for up to three months is my experience.

At what moment do you define package?
Network:1612



Dec 21, 2017 7:15 PM
Replying to Vincent Guerard
...
Sergio,

Understand you point and agree, but still feel there is a difference at some level on the two context.
At the end is a decision to take about the way you will perform actions (tactic). I pushed my way of thinking into each organization I worked mainly because I have to work on initiatives that today you can find with names like digital transformation, blockchain implementation, business on demmand, etc.
...
1 reply by Vincent Guerard
Dec 22, 2017 8:42 AM
Vincent Guerard
...
Sergio,

Thanks.
Yes Tactic that is an important part of project management.
Network:102724



Dec 21, 2017 8:41 PM
Replying to Anish Abraham
...
No, only after signing the contract.
Anish,

Would decomposing before contract reduce your risk? What is the nature of you project?
...
1 reply by Anish Abraham
Dec 22, 2017 11:26 AM
Anish Abraham
...
Vincent,
In my opinion, decomposing the work gives an idea of the effort required for each of the work packages together with the associated risk and complexity information, so I guess it can help to reduce the risk. I'm in healthcare IT, so have to deal with privacy laws, regulations etc. Anyway I know that it all depends on the project needs, the organization's risk tolerance and the type, size and complexity of the project.
Page: 1 2 3 4 5 <prev | next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Next week there can't be any crisis. My schedule is already full."

- Henry Kissinger

ADVERTISEMENT

Sponsors