New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA PK0-005 Exam - Topic 2 Question 34 Discussion

Actual exam question for CompTIA's PK0-005 exam
Question #: 34
Topic #: 2
[All PK0-005 Questions]

A developer focused on a single story during an entire sprint. The story was underestimated and, therefore, was not completed. Which of the following steps should the Scrum team take next?

Show Suggested Answer Hide Answer
Suggested Answer: B

The Scrum team should break the stories into workable items that can be completed within one sprint, which is a time-boxed period of 7 to 30 days, during which the team delivers a potentially releasable product increment. Breaking the stories into smaller and more manageable items can help the team to estimate them more accurately, plan them more effectively, and deliver them more reliably. Breaking the stories also aligns with the agile principle of delivering working software frequently and satisfying the customer through early and continuous delivery of valuable software.

The other options are not the best steps for the Scrum team to take next. Assigning more resources to complete similar stories in the future may not solve the problem of underestimation, and may introduce additional complexity and communication overhead. Extending the sprint duration when required with the approval of the product owner may compromise the consistency and predictability of the Scrum process, and may delay the feedback and validation from the stakeholders. Releasing the current progress into production and carrying over the rest of the code for the next sprint may result in an incomplete or unstable product increment, and may violate the definition of done, which is a shared understanding of the quality criteria that the product increment must meet. Reference = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 5: Project Scope Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 5: Project Scope Management2; The 3 Scrum Roles and Responsibilities Explained3; Implementation of Scrum - 7 Steps for an Effective Process4


Contribute your Thoughts:

0/2000 characters
Stefany
3 months ago
More resources won't solve the estimation issue.
upvoted 0 times
...
Delmy
3 months ago
Wait, can they really just extend the sprint like that?
upvoted 0 times
...
Jennie
3 months ago
I think releasing partial progress could confuse users.
upvoted 0 times
...
Albina
4 months ago
Totally agree, extending the sprint isn't a good idea!
upvoted 0 times
...
Hoa
4 months ago
Sounds like they should break the stories down better.
upvoted 0 times
...
Long
4 months ago
Assigning more resources sounds tempting, but I recall that it doesn't always solve the problem. Maybe we should focus on better estimating first.
upvoted 0 times
...
Casandra
4 months ago
I think we had a practice question about releasing incomplete work. Option D seems risky, but it might be necessary if the team is really stuck.
upvoted 0 times
...
Mable
4 months ago
I'm not sure about extending the sprint. I feel like that could lead to more issues down the line. Isn't it better to stick to the timebox?
upvoted 0 times
...
Ivette
5 months ago
I remember we discussed how breaking stories into smaller tasks can help with estimation. So, I think option B makes sense.
upvoted 0 times
...
Mica
5 months ago
I'm confident that option B is the correct answer here. Underestimating a story is a common issue, and the Scrum team should focus on breaking down the work into smaller, more achievable tasks that can be completed within a single sprint.
upvoted 0 times
...
Alfreda
5 months ago
Ah, I see. The question is asking about the next steps the Scrum team should take. I think option B, breaking the stories into workable items, is the best approach here. That way they can complete the work within a single sprint.
upvoted 0 times
...
Elza
5 months ago
Hmm, I'm a bit unsure about this one. The question mentions the story was underestimated, so I'm not sure if assigning more resources is the right approach. Maybe breaking the story into smaller pieces would be better?
upvoted 0 times
...
Olene
5 months ago
This seems like a straightforward Scrum question. I think the key is to focus on the Scrum principles of delivering working software and continuous improvement.
upvoted 0 times
...
Merri
5 months ago
Extending the sprint duration? I'm not sure that's the right call. The Scrum framework emphasizes delivering working software within a fixed time-box. I'd go with option B and break the story down into smaller, more manageable pieces.
upvoted 0 times
...
Marvel
5 months ago
This question seems straightforward. I think the key is to focus on the customization steps for identifying duplicates during change request processing.
upvoted 0 times
...
Eden
1 year ago
Wow, D) really? Releasing partial code? That's like trying to ship a car with no wheels. I'll stick with B), thanks.
upvoted 0 times
Kip
1 year ago
Assigning more resources may not always be the solution.
upvoted 0 times
...
Barbra
1 year ago
It's important to focus on completing tasks within one sprint.
upvoted 0 times
...
Lucia
1 year ago
Breaking stories into workable items is a better approach.
upvoted 0 times
...
Yen
1 year ago
I agree, releasing partial code is risky.
upvoted 0 times
...
...
Terina
1 year ago
B) Break the stories into workable items that can be completed within one sprint. Trying to fit a story that's too big into a single sprint is just asking for trouble.
upvoted 0 times
...
Lera
1 year ago
D) Release the current progress into production and carry over the rest of the code for the next sprint. Might as well ship what we have and pick up the rest later.
upvoted 0 times
...
Alverta
1 year ago
C) Extend the sprint duration when required with the approval of the product owner. Completing the story should be the priority, even if it means adjusting the sprint timeline.
upvoted 0 times
...
Johna
1 year ago
B) Break the stories into workable items that can be completed within one sprint. This seems like the best approach to avoid similar issues in the future.
upvoted 0 times
...
Coleen
1 year ago
I'm going with D. Ship it and let the users find the bugs. That's what quality assurance is for, right?
upvoted 0 times
...
Bulah
1 year ago
B, definitely B. Wouldn't want to end up like the developer in the question, stuck in a sprint-long story black hole.
upvoted 0 times
Farrah
1 year ago
Let's make sure to communicate with the product owner about the changes we plan to make.
upvoted 0 times
...
Noelia
1 year ago
It's important to learn from this experience and adjust our approach for future sprints.
upvoted 0 times
...
Cheryll
1 year ago
Agreed, that way we can ensure each item is completed within the sprint.
upvoted 0 times
...
Maybelle
1 year ago
Yes, breaking the stories into smaller items is definitely the way to go.
upvoted 0 times
...
...
Jody
1 year ago
A? Really? Throwing more resources at the problem? That's like trying to put out a fire with a flamethrower.
upvoted 0 times
...
Tequila
1 year ago
C is the obvious choice. Extend the sprint, get the job done, and make the product owner happy. Scrum is all about flexibility, after all.
upvoted 0 times
...
Merilyn
1 year ago
I don't know, D looks tempting. Ship what we have and worry about the rest later. That's how we get things done around here!
upvoted 0 times
...
Clement
1 year ago
B seems like the way to go. Break those stories down and make them more manageable. That's the Agile way, right?
upvoted 0 times
Alita
1 year ago
Agreed, it's important to have manageable tasks to ensure successful completion in each sprint.
upvoted 0 times
...
Stevie
1 year ago
It will help the team better estimate and complete the work within a single sprint.
upvoted 0 times
...
Royal
1 year ago
Yes, breaking down the stories into smaller tasks is definitely the Agile way to go.
upvoted 0 times
...
...
Denny
1 year ago
But what if we need more time? Shouldn't we extend the sprint duration?
upvoted 0 times
...
Scot
1 year ago
I agree with Glen. It will help us better estimate and complete the work.
upvoted 0 times
...
Glen
1 year ago
I think we should break the stories into workable items.
upvoted 0 times
...

Save Cancel