Let's do a second pass on the plan. We may be able to:
- reduce time estimates based on progress already made & re-use
- reduce time estimates after design simplifications
- rebalance who is doing what
- cut scope if really needed
Let's build our GANTT CHART:
high level development schedule of features based on priorities, dependencies and staff capacity.
The team put together the basics, we just need to assemble the pieces on the timeline.
Build the puzzle in less than 3min to get a bonus star
Days
____________
Luke
__
Ben
__
Kira
Ok! We have a Production Plan on a timeline.
Wait... According to this plan, it will take 6 days to complete the work. We barely have 5...
Also, we need a 1 DAY BUFFER for integration, extra testing and iteration...
So, we have to target 4 days of work planned maximum... Oops...
What are our options???
😅 How about we identify the CRITICAL PATH and find solutions as a team.
CRITICAL PATH:
Longest path (in time) from Start to Finish, based on features dependencies.
it indicates the minimum time necessary to complete the entire development.
It's a decision making tool to agree on what we start with.
Scratch inside the frame below to identify the Critical Path, represented by work blocks in red
â–
Luke is too loaded. Our designer is helping however 'programming' is the bottle neck...
Pre-Production / Mission [6/8] Part 2 completed
After discussions with the team, we have some good news:
Luke can re-use some of the code written during Conception and made good progress during pre-production.
Ben, our Designer, is on-boarding fast and is already up and running.
Let's do a second pass on the plan. We may be able to: