Estimation is a forecast based on current understanding, not a promise. The BA improves estimates by clarifying scope, rules, scenarios, dependencies, and assumptions while the people doing the work provide delivery expertise.
Create transparent forecasts by decomposing scope, exposing uncertainty, and involving the delivery team.
A Work Breakdown Structure decomposes outcomes into deliverables and manageable work. In adaptive delivery, story splitting creates smaller vertical slices of user value. Both reduce hidden scope.
Better understanding narrows the range; it never removes uncertainty entirely.
The team must forecast authentication, checkout, webhooks, reconciliation, and support work.
Decompose the integration into end-to-end capabilities and exception paths.
Document assumptions about provider sandbox, compliance, and existing platform services.
Use expert input and three-point ranges for high-uncertainty items.
Review the forecast after the first technical spike and update remaining work.
The forecast communicates uncertainty and dependencies rather than hiding them in one precise but fragile number.
Open each answer, then practice saying it naturally in your own words.
Clarify scope, decompose work, identify dependencies and assumptions, select a context-appropriate technique, involve delivery specialists, include risk, and adjust using actuals.
A hierarchical decomposition of deliverables and work.
A team-relative measure combining complexity, effort, and uncertainty.
Planned capacity for identified uncertainty and risk.
The number of work items completed in a period.
Answer all three questions. Score 2 out of 3 to pass this section and update your course progress.
Choose one answer for every question, then submit your quiz.