About the author
S02-E03 The world of precisely wrong with the project plan
You made your project plan (episode 1). Then you verified that it was at the right level of detail (episode 2)... knowing that there is an uncertainty that you will discover. How will/should you incorporate these elements into the project plan update? Whoa, slow down! We are going to integrate EVERYTHING into the schedule, aren't … Continued
2 min read
Agilea
You made your project plan (episode 1). Then you verified that it was at the right level of detail (episode 2)... knowing that there is an uncertainty that you will discover.
How will/should you incorporate these elements into the project plan update?
Whoa, slow down! We are going to integrate EVERYTHING into the schedule, aren't we ?!
So how do we choose what is important? How do we know that it will be important on the next project? In short, how do we do it?
1/ By applying the FLOW Project Management method,
you can use the Fever Chart to identify times when you have consumed buffer.
2/ Take these events and measure the impact it had on the buffer consumption.
- If the buffer has been significantly consumed by this event (10%) then the event should be considered in the future project,
- If the buffer was not significantly consumed, it may not be worthwhile to go into more detail.
- Then look at the tasks where you have recovered buffer and ask yourself if the actions you have taken, which have recovered buffer, should be integrated into the future project plan. This will avoid having a plan that only gets more complex.
3/ Forgetting a task.
Ah!, the famous task that we forgot to specify in the project and "that it would be good to take into account for the next time because you never know". In this case, go back to the previous article to see if this task fits into the criteria for cutting. In fact, very often, these tasks are "details" that reassure but that ultimately make the project more complex to read.
At this point; we have seen how to create the plan, check that it is controllable and we have just seen how the feedback around its execution can help us to update it.
However, it does not say what we could do to reduce the length of the plan and gain control over the execution.
More in episode 4…
Topics
Go further
Related articles
Flow Project Management
S02-E05 Managing the Load / Capacity of the Softs (the continuation of the precisely wrong)
At this point, everything is going well: But, there are several projects that use the same resources. So, how do you manage this? Most people will tell you that having a project management tool that collects load and capacity will help you drive your choices. This is simply not true. Most load / capacity tools … Continued
2 Jun 2022
2 min
Flow Project Management
S02-E04 How do I focus on the right tasks for my project?
Once you have completed your project plan, sized the tasks and avoided creating a labyrinthine system with too much detail, you need to move on to the step that will identify the most time critical task sequence. At this point, we recommend that you use the critical chain approach. Unlike the critical path approach, which … Continued
19 May 2022
2 min
Flow Project Management
S02-E02 What if I cut my project...
In the previous article, we saw what a project plan was and the elements to start building it. We ended with the following question: When did I reach the right granularity? How can I manage a project over several years? It is to these questions that we will try to answer in this article. The … Continued
29 Mar 2022
3 min
Does this article resonate?
Let's talk about your situation.
Our consultants help you translate these reflections to your Supply Chain and your teams — diagnosis, scoping or operational delivery.