1. Usage 0f the Classical estimating approaches byeugene.veselov@magento.com

2. Goal To reinforce Magento team with some knowledge at estimating methods To share positive knowledge

3. Theory. Expert Judgment Subtypes: Brainstorming, Delphi, NGT (see my presentation about this) General idea: Experts (internal/external or even 3rd party company) estimates your project/task Applicable: single activity estimation, WBS development, Choosing right estimating method for a task As a part of another estimating method

4. Theory. Bottom-Up Estimating Subtypes: WBS, CPA. General Idea: breaking the task down into its smallest work components; estimating the effort, duration, and cost of each; and Aggregating them into a full estimate. Applicable: For very precise estimation delivery of a task or entire project Problem of the approach: very slow, requires full understanding of the task.

5. Theory. Analogues Estimating General idea: Analogous is an estimating technique that uses the values of parameter, such as scope, cost, budget, and duration or measures of scale such as size, weight, and complexity from a previous, similar activity as the basis for estimation of the same parameter for a future activity. This is a form of expert judgment. Applicable: This technique is primarily used when there is a limited amount of detailed information about the project or program. When you have enough historical data to avoid bottom-up Problem: it provides a lower degree of accuracy than other estimating techniques, historical data needed

6. Theory. Parametric Estimating General Idea Parametric Estimating uses a statistical relationship between historical data and other variables to calculate an estimate for activity parameters, such as cost, duration, and budget Example: a support team usually fixes 10 bugs per day, so that we expect them to fix 220 bugs this month Applicable Total project/some segments estimation As a part of other estimating methods Problem: accuracy depends on complexity of the mathematical model and historical data.

7. Theory. Reserve Analysis General idea : 1. All the estimates may include contingency reserves to compensate schedule uncertainty. The contingency reserve may be a %% of the estimated activity duration, fixed number of work periods and etc. 2. As more precise information about the project available, the contingency reserve may be used, reduced or eliminated.

8. Theory. Three-point estimates (PERT) This is your homework, guys 

9. Task: develop an estimating strategy for the project described below One of our clients wants a Magento based solution to be integrated with his ERP system (MBS). The frontend (FE) should be almost the same as for one of our previous clients. Unfortunately, the client has self-written ERP system so that we have to implement unique synchronization module (SM) to connect our system and the ERP. The client also wants 20 reports (RPT) but they are very similar to each other. Extra info that came from our top management: Contract type : Fixed price SM should be developed by just created team of 1 client’s developer, 1 our veteran and 1 our newcomer. Other parts will be developed by our stable old teams. Estimation should be delivered ASAP otherwise we’ll get a risk to lose the client Test task. Brainstorm

10. MBS, Bottom up FE, Analogues SM, bottom-up + Delphi RPT #1 bottom up + brainstorm or NGT RPT #2 - 30 parametric Test task. A solution

11. ? Resources : 1. PMBOK 4th edition 2. My team work training materials 3. http://rpl-blog.blogspot.com

12. The end. Questions ? eugene.veselov@magento.com