Objective: Define and implement a software estimation process providing 3 estimates over the life cycle of the project (macro-estimation, general requirements, detailed requirements) in less than a month.
Context: You do not know anything about project estimation, but you have to define and implement a software estimation process.
Results: Estimancy helps you to build a working estimation process in less than a month.
Approach to software project estimation:
- Choice of the project type
- Training to software project estimation
- Calculation of productivity
- Configuration of Estimancy’s solution
- Standardization over the organization
- Go live
1. Choice of the type of project
We identify the projects the most representative of your organization and for which you need more reliable estimates. We will, as far as possible, choose only one technology to avoid the multiplication of productivity measurements (step 3).
2. Training to software project estimation
The team who is in charge of the estimation process (1-3 people) will be trained for 5 days on all the estimation techniques. Including the IFPUG (average complexity), Early&Quick and CoCoMo methods and the estimation best practices. That training is mostly based on practical cases.
3. Productivity calculation
Each language or technology has its own productivity rate. It is faster to develop with Java than Assembler for instance. To measure the productivity, must be defined the quantity of software developed by one person during a day. In this regard, we study a couple of former representative projects for which we know the global effort.
4. Configuration of Estimancy’s solution
The three estimation models (macro, approximate and detailed estimations) are configured in Estimancy’s solution. You will then be able to generate an estimation through the platform.
5. Standardization over the organization
At that stage, everything is technically ready. But your organization must know that a new estimation process is available for the project managers. In this regard, the process must be presented and teams must be trained. The project managers and specification writer must be educated about specification writing best practices.
6. Go live
Estimancy will assist you and provide support to ensure the proper running of your first two estimates.
After 20 days, your organization will have a global estimation process for software project:
- Macro estimation at the beginning of the project,
- Approximate estimation with general requirements,
- Detailed estimation with detailed requirements.
You can then enter a continuous improvement loop to tune your knowledge of the productivity parameters impacting projects.