Assist the Project Manager to record Size, Effort and Cost estimates for the project. Size and effort estimates form the basis for a detailed and reasonable Project Plan.
<?>
<?>
Identify Estimation Team
Identify Estimation Method
Estimate Size, Effort, Cost and Forecast Dates
Review and Validate Cost Estimates
Prepare Estimation Reports
Project Manager shall estimate effort for the Define phase based on the Project Charter Document baseline. The Project Manager shall form an Estimation Team to perform the estimation. The team recommended for the estimating Define phase estimates include the Requirements Analyst, Project Manager and other SMEs who have worked on similar projects. This team shall discuss the estimation technique or method to be used, seek clarifications on the same, and discuss the scope of work that forms basis for the estimation. Refer to Estimation Guidelines for details on the estimation methods that can be adopted.
The Project Manager, Requirements Analyst, and the SME shall develop the Effort estimates to develop the Business Requirements Document (BRD), System Requirements Specifications (SRS) and Architectural Design (AD) document. The complexity of each requirement shall be discussed and understood to arrive at the estimates. The system characteristics, complexity of the work product and the life cycle being used for Define phase shall be explained for the Estimation Team. The Estimation Report for Define Phase helps to document the rationale for each of the proposed requirements and the total project scope. The Effort estimates for developing BRD, SRS and AD documents shall be estimated in the Plan phase. The system characteristics, complexity of the work product and the life cycle being used for Define phase shall be explained to the Estimation Team. The effort to develop prototype or the use cases, whichever may be the case, shall be included in the Define phase estimates.
The Project Manager shall perform some checks to check consistency in the documented rationale and assumptions, and approve the Effort estimates. The estimation report shall be included in the Preliminary Project Plan [PP(P)] as an attachment. Section 4.3 of this process document provides the generic steps to be followed to develop estimates.
Project Manager shall identify the Estimation Team. Personnel having requisite knowledge and experience shall be selected to be part of the Estimation Team. They shall be members of the Project Team who are fully knowledgeable of the scope of the project and have reviewed the relevant baseline documents.
The Top-Down estimate shall be done by the Project Team to establish the preliminary budget costs and schedule. The Bottom-Up estimate shall be done during the end of the Plan phase for producing reasonable and realistic project schedule for the Define phase.
Project Manager shall choose an estimation method by referring to the Estimation Guidelines. Confidence in estimates is based on rationale for the selected estimation model or the method and the nature of the historical data available in the IO organization. There may be projects for which historical data does not apply, such as where efforts are unprecedented or where the project characteristics do not match with the available data. Unprecedented efforts are more risky and hence need appropriate adjustment through management reserve. The uniqueness of the projects should be documented in the assumption of the estimation report or the Project Plan.
Project Manager shall estimate cost and forecast dates (Schedule) after documenting the basis for the estimation, which is size and effort along with the estimation assumptions, constraints, and dependencies in the Estimation Report.
Project Manager shall take into consideration the following factors that can impact the system resize:
Using the estimated size and the productivity data as inputs, total effort for the development of the system shall be calculated. The effort shall be adjusted with project management effort, such as QA effort, CM effort, effort to get approval, effort for preparing documents before tollgate, etc.
The resources required for the project shall be estimated using the total effort estimates in person-months. The number of people required and the profile in terms of skill level and experience shall be identified. The critical computer resources such as computer memory capacity, computer processor use, etc., shall also be estimated based on the project’s characteristics and needs.
The requirements for the supporting infrastructure and items shall be included in the project costs. The templates for Top-Down estimates and Bottom-Up estimates help to record estimates of the Project Cost. The lead times required to secure funding and purchase goods and services for the project shall be identified and documented in the Project Costs section. The Size and Effort estimates have to be iterated as necessary until Cost estimates tie in together and are consistent.
It is mandatory to identify the critical path in the forecasts and track the same in the project to plan any changes in resources. This critical path must be reflected in the Gantt chart for the project.
Project Manager shall review the estimates to check if all aspects of project requirements have been considered and the commitments are reasonable to achieve.
The Project Manager shall get the Cost estimates and forecast dates reviewed by the Senior Manager to get commitment and guidance to execute the project. Based on the feedback the estimates may need to be reiterated and assumptions revisited.
The project costs and the forecast dates, as approved by the Senior Manager, shall be entered into PTS tool.
Project Manager shall prepare the Estimation Reports after reviewing and verifying the estimates. The Project Manager shall record all assumptions/constraints made while estimating and retain all past project data used during estimation.
Project Manager shall identify risks related to the project due to lack of data for estimation. Other issues that may reflect on the estimation accuracy shall be documented as necessary.