Q1. What is the difference between a top-down and a bottom-up planning?
- Plan is developed by individual or a small subset of people on a project).
- It provides details only as of a high-level schedules, costs, and risks.
- It should not be committed to management or the client, it should be said only as a targeted plan.
- Top-down planning is an essential business exercise that helps stakeholders get a better feel for the size, cost, and complexity of a project.
Bottom- Up Planning
- A bottom-up plan is developed with the participation of virtually all members of a project.
- All activities are identified (not just the significant ones), along with the activity owners, activity duration, the dependencies among activities, and other information.
- A bottom-up plan represents the plan that should be committed and is considered reasonable risk.
Q2: Why planning of a project is so important?
Progress on a project cannot be measured until a plan has been established and approved. Against which measurement could be made.
Q3. Contracts are often based on top-down planning. Are you saying that these plans should not be committed?
It is not realistic to wait for the critical mass of project members to be onboard before estimating plan commitments for a contract. With contracts, it is important that the final proposal be carefully reviewed before it is submitted. It also should include sufficient contingency to help address the unknown.
Q4. Who should approve the project plan?
- All stakeholders.
- Project members approve their own portions of the project plan as well as those portions that affect their area of responsibility. For him, this translates to having approval rights on the entire plan.
- Resource managers/Functional Managers approve those portions that affect their resource commitments.
- The product manager, sponsor, and/or client approve the major aspects of the plan such as scope, schedules, costs, and quality.
Q5. Who has the final rights on the project plan approval?
The person who has the most at stake based on the successful outcome of the project has the final approval authority. This person is called often called the product manager or sponsor. The project manager works on behalf of this person called the sponsor However, ultimately, the client has the final approval if the project is for a specific client.
Q6. When should a project plan be revised?
- Change control process to address changes in scope. Schedule ,cost
- Changes in the project’s ground rules that could affect the plan
- At the end of major phases
- As assumptions Changes.
- As the project achieves its major phases or milestones, better data is available from which to plan.
Q7 Define Project Plan vs Project Control?
- Project planning is to get the control; project tracking is about to stay in control.