Estimation (old)

 Overview

Estimation of a project is not always an easy process. It requires a full understanding of the incoming information, perseverance on what is being estimated.

 Estimation Flow

• When the first time the customer contacts the sales manager with all incoming information, the sales manager will have the new template for estimation already. Sales Manager is required to fill in the brief and the stakeholder register.

• PMO assigns a PM based on the requirements for the estimate, along with the developer(s) and QA for the estimation (sometimes, the PM will choose the developer(s) himself)

• The incoming documentation must be read by the PM, developers and QA

• There will be a new template for estimation that will be shared with the customer.

• The estimation must be based upon the incoming documentation from the customer. 

• The primal Estimation should be High Level, based on epics or main functions. 

• The Team Register should be filled in by the PM

• All the epics and main functions are to be entered by the PM and the developers estimating.

• After the customer agrees on the proposal, the estimation should be decomposed into tasks and be more detailed.

• Based on the total tasks hours, it is to be counted and added the time required for communication, planning, environment etc. For communication for daily meetings – 15 min per team member for each day. For planning it is approximately 1 hour per sprint (depending on the size of the project), for the environment – 8-16 hours depending on the dev.

 Tips and tricks


• If there is not enough incoming information, risks should be considered as well.

• In case of risks, the presumptions should be also written along with the percentage of the risk

• Risks can be added in percentage and discussed with the PMO.