Discuss Scrum PSM-II Exam Topic 2 Question 69

Your organization has announced a release to its user base three Sprints from now To be able to include all functionality in the release, work needs to accelerate. The Product Owner puts some testing from the Definition of Done on hold for the next three Sprints, while adding a generic item to the Product Backlog to resolve this in a future release.

The Developers object that this will lead to technical debt. Select two ways that explain the impact of technical debt to the Product Owner.

(choose the best two answers)

AFeature development of a next release is not allowed to start as long as there is technical debt from the current release. The Product Owner should first accept this impact before the Definition of Done can be reduced.

BA generic Product Backlog item is not good enough. The amount of technical
debt will have to be calculated and estimated much more precisely, so the total
amount of extra work that needs to be budgeted is well known.

CReleasing the version creates false assumptions about the actual state of the
system. This is likely to result in interruptions during future Sprints in order to react to unforeseen problems arising from not having met the Definition of Done.

DAs development progresses and functionality is added upon the reduced
Definition of Done, unknown errors will creep in. The system becomes more
difficult to stabilize. Work for the actual release as well as future releases Will be slowed down in unpredictable ways.

Suggested Answer: C, D

Technical debt is the implied cost of rework caused by choosing an easy solution now instead of a better approach that would take longer1. Reducing the Definition of Done for the next three Sprints will create technical debt, which will have negative impacts on the product quality, value, and delivery. Two ways to explain these impacts to the Product Owner are:

Releasing the version creates false assumptions about the actual state of the system.This is likely to result in interruptions during future Sprints in order to react to unforeseen problems arising from not having met the Definition of Done2. This will reduce the transparency, predictability, and adaptability of the Scrum process, and compromise the trust and satisfaction of the customers and stakeholders.

As development progresses and functionality is added upon the reduced Definition of Done, unknown errors will creep in. The system becomes more difficult to stabilize.Work for the actual release as well as future releases will be slowed down in unpredictable ways3. This will increase the complexity, risk, and cost of the product development, and lower the value and quality of the product.

What is Technical Debt in Scrum? | StarAgile, section ''The technical debt is created when''.

Technical Debt & Scrum: Who Is Responsible? | Scrum.org, section ''What Is Technical Debt?''.

Managing Technical Debt in a Scrum Project | SCRUMstudy Blog, section ''Technical debt accrues''.

Get Premium PSM-II Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

37 comments · newest first

Micaela 10 months ago

Feature development shouldn't be stalled by debt, that's just bad practice!

Bronwyn 11 months ago

If we skip testing now, future Sprints will be a mess for sure.

Layla 11 months ago

Wait, so we’re just ignoring the Definition of Done? That seems risky.

Detra 11 months ago

Totally agree, technical debt will bite us later.

Carey 11 months ago

A generic backlog item won't cut it. We need precise estimates!

Laurel 12 months ago

I vaguely recall that A might not be the best option. It seems too rigid to say we can't start new features at all because of technical debt.

Maxima 12 months ago

I feel like D might be relevant as well. If we reduce the Definition of Done, it could lead to more errors down the line, which would slow everything down.

Alaine 12 months ago

I'm not entirely sure, but I think B makes sense too. We can't just leave technical debt as a vague item; it needs proper estimation.

Alex 1 year ago

I remember discussing how technical debt can really impact future sprints, especially if we don't meet the Definition of Done. It feels like C could be a strong choice.

Bea 1 year ago

I'm leaning towards answers C and D. They both emphasize how technical debt can create unpredictability and make the system harder to maintain going forward. That seems like a strong argument to present to the Product Owner.

Karl 1 year ago

I'm a bit confused by the wording of option A. Doesn't the Product Owner have the authority to make decisions about the Definition of Done? I'm not sure I fully understand the impact it's describing.

Walker 1 year ago

I think the key here is to focus on the long-term impact of technical debt. Answers C and D seem to capture that well, highlighting how it can lead to unforeseen problems and slow down future development.

Frederica 1 year ago

Option B makes a good point about needing to quantify the technical debt more precisely. A generic backlog item doesn't give the Product Owner a clear picture of the additional work required.

Laila 1 year ago

Okay, I'm pretty confident the answer is D. Collaborative Filtering. That's the algorithm that uses data about similar users to recommend products, right?

Edna 1 year ago

Okay, let's see. The target server has to receive the deployment command and perform the actual deployment, that seems like a given. But what else could be common across all three modes?

Alecia 2 years ago

I'm with the Developers on this one. The Product Owner is trying to cut corners and that's never a good idea. Option A is the way to go - the technical debt has to be addressed before any new features can be added.

Helene 2 years ago

Haha, the Product Owner is really trying to pull a fast one here! 'Oh, let's just skip a few testing steps, what could go wrong?' Rookie mistake, my friend. Option D is spot on - the system is going to become a real mess.

Ryan 2 years ago

↳ replying to Helene

Option D is a clear warning sign of the chaos that could ensue.

Huey 2 years ago

↳ replying to Helene

The Product Owner needs to understand the long-term consequences of cutting corners.

Cecily 2 years ago

↳ replying to Helene

Definitely, technical debt will pile up and cause major issues down the line.

Theron 2 years ago

↳ replying to Helene

I agree, skipping testing steps is a recipe for disaster.

Kanisha 2 years ago

Why would the Product Owner even consider reducing the Definition of Done? That's just asking for trouble. The Developers are right - this is going to lead to a lot of technical debt and problems down the line.

Melda 2 years ago

↳ replying to Kanisha

Developers need to communicate the risks of reducing the Definition of Done to the Product Owner.

Denae 2 years ago

↳ replying to Kanisha

It's important for the Product Owner to understand the long-term consequences of technical debt.

Nilsa 2 years ago

↳ replying to Kanisha

Product Owner may be under pressure to deliver more features quickly.

Silva 2 years ago

↳ replying to Kanisha

Developer 2: Technical debt will slow down future releases and create unknown errors.

Bernadine 2 years ago

↳ replying to Kanisha

Developer 1: Reducing the Definition of Done will lead to technical debt.

Mariann 2 years ago

↳ replying to Kanisha

Product Owner: We need to accelerate work to meet the release deadline.

Micaela 2 years ago

Yes, I think option D highlights the importance of maintaining a high level of quality in each release to avoid future problems.

Irma 2 years ago

I believe option D is the best explanation of the impact of technical debt. Unknown errors creeping in can really slow down future releases.

My 2 years ago

I agree with you, Micaela. It's important to address technical debt before moving on to new features.

Vivan 2 years ago

I agree with B. We need to quantify the technical debt and account for it properly. A generic backlog item just won't cut it. The Product Owner has to be aware of the real cost.

Micaela 2 years ago

I think technical debt is a serious issue that can impact future releases.

Dalene 2 years ago

Option C makes the most sense. Releasing a version with technical debt will definitely lead to future issues and interruptions. The Product Owner needs to understand this impact before making any changes to the Definition of Done.

Deane 2 years ago

↳ replying to Dalene

Agreed, it's important to consider the long-term consequences of technical debt on the development process.

Micaela 2 years ago

↳ replying to Dalene

The Product Owner needs to understand this impact before making any changes to the Definition of Done.

Sarah 2 years ago

↳ replying to Dalene

Option C makes the most sense. Releasing a version with technical debt will definitely lead to future issues and interruptions.

Scrum PSM-II Exam - Topic 2 Question 69 Discussion