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:89971



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:89971



Dec 22, 2017 4:22 AM
Replying to Peter Ambrosy
...
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.
Peter,

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

At what moment do you define package?
...
1 reply by Peter Ambrosy
Dec 22, 2017 10:43 AM
Peter Ambrosy
...
Planning is an ongoing team accountability. Normally my teams plan with 2-mx. 3 months perspective on a revolving basis. This represents the tactical level. In SAP projects we plan with max 1 month time-boxed iteration. The first 2 weeks of the first month sprint we plan very detailed (team member task-level). The rest emerges over the time-box through daily inspect and adapt. Same procedure applies to the following iterations.
On a high level (strategic layer) we plan overall roadmap milestones and synchronization needs. On this layer it is also possible to define bigger work-packages that need to be sliced in more detail forthcoming iterations.
Network:89971



Dec 22, 2017 5:51 AM
Replying to 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.
Sergio,

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



Dec 22, 2017 8:40 AM
Replying to Vincent Guerard
...
Peter,

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

At what moment do you define package?
Planning is an ongoing team accountability. Normally my teams plan with 2-mx. 3 months perspective on a revolving basis. This represents the tactical level. In SAP projects we plan with max 1 month time-boxed iteration. The first 2 weeks of the first month sprint we plan very detailed (team member task-level). The rest emerges over the time-box through daily inspect and adapt. Same procedure applies to the following iterations.
On a high level (strategic layer) we plan overall roadmap milestones and synchronization needs. On this layer it is also possible to define bigger work-packages that need to be sliced in more detail forthcoming iterations.
...
1 reply by Vincent Guerard
Dec 26, 2017 7:34 PM
Vincent Guerard
...
Peter,

Nice approach
Network:1396



Dec 22, 2017 8:37 AM
Replying to Vincent Guerard
...
Anish,

Would decomposing before contract reduce your risk? What is the nature of you project?
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.
...
1 reply by Vincent Guerard
Dec 26, 2017 7:36 PM
Vincent Guerard
...
Anish,

Very true, each project is different.
Network:89971



Dec 22, 2017 10:43 AM
Replying to Peter Ambrosy
...
Planning is an ongoing team accountability. Normally my teams plan with 2-mx. 3 months perspective on a revolving basis. This represents the tactical level. In SAP projects we plan with max 1 month time-boxed iteration. The first 2 weeks of the first month sprint we plan very detailed (team member task-level). The rest emerges over the time-box through daily inspect and adapt. Same procedure applies to the following iterations.
On a high level (strategic layer) we plan overall roadmap milestones and synchronization needs. On this layer it is also possible to define bigger work-packages that need to be sliced in more detail forthcoming iterations.
Peter,

Nice approach
Network:89971



Dec 22, 2017 11:26 AM
Replying to 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.
Anish,

Very true, each project is different.
Network:10479



I typically break down a project into various phases, with the level of detail decreasing across successive phases. I.e. for the first phase, I plan with high level of detail; thus, work packages and activities. In successive phases, I may initially plan at high level only, and add detail as the previous phase is coming to completion.
...
1 reply by Vincent Guerard
Dec 28, 2017 10:33 PM
Vincent Guerard
...
Eduard,

Once in a phase you go to high level of detail, would that detail include package definition?
Network:115



I'll try to be a bit more quantitative on this. I like to use 1/1/1/1 rule, as follows:

1 task assigned to
1 person creating
1 deliverable with a duration of no more than
1 week

Naturally your situation may vary, but I've found this to be a good guideline.
...
1 reply by Vincent Guerard
Dec 28, 2017 10:39 PM
Vincent Guerard
...
Lonnie,

Not sure I understand.
Your package definition involve a 1/1/1/1 rule.
1 TASK assign to 1 PERSON to execute 1 DELIVERABLE in 1 WEEK.

What is the distinction between Task and Deliverable in that case?
Network:18



I will not go to the work packages' detail. because at the very beginning if there are too many details to handle it will be a very huge wbs so it's focus on the important point: deadline, resources, risks.
...
1 reply by Vincent Guerard
Dec 28, 2017 10:41 PM
Vincent Guerard
...
Fei,

You don't go to the package detail at the start, do you do it eventually? When?
Network:89971



Dec 28, 2017 11:34 AM
Replying to Eduard Hernandez
...
I typically break down a project into various phases, with the level of detail decreasing across successive phases. I.e. for the first phase, I plan with high level of detail; thus, work packages and activities. In successive phases, I may initially plan at high level only, and add detail as the previous phase is coming to completion.
Eduard,

Once in a phase you go to high level of detail, would that detail include package definition?
Page: 1 2 3 4 5 <prev | next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

You can say any foolish thing to a dog, and the dog will give you a look that says, "My God, you're right! I never would've thought of that!

- Dave Barry

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events