1. Aggressive scheduling- Reduce original estimates of each task by 50% to remove buffer which helps in reduce student syndrome and parkinson's effect.
It is considered that each developer, tester gives estimation after including safety time and contingency. It is very difficult to detect how much safty is added in each task so the thumb rule is reduce the estimates by 50%. When you reduce the estimates into 50%, you will get strange reaction from your team. So it is challenging task to convience team to remove buffer form each task and add it at project level. Manager should not introduce new estimates as commitment from the team and make clear that it is not mandetory to meet these estimstes.Team may think this as PM is putting pressure to complte the task early but this step is very important to eliminate student syndrome and parkinson's effect.
2. Remove bad Multitasking- Control the WIP(Work in progress) by each team member.
Make sure that each resource works on single (minimum as possible) task at a time. This will aviod the delayed start of next task and also help in reducing set up time and set down time to improve productive time.3. Eliminate desychronization losses: Remove estimated start date and finish date for tasks as we should protect the complition date of whole project than complition of each task. Start successor task as cuurent task gets finished (Unless there is some dependacy from other task)
4. Introduce flow time- Flow time (Dedicated time for focusing only on given task) of around 3-4 hours through day should be introduced to improve productivity. There wiil be no meetings, calls, knowledge transfer during flow time.
5. Buffer Management- Frequent reporting (may be daily 5-10 min stand-up meeting) from team is very important. This help in detecting early warnigs (risks) and this can be work as effective forum forum for solving blocking issues. Task priorities should be decided according to project and feeding buffer consumption.
Project buffer penetration:
Green: OK.
Yellow: Plan buffer recovery.
Red : Take Action for buffer recovery.
Threshold points on Fever chart should be determined by mangement, there are no standard method to determine it.
Threshold point should be realistic and should not be to low to minimise false signals. Followings may be used as threshold points:
Buffer penetration%
Critical chain complete % ---Grren to Yellow transition % ---Yellow to Red transition %
0 ----------------------------------15 ---------------------------------30
100------------------------------- 75--------------------------------- 90
Advantages of CCPM implementation: -
1. Proper Planing: CCPM implementation requires well defined scope and planning shedule with cosidering resource contention.
2.Early Warnigs: Frequent reporting helps in finding task progerss. As we are tracking remaining duration for each on-going task, if anybody gets stuck because of reasons like expansion of work, beacuse of incompetancy with fuctional or technical knowledge it comes to know very early during task execution. This helps to take necessary decisions for proper control over project.
3. Remove the wastage: The task dates become deadlines. They cause waste because people who finish the task early don’t pass it on.”
2.Early Warnigs: Frequent reporting helps in finding task progerss. As we are tracking remaining duration for each on-going task, if anybody gets stuck because of reasons like expansion of work, beacuse of incompetancy with fuctional or technical knowledge it comes to know very early during task execution. This helps to take necessary decisions for proper control over project.
3. Remove the wastage: The task dates become deadlines. They cause waste because people who finish the task early don’t pass it on.”
On time compltion of project is improved from 40% to 92% after CCPM implementation.



No comments:
Post a Comment