Pre-Pro [6/8] Part 1
Gantt Chart
0
0
0
A GANTT chart illustrates work planned to be completed over a period of time.
It can include the start and end dates of tasks, sprints, milestones, dependencies between tasks, assignees, and more.
Building a Gantt chart is an iterative process. Here is an example:
1. Reduce complexity and build a WBS
2. Start with ballpark estimates (t-shirt sizing)
3. Iterate on the scope granularity.
Nail your design & tech plan
4. Estimate each tasks duration in time
5. Add a risk buffer
(5 to 25% depending on task complexity).
6. Make room for 'time eaters'.
Usually 20% (project management, meetings, tests,...)
A. Using old data from the project, OR
using analog estimations from experts & benchmarks
B. Bottom up estimation: adding dev time from a detailed WBS, OR
Top-Down estimations: high level broad estimates, refined as the project progresses.
C. Three-point estimation (PERT): Optimistic / Pessimistic / Most Likely, OR
Parametric estimation: based on math formulas & data (assumptions & models)
Tip: Make it a team building exercise!
Only 50% of IT projects are completed on time.
Inadequate time estimation is becoming a primary cause of failures
(in up to 25% of failure cases).
Inacurate time estimation is a source of friction and inefficiency in a team
(ex: developers waiting for other developers to finish their tasks).
IT projects face a high risk of financial penalties & failure due to schedule overruns
(in up to 30% of the failure cases).
Tip: Be transparent with the team and stakeholders. Surprises hurt projects.
The team agreed on the following conversion table:
All clear?
Please make sure to consult all cards.
Level
1
0
Pre-Production / Mission [6/8] Part 1 completed.
Now that we have time estimates, we can shape our production plan.
This will allow us to:
Ok, enough theory. Let's buid it up.
