Answer.

The role of a business analyst in planning and estimating costs is closely related to analyzing business goals, defining scope of work, and identifying necessary resources. The analyst helps to formulate and specify requirements, as well as calculate expected expenses considering all necessary components: labor costs, licenses, equipment, integrations, staff training, and other hidden expenses. Key methods include: expert assessments, analogies with past projects, the COCOMO model, task decomposition with subsequent cost summation, and cost-benefit analysis.

Key features:

• Comprehensive information gathering for structured project cost assessment
• Use of various assessment methodologies: expert assessments, calculation models, benchmarking with similar projects
• Continuous monitoring of requirement changes and budget updating

Trick Questions.

Can we fully trust only expert assessments or should we combine different cost estimation methods?

No, relying solely on expert assessment is risky due to the human factor. Methodologies need to be combined to minimize the likelihood of errors.

Should a business analyst be able to detail technical work for estimating all costs?

A business analyst should understand the essence of technical work to accurately reflect it in the estimate, but is not required to delve into every technical detail. Experts from teams are brought in for this.

Are hidden and indirect costs significant for the final budget assessment of the project?

Yes, failing to account for hidden expenses (training, support, communications, licenses) often leads to budget shortfalls — they must be taken into account.

Common Mistakes and Anti-Patterns

• Ignoring indirect costs and underestimating the impact of requirement changes
• Overly optimistic estimates without risk provisions
• Estimates "from the top of the head" without documenting assumptions

Example from Real Life

Negative Case: Costs were estimated only based on developer rates and license costs, without considering expenses for integration, training, and ongoing support. Pros: Budget was agreed upon quickly. Cons: Additional expenses arose during the process, budgets had to be increased, and client relations deteriorated.

Positive Case: Working time, licenses, expert consultation costs, user training expenses, and ongoing support were taken into account. The estimate was made in several stages with updates after clarifying requirements. Pros: The budget was transparent, no urgent funding expansion was needed, client trust was maintained. Cons: A bit more time was spent preparing the detailed estimate.