15 min of reading
Backlog Management Simulation
Start
Learning Outcomes
By the end of this simulation, you’ll be able to…
Explain the purpose of backlog management
Identify which items belong in the backlog by evaluating whether they provide stakeholder value
Describe how backlog items are adjusted as stakeholder needs or dependencies change
Interpret changes in backlog size to identify potential causes, such as increased demand or productivity shifts
Back
Next
Backlog management is the technique used to record, track, and prioritize work items that need to be completed when demand exceeds delivery capacity.
- is a living list of work items, including: requirements, defects, change requests, risk items, maintenance, and other work
- The backlog evolves as items are added, refined, prioritized, completed, or removed
- Multiple backlogs may exist
A backlog
In this interactive simulation, you will step into the role of Anna, a newly hired business analysis professional. Can you help Anna build a value-driven backlog?
Back
Next
Key Takeaways
How to use backlog management
Prioritize by relative importance
Use multi-phase prioritization
Add potentially valuable items
Items are ranked against each other so that the most critical ones rise to the top.
Start with broad labels like “high/medium/low,” then refine high-priority items with detailed rankings.
Items should offer potential stakeholder value before being added to the backlog.
Review backlog regularly
Refine just-in-time
Estimate effort as priority increases
Don’t overwork low-priority items; elaborate only when they’re close to being worked on.
Stakeholder needs change—review cycles help adjust priorities and ensure relevance.
As items approach the top, more detail and effort estimation are applied to support planning.
Choose items based on readiness and capacity
Remove or archive completed or dropped items
Track growth or decline
Backlog trends help diagnose whether demand is rising, productivity is falling, or delivery is improving.
Keep the backlog clean by removing irrelevant or completed items, with the option to re-add if needed.
When capacity opens up, select work considering priority, size, and interdependencies.
Back
Next
Anna is a new business analysis professional at an e-commerce company. After just two weeks on the job, she’s already overwhelmed by requests: 1) Marketing wants new dashboard filters 2) Customer support is reporting multiple bugs 3) Legal is demanding an urgent compliance update So, she walks over to her mentor James for help.
Hey James, I’m swamped. Everyone’s sending requests and saying it’s urgent. I don’t know where to start.
Classic case. Time to build a backlog—a prioritized list of all work items based on value and readiness.
Back
Next
Challenge 1: What should Anna do FIRST to begin managing the situation?
Write them all down in a backlog tool, tagging by type (feature, bug, or compliance)
Consider stakeholder value and add all items that have potential value to the product backlog
Ask each department to argue their case, then decide later
Start fixing customer support bugs immediately because they’re urgent
Back
Next
Now that Anna understands that the backlog collects potentially valuable items, let’s take it a step further. Anna's standing in front of the backlog board. She's got five requests in her hand, and she needs to decide where each one goes:
- High priority
- Low priority
- Not in the backlog
Let’s help her place them correctly.
* In this exercise, we’ll use a multi-phased prioritization approach, starting with categorization first, then moving into relative prioritization. This is just one way to approach prioritization, and different organizations may use different methods.
Back
Next
Challenge 2.1: Backlog Organizer
- Request: Add a cookie-consent banner at site entry (it currently triggers too late in the user journey).
- Stakeholder Value: Ensures compliance with data privacy regulation across the full user journey.
- Urgency: There’s talk that enforcement may begin in the next few weeks, so Legal wants this addressed soon.
- Impact: Late consent could lead to potential penalties in the future.
- Effort: Low (UI update + legal text).
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 1: Compliance Banner (Legal)
Low priority
Title
Add a cookie consent banner to meet upcoming privacy regulations.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.2: Backlog Organizer
- Request: Add regional filter in campaign dashboard.
- Stakeholder Value: Saves time for Marketing in reporting.
- Urgency: Needed next quarter, not tied to immediate KPIs.
- Impact: Current workaround (manual SQL) takes 2–3 hours each month.
- Effort: Medium (reporting pipeline update).
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 2: Dashboard Filter (Marketing)
Low priority
Title
Add a regional filter to the campaign dashboard for easier reporting.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.3: Backlog Organizer
- Request: Discount codes not applying for some customers.
- Stakeholder Value: Impacts user trust and revenue.
- Urgency: Constant feedback received.
- Impact: Finance claims 5% revenue loss weekly; Engineering says <1% users affected.
- Effort: Medium (root cause investigation needed)
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 3: Bug Report – Discount Codes (Support)
Low priority
Title
Fix the bug preventing certain users from applying discount codes at checkout.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.4: Backlog Organizer
- Request: Customers want a "Save for Later/Wishlist" function in carts.
- Stakeholder Value: Could boost engagement and repeat purchases.
- Urgency: No immediate urgency; Product Owner says roadmap is full this quarter.
- Impact: Long-term customer satisfaction and differentiation.
- Effort: High (new feature design + dev + QA).
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 4: Wishlist Feature (Customer Requests)
Low priority
Title
Add a "Saved for Later/Wishlist" function to the shopping cart.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.5: Backlog Organizer
- Request: Anna to present “Intro to BA” lunch-and-learn for interns.
- Stakeholder Value: Improves team knowledge but no product impact.
- Urgency: Manager wants it next month.
- Impact: Internal learning, not tied to product outcomes.
- Effort: Low (prep + delivery).
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 5: Internal Business Analysis Training (Manager)
Low priority
Title
Deliver an intro to business analysis session for interns.
Not in the backlog
Write a brief description here
Back
Next
I’ve added all the valuable items to the backlog, but now I’m wondering… some are well-described, and others are barely more than a title. Should I go through the entire list and fill in all the missing details?
Hmm, that depends. Do you expect to work on all of them soon?
Not really—some are probably months out. But I figured the cleaner the backlog, the better, right?
Clean is good. But consider this: how often do priorities shift after you’ve already spent time writing up something in detail?
Back
Next
Challenge 3: What’s the MOST PRACTICAL next step for Anna?
Tidy up the entire backlog now so it’s consistent and detailed
Create a standardized template and apply it to every item
Mark vague items as “unusable” and remove them
Leave most items as-is and focus on clarifying those likely to be picked up soon
Back
Next
Anna has sorted the backlog, but the real world is messy. Priorities shift quickly when new data, deadlines, or business pressures emerge. Several updates have just landed on her desk, so the backlog needs to be reorganized.
Back
Next
Challenge 4: Re-Rank the Backlog
- The government has finalized the new data privacy regulation, and it's scheduled to take effect in the coming weeks.
- Legal has advised that non-compliance will result in financial penalties, mandatory remediation orders, and potential restrictions on certain online operations until compliance is confirmed.
- An investigation by the engineers determined that the issue comes from an outdated payment gateway integration, which is already scheduled to be fully replaced in next month’s infrastructure upgrade.
- A temporary workaround (manual refunds) is already in place.
Bug report – discount codes (support)
Compliance banner (legal)
Title
Title
Use this side to give more information about a topic.
Use this side to give more information about a topic.
Subtitle
Subtitle
- During the quarterly town hall, the CEO publicly stated: “This quarter, we will deliver automated regional campaign reporting for marketing.”
- The marketing director followed up, stressing this commitment is now part of the board’s performance review metrics.
- A competitor recently rolled out a wishlist feature, and customer forums and reviews are praising it.
- Anna’s company has started seeing occasional mentions of a wishlist in support tickets and user interviews, but demand is still sporadic, not widespread.
Title
Title
Use this side to give more information about a topic.
Use this side to give more information about a topic.
Dashboard filter (marketing)
Wishlist feature (customers)
Subtitle
Subtitle
Back
Next
James, I’ve been keeping the backlog up to date— reviewing, prioritizing, cleaning up. But I noticed something interesting. We’re delivering consistently, but the backlog keeps growing. A lot of new items are coming in, and some low-priority stuff has been sitting untouched for weeks.
That’s not unusual. But here’s the key question: what might that pattern be telling you?
Hmm… maybe it’s not just about managing the list, but figuring out what the list is showing me?
Exactly. A backlog is like a dashboard. More than just tasks, it reflects how the team and the business are functioning.
Back
Next
Challenge 5: What insight should Anna take from this trend?
The backlog is too long and needs to be archived entirely
There may be rising demand or delivery slowdowns that need attention
The team should stop accepting new work until everything is cleared
Nothing is wrong; as long as top items are moving, the rest can be ignored
Back
Next
Wow! I hadn’t thought of it that way. The backlog is more than just a list of priorities. It’s also a window into how we’re working.
Now you’re thinking like a strategic business analysis professional. Backlog management involves both execution and insight.
Back
Recap
What have you learned about backlog management?
It keeps work visible and organized in fast-changing environments.
It encourages just-enough planning—refine only what’s needed, when needed.
It helps business analysis professionals and teams align with what stakeholders need now.
Prioritization isn't static. It must be periodically reviewed and adjusted as stakeholder needs, deadlines, and external pressures evolve.
Backlog items must be prioritized relative to each other, with the top items reflecting the highest business value and risk.
In practice, priorities shift quickly: a regulatory deadline confirmed by government, a CEO’s public promise, or a competitor’s launch can flip the backlog order overnight.
Back
Next
Back
End
Congratulations, You’ve Levelled Up!
Start Over
Oh no...
That's an overreaction. Archiving everything could mean losing valid, valuable items.
✅ Yeah! Correct!
This request holds potential value and is appropriate to include in the backlog. However, given current priorities and its limited impact on early marketing decisions, it should remain in the lower tier for now. It's acceptable for lower-priority items to start with minimal detail—they can be progressively elaborated as their relative value or urgency increases.
✅ Nice work!
This aligns with the “just-in-time refinement” principle: only top-priority items need detail now. Time and effort are better spent preparing what’s actually going to be worked on.
✅ You got it!
Customer value should be captured, even if details are light right now. The backlog items at the bottom reflect lower priorities and are refined later.
Uh oh…
The defects are valid backlog items. Even if rare, they must be captured and reviewed.
Hmm… not bad
This creates visibility, which is a good instinct—but a backlog isn’t just a dumping ground. According to backlog management practices, only items with potential stakeholder value should be formally included. If everything is added without filtering, the backlog can grow unwieldy, making it difficult to prioritize, track, and periodically review effectively. Remember, backlog management also involves deciding what NOT to add.
Example of a Backlog
✅ You're right!
This reflects the BABOK Guide. Backlog trends reveal system-level issues such as increasing demand, bottlenecks, or persistent low-value clutter. It’s not just the item count that matters, but also what it conveys.
Hmm…
This neglects trend analysis and backlog health, which are essential for strategic delivery planning.
✅ Yeah! You got it.
An item is added to the backlog if it has potential value to a stakeholder—that’s the foundation. This ensures the backlog remains meaningful and manageable. By capturing items that may provide value, you create the space for prioritization, estimation, and regular review without unnecessary clutter. Remember that backlog management is an ongoing process. Items are described, refined, tracked, and reprioritized as needs change. They're eventually removed when completed or deemed unnecessary.
Not really...
This involves unnecessary effort on low-priority items that might never be developed.
Uh oh...
While templates can help, creating detailed documentation too early goes against the idea of progressive elaboration.
Careful…
This may create friction with stakeholders and ignore the root cause (e.g., resource gaps or process inefficiencies).
✅ Yeah! Correct!
The BABOK Guide lists defects as backlog items, and those with potential financial impact should be near the top in this case.
Uh oh…
The backlog items are added if they provide potential stakeholder value, and they can include activities such as conducting a presentation. This training presentation is valuable because it supports internal capability building, but it doesn’t directly change the product or customer experience. In practice, teams often maintain more than one backlog for different types of work, so this item fits better in an internal or team backlog rather than the product backlog Anna's managing.
Hmm… not quite.
The backlog should be periodically reviewed, but items with major risk should already be high priority. In this case, compliance updates must be visible at the top.
To help you with the practice, here’s some business context:The company runs a mid-sized e-commerce platform operating in a regulated environment. It aims to protect customer trust, remain compliant, sustain revenue performance, and improve internal efficiency where meaningful. Teams typically balance:
- Compliance expectations
- Customer impact and revenue effects
- Operational efficiency
- Existing roadmap commitments and team capacity
✅ Correct!
The training task is valid work, but it doesn’t belong in the product backlog. In practice, teams often use multiple backlogs to separate product work from internal operational tasks, so this would be tracked in an internal or ops backlog rather than alongside product changes.
Uh oh...
Not all vague items are valueless. They may become important later and can be refined and developed at that stage.
Careful…
The priorities shift with stakeholder needs, but convenience isn’t top priority when compliance and revenue are at stake.
Uh oh… that’s risky.
The items are added if they have stakeholder value. Regulatory compliance always has value, so leaving it out is a mistake.
Uh oh…
The backlog is a communication tool. It's better to backlog something than ignore stakeholder needs.
Hmm…
This might undervalue it. The items must be periodically reviewed. You could backlog it lower for now, but finance’s claim suggests it should be tracked higher until disproved.
✅ Yeah! Correct!
The backlog items with the highest business value and risk go to the top. In this case, compliance is non-negotiable as it carries regulatory consequences.
Hmm…
The training supports internal capability building (e.g., team skills), but it doesn't directly contribute to a product change or customer outcome. Many organizations maintain separate backlogs for different types of work—while this kind of training does have stakeholder value, it typically belongs in an internal or team backlog rather than the product backlog.
Uh oh…
This is reactive and skips the purpose of backlog management: to record, track, and prioritize remaining work items. Jumping straight into execution without documenting and comparing items removes the ability to evaluate relative value, urgency, or dependencies. You risk ignoring higher-value or higher-risk work that should come first.
Uh oh...
While stakeholder input matters, backlog management isn’t about negotiation in the moment. It’s about applying a consistent and transparent process: capturing items with value, describing them just enough to track and estimate, and prioritizing them in relation to all others. Letting stakeholders compete for your attention may create bias, not balance.
Uh oh…
Ignoring customer input reduces transparency. The backlog communicates both current and future priorities.
Not quite.
The backlog prioritization must reflect urgency and strategic alignment. This is a valuable item, but not an immediate one.
[Released] Backlog Management Simulation-rev2
Ilaria Ma
Created on November 19, 2025
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Feedback and Leadership Simulation
View
Product Purchase Simulation
View
Onboarding Quiz for New Employees
View
Work Style Quiz
View
The Meeting Microlearning
View
The Meeting Microlearning Mobile
View
Customer Management Simulation
Explore all templates
Transcript
15 min of reading
Backlog Management Simulation
Start
Learning Outcomes
By the end of this simulation, you’ll be able to…
Explain the purpose of backlog management
Identify which items belong in the backlog by evaluating whether they provide stakeholder value
Describe how backlog items are adjusted as stakeholder needs or dependencies change
Interpret changes in backlog size to identify potential causes, such as increased demand or productivity shifts
Back
Next
Backlog management is the technique used to record, track, and prioritize work items that need to be completed when demand exceeds delivery capacity.
A backlog
In this interactive simulation, you will step into the role of Anna, a newly hired business analysis professional. Can you help Anna build a value-driven backlog?
Back
Next
Key Takeaways
How to use backlog management
Prioritize by relative importance
Use multi-phase prioritization
Add potentially valuable items
Items are ranked against each other so that the most critical ones rise to the top.
Start with broad labels like “high/medium/low,” then refine high-priority items with detailed rankings.
Items should offer potential stakeholder value before being added to the backlog.
Review backlog regularly
Refine just-in-time
Estimate effort as priority increases
Don’t overwork low-priority items; elaborate only when they’re close to being worked on.
Stakeholder needs change—review cycles help adjust priorities and ensure relevance.
As items approach the top, more detail and effort estimation are applied to support planning.
Choose items based on readiness and capacity
Remove or archive completed or dropped items
Track growth or decline
Backlog trends help diagnose whether demand is rising, productivity is falling, or delivery is improving.
Keep the backlog clean by removing irrelevant or completed items, with the option to re-add if needed.
When capacity opens up, select work considering priority, size, and interdependencies.
Back
Next
Anna is a new business analysis professional at an e-commerce company. After just two weeks on the job, she’s already overwhelmed by requests: 1) Marketing wants new dashboard filters 2) Customer support is reporting multiple bugs 3) Legal is demanding an urgent compliance update So, she walks over to her mentor James for help.
Hey James, I’m swamped. Everyone’s sending requests and saying it’s urgent. I don’t know where to start.
Classic case. Time to build a backlog—a prioritized list of all work items based on value and readiness.
Back
Next
Challenge 1: What should Anna do FIRST to begin managing the situation?
Write them all down in a backlog tool, tagging by type (feature, bug, or compliance)
Consider stakeholder value and add all items that have potential value to the product backlog
Ask each department to argue their case, then decide later
Start fixing customer support bugs immediately because they’re urgent
Back
Next
Now that Anna understands that the backlog collects potentially valuable items, let’s take it a step further. Anna's standing in front of the backlog board. She's got five requests in her hand, and she needs to decide where each one goes:
- High priority
- Low priority
- Not in the backlog
Let’s help her place them correctly.* In this exercise, we’ll use a multi-phased prioritization approach, starting with categorization first, then moving into relative prioritization. This is just one way to approach prioritization, and different organizations may use different methods.
Back
Next
Challenge 2.1: Backlog Organizer
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 1: Compliance Banner (Legal)
Low priority
Title
Add a cookie consent banner to meet upcoming privacy regulations.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.2: Backlog Organizer
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 2: Dashboard Filter (Marketing)
Low priority
Title
Add a regional filter to the campaign dashboard for easier reporting.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.3: Backlog Organizer
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 3: Bug Report – Discount Codes (Support)
Low priority
Title
Fix the bug preventing certain users from applying discount codes at checkout.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.4: Backlog Organizer
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 4: Wishlist Feature (Customer Requests)
Low priority
Title
Add a "Saved for Later/Wishlist" function to the shopping cart.
Not in the backlog
Write a brief description here
Back
Next
Challenge 2.5: Backlog Organizer
Where would you place this item on the product backlog board?
Use this side of the card to provide more information about a topic. Focus on one concept. Make learning and communication more efficient.
High priority
Request 5: Internal Business Analysis Training (Manager)
Low priority
Title
Deliver an intro to business analysis session for interns.
Not in the backlog
Write a brief description here
Back
Next
I’ve added all the valuable items to the backlog, but now I’m wondering… some are well-described, and others are barely more than a title. Should I go through the entire list and fill in all the missing details?
Hmm, that depends. Do you expect to work on all of them soon?
Not really—some are probably months out. But I figured the cleaner the backlog, the better, right?
Clean is good. But consider this: how often do priorities shift after you’ve already spent time writing up something in detail?
Back
Next
Challenge 3: What’s the MOST PRACTICAL next step for Anna?
Tidy up the entire backlog now so it’s consistent and detailed
Create a standardized template and apply it to every item
Mark vague items as “unusable” and remove them
Leave most items as-is and focus on clarifying those likely to be picked up soon
Back
Next
Anna has sorted the backlog, but the real world is messy. Priorities shift quickly when new data, deadlines, or business pressures emerge. Several updates have just landed on her desk, so the backlog needs to be reorganized.
Back
Next
Challenge 4: Re-Rank the Backlog
Bug report – discount codes (support)
Compliance banner (legal)
Title
Title
Use this side to give more information about a topic.
Use this side to give more information about a topic.
Subtitle
Subtitle
Title
Title
Use this side to give more information about a topic.
Use this side to give more information about a topic.
Dashboard filter (marketing)
Wishlist feature (customers)
Subtitle
Subtitle
Back
Next
James, I’ve been keeping the backlog up to date— reviewing, prioritizing, cleaning up. But I noticed something interesting. We’re delivering consistently, but the backlog keeps growing. A lot of new items are coming in, and some low-priority stuff has been sitting untouched for weeks.
That’s not unusual. But here’s the key question: what might that pattern be telling you?
Hmm… maybe it’s not just about managing the list, but figuring out what the list is showing me?
Exactly. A backlog is like a dashboard. More than just tasks, it reflects how the team and the business are functioning.
Back
Next
Challenge 5: What insight should Anna take from this trend?
The backlog is too long and needs to be archived entirely
There may be rising demand or delivery slowdowns that need attention
The team should stop accepting new work until everything is cleared
Nothing is wrong; as long as top items are moving, the rest can be ignored
Back
Next
Wow! I hadn’t thought of it that way. The backlog is more than just a list of priorities. It’s also a window into how we’re working.
Now you’re thinking like a strategic business analysis professional. Backlog management involves both execution and insight.
Back
Recap
What have you learned about backlog management?
It keeps work visible and organized in fast-changing environments.
It encourages just-enough planning—refine only what’s needed, when needed.
It helps business analysis professionals and teams align with what stakeholders need now.
Prioritization isn't static. It must be periodically reviewed and adjusted as stakeholder needs, deadlines, and external pressures evolve.
Backlog items must be prioritized relative to each other, with the top items reflecting the highest business value and risk.
In practice, priorities shift quickly: a regulatory deadline confirmed by government, a CEO’s public promise, or a competitor’s launch can flip the backlog order overnight.
Back
Next
Back
End
Congratulations, You’ve Levelled Up!
Start Over
Oh no...
That's an overreaction. Archiving everything could mean losing valid, valuable items.
✅ Yeah! Correct!
This request holds potential value and is appropriate to include in the backlog. However, given current priorities and its limited impact on early marketing decisions, it should remain in the lower tier for now. It's acceptable for lower-priority items to start with minimal detail—they can be progressively elaborated as their relative value or urgency increases.
✅ Nice work!
This aligns with the “just-in-time refinement” principle: only top-priority items need detail now. Time and effort are better spent preparing what’s actually going to be worked on.
✅ You got it!
Customer value should be captured, even if details are light right now. The backlog items at the bottom reflect lower priorities and are refined later.
Uh oh…
The defects are valid backlog items. Even if rare, they must be captured and reviewed.
Hmm… not bad
This creates visibility, which is a good instinct—but a backlog isn’t just a dumping ground. According to backlog management practices, only items with potential stakeholder value should be formally included. If everything is added without filtering, the backlog can grow unwieldy, making it difficult to prioritize, track, and periodically review effectively. Remember, backlog management also involves deciding what NOT to add.
Example of a Backlog
✅ You're right!
This reflects the BABOK Guide. Backlog trends reveal system-level issues such as increasing demand, bottlenecks, or persistent low-value clutter. It’s not just the item count that matters, but also what it conveys.
Hmm…
This neglects trend analysis and backlog health, which are essential for strategic delivery planning.
✅ Yeah! You got it.
An item is added to the backlog if it has potential value to a stakeholder—that’s the foundation. This ensures the backlog remains meaningful and manageable. By capturing items that may provide value, you create the space for prioritization, estimation, and regular review without unnecessary clutter. Remember that backlog management is an ongoing process. Items are described, refined, tracked, and reprioritized as needs change. They're eventually removed when completed or deemed unnecessary.
Not really...
This involves unnecessary effort on low-priority items that might never be developed.
Uh oh...
While templates can help, creating detailed documentation too early goes against the idea of progressive elaboration.
Careful…
This may create friction with stakeholders and ignore the root cause (e.g., resource gaps or process inefficiencies).
✅ Yeah! Correct!
The BABOK Guide lists defects as backlog items, and those with potential financial impact should be near the top in this case.
Uh oh…
The backlog items are added if they provide potential stakeholder value, and they can include activities such as conducting a presentation. This training presentation is valuable because it supports internal capability building, but it doesn’t directly change the product or customer experience. In practice, teams often maintain more than one backlog for different types of work, so this item fits better in an internal or team backlog rather than the product backlog Anna's managing.
Hmm… not quite.
The backlog should be periodically reviewed, but items with major risk should already be high priority. In this case, compliance updates must be visible at the top.
To help you with the practice, here’s some business context:The company runs a mid-sized e-commerce platform operating in a regulated environment. It aims to protect customer trust, remain compliant, sustain revenue performance, and improve internal efficiency where meaningful. Teams typically balance:
✅ Correct!
The training task is valid work, but it doesn’t belong in the product backlog. In practice, teams often use multiple backlogs to separate product work from internal operational tasks, so this would be tracked in an internal or ops backlog rather than alongside product changes.
Uh oh...
Not all vague items are valueless. They may become important later and can be refined and developed at that stage.
Careful…
The priorities shift with stakeholder needs, but convenience isn’t top priority when compliance and revenue are at stake.
Uh oh… that’s risky.
The items are added if they have stakeholder value. Regulatory compliance always has value, so leaving it out is a mistake.
Uh oh…
The backlog is a communication tool. It's better to backlog something than ignore stakeholder needs.
Hmm…
This might undervalue it. The items must be periodically reviewed. You could backlog it lower for now, but finance’s claim suggests it should be tracked higher until disproved.
✅ Yeah! Correct!
The backlog items with the highest business value and risk go to the top. In this case, compliance is non-negotiable as it carries regulatory consequences.
Hmm…
The training supports internal capability building (e.g., team skills), but it doesn't directly contribute to a product change or customer outcome. Many organizations maintain separate backlogs for different types of work—while this kind of training does have stakeholder value, it typically belongs in an internal or team backlog rather than the product backlog.
Uh oh…
This is reactive and skips the purpose of backlog management: to record, track, and prioritize remaining work items. Jumping straight into execution without documenting and comparing items removes the ability to evaluate relative value, urgency, or dependencies. You risk ignoring higher-value or higher-risk work that should come first.
Uh oh...
While stakeholder input matters, backlog management isn’t about negotiation in the moment. It’s about applying a consistent and transparent process: capturing items with value, describing them just enough to track and estimate, and prioritizing them in relation to all others. Letting stakeholders compete for your attention may create bias, not balance.
Uh oh…
Ignoring customer input reduces transparency. The backlog communicates both current and future priorities.
Not quite.
The backlog prioritization must reflect urgency and strategic alignment. This is a valuable item, but not an immediate one.