The backlog management technique is BABOK technique 10.2: recording, tracking and ordering the work items that are still to be done, so the most valuable ones are always worked on first. In the BABOK Guide v3 it is approach-neutral, not a Scrum ritual, and on the Certified Business Analysis Professional (CBAP) exam it shows up mostly in Requirements Life Cycle Management (15% of the exam) when requirements are prioritised and changed.
Last verified: October 2026 (exam facts from iiba.org).
What the backlog management technique is
Backlog management is a way to handle more work than the team can do at once: you keep the remaining items in one ordered list and keep re-ordering it as you learn. The International Institute of Business Analysis (IIBA) describes a backlog in its BABOK Applied resource as what happens when work items exceed what can be completed.
The BABOK Guide v3 describes the technique through four elements:
| Element | What it covers | What the BA does |
|---|---|---|
| Items in the backlog | any work item: requirements, user stories, features, defects, change requests, even design or research work | makes each item clear enough to understand and trace |
| Prioritization | the order of the items | facilitates ordering by value, risk, dependencies and urgency |
| Estimation | the relative size of items, more precise near the top | gets sizes from the people doing the work |
| Managing changes to the backlog | adding, removing, splitting and re-ordering items as needs change | keeps the list current and the changes visible |
If you want the Scrum view of the same idea, our earlier note on Product Backlog management for the PSPO covers ordering and transparency from the Product Owner's side. This article looks at it the way the BABOK Guide and the CBAP exam do.
Why it matters on the CBAP exam
Backlog management matters because the CBAP exam tests it in a method-neutral way. In the BABOK Guide v3 it is listed for tasks including Prioritize Requirements (5.3) and Analyze Potential Value and Recommend Solution (7.6), so questions often sit in Requirements Life Cycle Management or Requirements Analysis and Design Definition (30% of the exam). Our map of all 50 BABOK techniques shows its neighbours.
According to IIBA, the CBAP exam has 120 scenario and case-study questions in 210 minutes. Two things make backlog questions tricky:
- They are not about Scrum roles. The BABOK Guide does not assume a Product Owner or sprints. A question may describe a waterfall programme with a change backlog, and the answer still comes from the technique.
- They mix with nearby techniques. Prioritization (10.33), Estimation (10.19) and Item Tracking (10.26) all sit close to backlog management, and distractors use their names.
How backlog management works, step by step
Backlog management runs as a loop rather than a one-off activity.
- Capture items. Requirements, ideas, defects and change requests enter the backlog with enough context to understand them: who needs it, what it is, why it matters.
- Order the top of the list. Stakeholders and the team order items by value, risk, dependencies and cost of delay. The order at the top must be precise; lower down, rough groups are enough.
- Elaborate just in time. Items gain detail as they move up: acceptance criteria, models and estimates are added when the team is about to work on them, not months earlier.
- Estimate relatively. The people doing the work size the items near the top, often in relative units such as story points or T-shirt sizes.
- Take items from the top. Work is pulled from the top of the list, so effort always goes to the current most valuable items.
- Manage change. New items are added, obsolete ones removed, large ones split, and the order revisited whenever stakeholder needs or the context change.
Steps 2 and 3 are where BAs add the most value. Our articles on backlog refinement and estimation and relative sizing cover them in more depth.
Example: a change backlog in a non-agile programme
A bank is replacing its loan origination system on a fixed-scope, phased plan. Change requests keep arriving from compliance, branches and the digital team, far more than the release can absorb.
The BA sets up one change backlog instead of separate email threads:
| Item | Source | Value / risk | Size | Position |
|---|---|---|---|---|
| New affordability rule required by the regulator | Compliance | mandatory, deadline in Q2 | M | 1 |
| Pre-fill applicant data from core banking | Digital | high value, removes rekeying | L | 2 |
| Branch report on pending applications | Branches | medium value | S | 3 |
| Change logo on PDF letters | Marketing | low value | XS | 4 |
| Old request: fax confirmation | Unknown | no owner, no reason | ? | removed |
Each month the BA runs a short review with the sponsor and the delivery lead. Mandatory and high-value items move into the next release; the fax request is removed because nobody can say who needs it or why. The project stays phased, but the backlog makes the trade-offs visible and the decisions traceable, which is exactly what Prioritize Requirements (5.3) and the approval tasks in Requirements Life Cycle Management ask for.
What practitioners say
Practitioners repeat one message: a backlog only helps if it stays short, ordered and owned.
- In a September 2026 article on Adaptive US, CBAP trainer LN Mishra calls the backlog a central repository for requirements, but lists its limits: long lists overwhelm teams, estimates can create false expectations, and subjective ordering can drift away from business goals.
- On the ProductPlan blog, product manager Adrian Bryant describes deleting more than 600 backlog items; the team moved faster afterwards. His reasoning: "if an idea has high enough value for customers, it will come back."
- Felix Sargent, writing for the Pragmatic Institute, gives a simple filter for old items: "If it doesn't have a who, what and why, delete it."
- The Welsh Government's Centre for Digital Public Services teaches teams to add detail as items move up, to estimate the top items, and to involve the wider team in prioritisation so decisions can be challenged.
- An IISCM technique note on the Fhyzics blog frames backlog management as a way to record, track and prioritise remaining work in one authoritative list.
Common misconceptions
Most exam mistakes come from bringing Scrum assumptions into a BABOK question.
- Backlog management is only for agile teams. The BABOK Guide presents it as usable in any approach. A change backlog on a waterfall project is still backlog management.
- Every item must be fully specified. Detail should grow as an item rises in the order. Fully specifying the bottom of the list is waste, because many of those items will change or disappear.
- The backlog only holds user stories. It can hold any work item, including defects, technical work, research and change requests.
- Backlog management and Item Tracking are the same. Item Tracking (10.26) records issues, actions and decisions and follows them to closure; backlog management orders future work by value. A risk log is item tracking; a ranked list of features is a backlog.
- Prioritising once is enough. Managing changes to the backlog is one of the four elements. Order is revisited every time needs change.
Practice Questions
These are original questions written for this article.
Question 1
On a phased ERP programme, stakeholders send dozens of change requests by email, and the team works on whichever arrived last. What should the business analyst do first?
A. Freeze all change requests until go-live B. Collect the requests in a single ordered backlog and agree how items will be ranked C. Ask developers to estimate every request in detail D. Move the programme to Scrum
Answer: B. Backlog management works in any approach. One ordered list with an agreed ranking method makes the trade-offs visible. Detailed estimates for every item are wasteful, and changing the delivery approach is not needed.
Question 2
A team has a backlog of 900 items. Items near the bottom are fully specified with detailed acceptance criteria, while the top items lack estimates. What is the main problem?
A. The backlog has too few items B. Detail and estimates are concentrated where they are least useful C. Acceptance criteria should never be written for backlog items D. The backlog should be ordered alphabetically
Answer: B. Items should gain detail and estimates as they approach the top. Effort spent specifying low-priority items is likely to be wasted.
Question 3
Which statement best distinguishes Backlog Management (10.2) from Item Tracking (10.26)?
A. Backlog management orders future work by value; item tracking follows issues, actions and decisions to resolution B. Item tracking is used only in agile projects C. Backlog management is used only for defects D. They are two names for the same technique
Answer: A. Both keep lists, but they serve different purposes. A backlog is ranked by value to decide what to work on next; item tracking makes sure each issue or action has an owner and gets closed.
Related techniques
Backlog management depends on several other BABOK techniques. Prioritization (10.33) supplies the ordering methods, and Estimation (10.19) supplies sizes. User Stories (10.48) are a common item format; see user stories, job stories and decomposition. Acceptance and Evaluation Criteria (10.1) define when a backlog item is done; our deep dive on acceptance and evaluation criteria covers that technique. For release-level views of a backlog, story mapping is a useful companion.
Backlog questions also appear in Scrum certifications; if you are preparing for one as well, you can practise on our PSPO I practice exam.
FAQ
What is backlog management in the BABOK Guide?
It is technique 10.2: recording, tracking and ordering the work items that remain, so the most valuable ones are done first. Its four elements are items in the backlog, prioritization, estimation and managing changes to the backlog.
Is backlog management only used in agile projects?
No. The BABOK Guide treats it as approach-neutral. A change request backlog on a phased or waterfall programme uses the same technique, even without sprints or a Product Owner.
What can go into a backlog?
Any work item the team may do: requirements, user stories, features, defects, change requests, technical work or research. What matters is that each item is clear, ordered and traceable.
How detailed should backlog items be?
Only as detailed as their position requires. Items near the top need acceptance criteria and estimates; items further down can stay short until they move up.
Which CBAP knowledge area tests backlog management?
Mostly Requirements Life Cycle Management, in Prioritize Requirements, and Requirements Analysis and Design Definition, when the analyst recommends a solution. Expect scenarios where backlog management must be told apart from Item Tracking or Prioritization.
Sources
- IIBA: Certified Business Analysis Professional (CBAP)
- IIBA Knowledge Hub: BABOK Applied, Backlog Management
- Adaptive US: Backlog Management for Business Analysts
- ProductPlan: When to Declare Backlog Bankruptcy
- Pragmatic Institute: Delete It, Managing Your Backlog
- Centre for Digital Public Services (Wales): Building a product backlog
- Fhyzics: BA Techniques, Backlog Management