Business analysis estimation – Theory vs. Practice
Business analysis estimation is bit of a strange topic for most BAs.
We do study 8 to 10 techniques mentioned in various sources.
Most common techniques mentioned are:
• Top-down estimation
Estimate efforts for components using hierarchical breakdown. Typically done when the budget is fixed.
• Bottom-up estimation
Uses WBS to estimate deliverables, activities, tasks and estimates from all involved stakeholders and rolls them up to get a total for all activities and tasks. It is easier to estimate smaller items than larger items, bottom-up estimating can produce MOST accurate and defensible estimates.
• Parametric estimation
Uses a calibrated parametric model of element attributes. For example, if one use case takes 3 days to develop, it will take 60 days for developing 20 use cases. Estimate = Sum(fi*xi)
• Rough order of magnitude (RoM) / Ball park
Based on limited information, a high level estimate with a very wide confidence interval. Typically based on history or expert judgment.
• Rolling wave
Involves continual refinement of estimates. Estimate details for activities in current iteration and extrapolate it for entire scope of work. As end of iteration approaches, estimates for next iteration can be made and initial estimate for all activities is refined.
• Delphi estimation
Uses a combination of expert judgment and history. Include individual estimates, sharing estimates with experts and having several rounds until consensus is reached.
• PERT (Program Evaluation Review Technique)
Each component of estimate has 3 values:
• (M) Most likely estimate (3 days)
• (O) Optimistic or best-case scenario (2 days)
• (P) Pessimistic or worst-case scenario (7 days)
PERT estimate: (1 * Optimistic + 1 * Pessimistic + 4 * Most likely)/6 = (4*3+2+7)/6 = 3.5
Source: BABoK Version 3.0
However, when I look back at my own BA career and I ask many other BAs, most of us really seem clueless about BA estimation.
How is BA estimation different from development estimation?
BA essentially is a discovery process – you are not very sure what you will discover as you wade through the discovery process.
Development estimation happens on data which has reasonable clarity. Requirements are unlikely to fall into this category.
In many projects, most project managers even do not bother so much about BA estimation. The reason is possibly due to the fact that we run usually run short of development capacity, not BA capacity. One single BA can possibly provide enough requirements for 5 to 10 developers. So in many companies, especially agile projects, PM assigns 1 BA for 5 developers.
When I worked in Infosys, we followed a top down approach where 15% of overall project effort was assigned to BA. I have worked on short waterfall projects where initial 2 to 3 weeks were allocated for BA work in a 6 month long projects.
Have you folks actually used other methods such as WBS?
WBS is probably good for development estimation than BA estimation.
I would love to learn from fellow BAs about the BA estimation approaches they followed in their projects.
I am a professional BA, trainer, coach and author.
If you like my posts please like/share/comment and spread the word in your network.
Would love to connect with fellow professionals.
You can also reach me at LNMishra@AdaptiveProcesses.com
About my organization, Adaptive Processes
We provide training, study guides, question banks, necessary PDUs for ECBA, CCBA, CBAP and CPRE certifications.
For more details, please visit www.AdaptiveProcesses.com
24+ years of professional experience inbusiness analysis, software product development, business analysis, ERP implementations, software processes , strategic Change Management Consultancy.
Author of 12 books on Business Analysis and Requirements Engineering
Latest posts by LN (see all)
- Business analysis estimation – Theory vs. Practice - July 10, 2017
- Coolest trick to get 60 hours out of thin air for your CBAP exam - July 5, 2017
- 100 common risks for business analysis - June 20, 2017