This is another presentation in a series of presentation highlighting Critical Chain Project Management (CCPM) Benefits and methodologies for Program and Project managers.
4. 1. Stagger projects based on the
constraint. Launch projects As Late As
Possible*.
Requirements
3 wks
Design
3 wks
Build
6 wks
Test
4 wks
Deploy
4 wks
Requirements
3 wks
Design
3 wks
Build
6 wks
Test
4 wks
Requirements
3 wks
Design
3 wks
Buil
6 wk
* Subordinating everything to the constraint. No Reason to begin project #2 sooner –
that will only increase the WIP and may lead to multi-tasking and incorrect
prioritization of tasks by developers and team leaders.
5. 2. Use Shared Buffers, move safeties to
the end using CCPM methodology
Test
2 wks
Deploy
2 wks
Reqs
1.5 wk
Desgn
1.5 wk
Build
3 wks
Project Buffer
5 wks
Requirements
3 wks
Design
3 wks
Build
6 wks
Test
4 wks
Deploy
4 wks
6. 3. Use Buffer Consumption and Project
Completion to determine prioritization
between tasks.
Test
2 wks
Deploy
2 wks
Reqs
1.5 wk
Desgn
1.5 wk
Build
3 wks
Project Buffer
5 wks
Test
2 wks
Deploy
2 wks
Desgn
2 wks
Build
2 wks
Project Buffer
4 wks
Project A – Project Completed 60%, Buffer Consumption 50%.
Project B – Project Completed 50%, Buffer Consumption 50%.
Therefore Test Resources will be working on Project B before Project A due
to higher priority based on the Buffer Index (Project Completion/Buffer
Consumption)
7. What is the Program
Manager role in an IT
multi-projects
environment?
8. 1. Maintain low Work In Progress (WIP).
Only Constraints need to be fully
occupied.
2. Ensure quick issues resolution and
tasks priorities discipline enforced by
PMs.
3. Make sure projects and tasks have all
resources and other dependencies
ready before beginning
9. For more information please
contact Yossi Bonomo
mail@yossibonomo.com
913-230-2230
LinkedIn/in/yossibonomo