Eighth Myth (10 Myth Of Software Project Planning)
Sign in

Eighth Myth (10 Myth of Software Project Planning)

Project Manager at Paxcel Technologies

Eighth Myth
Keeping backup/buffer in project schedule/plan is a bad practice.

It is bad if you make this buffer on fly without any concrete analysis and it is hidden to your clients/ management. Always maintain transparency with your client and each stakeholder of your project.

Please follow different techniques of reserve analysis and make it part of your contingency plan. Keep time and cost buffers/reserves, but after a thorough analysis and not on fly.

It is good to include contingency reserves into the overall project schedule to account for schedule uncertainty. The contingency reserve may be a percentage of the estimated activity duration, a fixed number of work duration or, may be developed by using quantitative methods. The contingency reserve may be used, reduced or, eliminated as per requirements. This should be clearly identified in the schedule document and should be known to each stakeholder of the project.

Reserve analysis compares the amount of the contingency reserves remaining to the amount of risk remaining at any time in the project in order to determine if the remaining reserve is adequate. Following are couple of methods/techniques you can use for your contingency plan:

1. What if scenario analysis

2. Reserve Analysis - Contingency reserves and management reserves

3. Proper use of Leads and lags in schedule

4. Expert Judgment, play a vital role in getting trust from management and stakeholders

5. Risk analysis and risk response planning, it gives better understanding on the reserves you need for your project.

6. Contingent Response Strategies, identifying predefined conditions where the reserves can be used.

prevnew
start_blog_img