Identify business analysis performance improvements is BABOK Guide v3 task 3.5: the business analyst measures how well the business analysis work itself is going, compares it with agreed objectives, finds root causes of gaps, and recommends preventive, corrective or improvement actions. Its single output is the business analysis performance assessment. The task sits in Business Analysis Planning and Monitoring (BAPM), which carries 14% of the CBAP exam.
This is article 6 of our BAPM series. Tasks 3.1 to 3.4 plan the work; task 3.5 is the "monitoring" half of the knowledge area name. For the big picture, start with the business analysis planning and monitoring overview.
What business analysis performance improvements means
Business analysis performance improvement is the loop of measuring business analysis work, explaining the variance, and changing how the work is done. The subject is the analysis process, its deliverables and the people doing it, not the solution being built.
IIBA's task card for 3.5 states the purpose as assessing business analysis work and planning to improve processes where required. It describes the output as an assessment that holds the results, the root causes of variances from expected performance, and proposed ways to improve (IIBA task card, v1.0, November 2022).
| Item | Task 3.5 |
|---|---|
| Inputs | Business analysis approach; performance objectives (external) |
| Guidelines and tools | Organizational performance standards (if they exist) |
| Sample techniques | Lessons Learned, Metrics and KPIs, Process Analysis, Process Modelling, Root Cause Analysis |
| Stakeholders | Sponsor, project manager, domain subject matter expert, others as needed |
| Output | Business analysis performance assessment |
Sources: IIBA task card (above); inputs and output also confirmed by Open Exam Prep's task 3.5 guide. The BABOK Guide v3 lists more techniques than the five shown on the card.
Why the task matters on the CBAP exam
The exam uses task 3.5 to test whether you can tell a process problem from a product problem. The Certified Business Analysis Professional (CBAP) exam has 120 scenario-based multiple-choice questions in 210 minutes, and BAPM is 14% of the blueprint, so expect a handful of questions where "how is our analysis going?" is the real issue (IIBA CBAP page).
Last verified: October 2026.
Typical stems describe late requirement defects, slow sign-offs, repeated rework or unhappy stakeholders. The correct answer usually measures, analyzes the cause, and then acts. Answers that jump straight to blame, or that evaluate the delivered solution, are usually wrong.
How task 3.5 works, step by step
Task 3.5 has four elements: performance analysis, assessment measures, analyze results, and recommend actions for improvement. Read them as one cycle.
1. Performance analysis
Decide what "good performance" means for this initiative. The definition comes from the business analysis approach (task 3.1) and from external performance objectives, such as organizational standards or a BA practice's targets. Agree it with the stakeholders who will judge the work, typically the sponsor and the project manager. See plan business analysis approach for where these expectations are first set.
2. Assessment measures
Pick measures that fit the approach. BABOK v3 gives example measure categories: accuracy and completeness, knowledge, effectiveness, organizational support, significance, strategic, and timeliness. In practice they turn into numbers such as:
| Measure category | Example metric |
|---|---|
| Accuracy and completeness | Defects traced to requirements; requirements review efficiency |
| Timeliness | Days from draft to sign-off; analysis ready before sprint planning |
| Effectiveness | Share of stories accepted without rework |
| Knowledge | Stakeholder questions the BA could not answer on first ask |
| Organizational support | Workshop slots cancelled by SMEs |
| Significance | Analysis effort spent on high-value scope vs low-value scope |
Adaptive teams measure often and lightly; predictive teams may measure at phase gates. Both are valid, as long as the measures match the approach.
3. Analyze results
Compare actual results with the objectives, then find why the gap exists. Root cause analysis, process analysis and lessons learned sessions do the heavy lifting here. A number alone does not tell you whether the cause is the BA, the process, the tools or missing stakeholder time. Our root cause analysis and 5 Whys guide shows the mechanics.
4. Recommend actions for improvement
Recommend actions of three types:
| Action type | What it does | Example |
|---|---|---|
| Preventive | Reduces the chance that a known problem will happen | Add a three-person story walkthrough before sprint planning |
| Corrective | Fixes a deviation that already occurred | Re-run a review on the requirements that caused UAT defects |
| Improvement | Raises performance even where nothing is broken | Update the shared template so future teams start better |
Open Exam Prep describes the same three-way split, and BA Coach summarizes the task as defining and executing improvements when expected and measured performance differ. Some recommendations change the governance or information management approach too, which links back to business analysis governance and business analysis information management.
Worked example: a checkout team
Here is a short, fictional example of the full loop.
Context. An e-commerce team runs two-week sprints on checkout changes. The business analysis approach says stories should be ready two days before sprint planning, and no more than 5% of user acceptance testing (UAT) defects should trace back to requirements.
Measure. After three sprints the BA pulls numbers from the tracker:
| Measure | Target | Actual |
|---|---|---|
| Stories ready 2 days before planning | 90% | 62% |
| UAT defects traced to requirements | at most 5% | 18% |
| Sponsor survey: "analysis is clear" (1 to 5) | 4.0 | 3.4 |
Analyze. A 45-minute lessons learned session plus a 5 Whys on the top defects shows a pattern. Most defects sit in payment-method edge cases. The payments SME joined only one of three refinement sessions because of a release freeze in her team. Acceptance criteria were written by the BA alone and missed failure paths.
Recommend.
- Corrective: review the open payment stories with the SME this week and add the missing failure paths.
- Preventive: book a fixed 30-minute SME slot each sprint, agreed with her manager; add an acceptance criteria checklist for payment stories.
- Improvement: add a "failure paths" section to the team's story template and share it with the BA practice.
Assessment. The BA writes a one-page business analysis performance assessment with the numbers, causes and actions, and agrees it with the product owner and project manager. The next check happens after two more sprints.
Notice what is not in the assessment: a judgement of the individual BA. The cause was structural (SME availability), so the fix was structural too.
What practitioners say about measuring business analysis
Practitioners agree on one thing: measure outcomes and causes, not activity. Several authors warn that counting documents or meetings pushes analysts toward volume.
- Laura Brandenburg (Bridging the Gap, 2024) advises judging a BA by delivered value, stakeholder alignment and late-project surprises. She warns "you are likely to get exactly what you measure" (Bridging the Gap).
- Adriana Beal on Modern Analyst lists five management mistakes, including measuring before setting goals and tying metrics to reward or punishment. She notes "Just because something can be measured, it doesn't mean it should be." (Modern Analyst).
- Angela Wick (BA Times, 2014) suggests three BA metrics: layers of defects, the sponsor's view of project success, and rework caused by diving into detail too early (BA Times).
- Mariana Mitevska, from the IIBA Sofia chapter community, collected KPI ideas from a practitioner workshop and warns that KPIs often end up used to assign blame (Modern Analyst).
- Techcanvass defines requirements review efficiency as review defects divided by review defects plus test defects traced to requirements; in their example it is 25% (Techcanvass, 2019).
- Qarina Mannaf (BA Times, 2018) describes the BA running retrospectives with fishbone diagrams and 5 Whys, and keeping actions small enough for the next sprint (BA Times).
- An IIBA member article based on Ryland Leyton's webinar says good KPIs are unambiguous, relevant, measurable and tied to strategy (IIBA).
The common thread matches task 3.5: agree objectives first, use few measures, look for root causes, and turn lessons learned into actions someone owns.
Common misconceptions
"Task 3.5 evaluates the solution." No. Solution performance belongs to Solution Evaluation (chapter 8). Task 3.5 looks at the business analysis work. Exam stems often mix the two.
"It happens at the end of the project." No. Lessons learned and retrospectives can run at any point. Adaptive teams assess every iteration.
"It is a personal performance review." Not mainly. The assessment covers processes, deliverables and conditions. Blaming one person rarely fixes a structural cause.
"More metrics mean better control." Practitioners above warn that many metrics, especially activity counts, drive the wrong behaviour.
"Corrective and preventive are the same." Corrective fixes what already went wrong. Preventive stops a known problem from happening (again). Improvement raises the bar where nothing is broken.
"Lessons learned are the output." The output is the business analysis performance assessment. Lessons learned is one technique that feeds it.
Practice Questions
Question 1. Three sprints in, 20% of UAT defects trace back to missing acceptance criteria. The sponsor asks the business analyst what to do first. What is the best response?
A. Ask the developers to fix the defects faster B. Compare the results with agreed performance objectives and analyze root causes C. Replace the business analyst on the payment stories D. Run a solution performance assessment
Answer: B. Task 3.5 first compares measures with objectives and looks for causes, then recommends actions. A treats the symptom. C assumes blame without analysis. D belongs to Solution Evaluation.
Question 2. After a lessons learned session, the team adds a mandatory SME walkthrough before every sprint planning so that edge cases are not missed again. Which type of action is this?
A. Corrective B. Preventive C. Improvement D. Escalation
Answer: B. The action reduces the chance of a known problem recurring. A corrective action would fix the defects already found.
Question 3. Which item is the output of Identify Business Analysis Performance Improvements?
A. Business analysis approach B. Governance approach C. Business analysis performance assessment D. Solution performance analysis
Answer: C. The business analysis approach is an input to task 3.5. The governance approach is the output of task 3.3. Solution performance analysis belongs to chapter 8.
For timed, scenario-style practice on another IIBA exam, try our IIBA CBDA practice exam.
Related techniques
Task 3.5 relies on techniques you also use elsewhere: Lessons Learned, Metrics and Key Performance Indicators (KPIs), Process Analysis, Process Modelling and Root Cause Analysis. See the BABOK techniques map by knowledge area for where each technique appears.
FAQ
What is the output of BABOK task 3.5?
The output is the business analysis performance assessment. It records the performance results, the root causes of variances from expected performance, and the proposed improvement actions. Stakeholders such as the sponsor and project manager review it.
What are the inputs to Identify Business Analysis Performance Improvements?
There are two inputs: the business analysis approach and performance objectives (external). The approach sets how the work should be done; the objectives define what good performance looks like. Organizational performance standards act as a guideline.
What is the difference between preventive and corrective actions in task 3.5?
A corrective action fixes a performance problem that has already occurred, such as re-reviewing requirements that caused defects. A preventive action reduces the chance that a known problem will occur or recur, such as booking regular SME time. Improvement actions raise performance where nothing is failing.
Is task 3.5 the same as Solution Evaluation?
No. Task 3.5 assesses business analysis work, deliverables and processes. Solution Evaluation (BABOK chapter 8) assesses the performance and value of the solution itself. CBAP questions often test this distinction.
Do agile teams need task 3.5?
Yes. Agile teams usually perform it through iteration retrospectives and lightweight metrics rather than a formal phase-end review. The task card notes that measuring business analysis performance matters for adaptive, predictive and hybrid approaches.
Sources
- IIBA: Task card, Identify Business Analysis Performance Improvements (v1.0, November 2022)
- IIBA: BABOK Guide v3, 3.5 Identify Business Analysis Performance Improvements
- IIBA: CBAP certification page
- IIBA: How to measure the performance of business analysis professionals
- Open Exam Prep: Identify BA Performance Improvements (Task 3.5)
- BA Coach: Business Analysis Planning and Monitoring (2020)
- Bridging the Gap: Guide to Business Analyst Performance Metrics and KPIs (2024)
- Modern Analyst: 5 Top Mistakes Management Makes With BA Performance Measurement Programs
- Modern Analyst: KPIs for Business Analysts
- BA Times: Three BA Metrics You Should be Tracking (2014)
- BA Times: Value Gained from taking a BA Approach to Retrospectives (2018)
- Techcanvass: What is Review Efficiency? (2019)