Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scaled Agile SAFe-SASM Exam - Topic 1 Question 15 Discussion

A team integrates and tests the Stories on the last day of the Iteration. This has become a pattern for the last three Iterations. Why is this considered an anti-pattern?
A) Because the team is waterfalling the Iteration
B) Because the team demonstrates the full Stories to the Product Owner during the Iteration review
C) Because the team consistently meets their commitments, and the Product Owner accepts the Stories
D) Because it is difficult to manage dependencies with other teams

Scaled Agile SAFe-SASM Exam - Topic 1 Question 15 Discussion

Actual exam question for Scaled Agile's SAFe-SASM exam
Question #: 15
Topic #: 1
[All SAFe-SASM Questions]

A team integrates and tests the Stories on the last day of the Iteration. This has become a pattern for the last three Iterations. Why is this considered an anti-pattern?

Show Suggested Answer Hide Answer
Suggested Answer: A

Waterfalling the Iteration: The term 'waterfalling' in an Agile context refers to the anti-pattern where teams delay integration, testing, and other critical activities until the end of the iteration, mimicking the Waterfall model of sequential phases.

Agile Practice: In Agile, the goal is to continuously integrate and test stories throughout the iteration. This practice ensures that issues are identified and addressed early, and the product increment is always in a potentially shippable state.

Anti-pattern Explanation: Integrating and testing stories only on the last day of the iteration means the team is not practicing continuous integration. This can lead to hidden defects, reduced quality, and last-minute rushes that jeopardize the team's ability to meet commitments effectively.

SAFe Scrum Master Reference:

SAFe emphasizes continuous integration and regular testing as key practices to maintain quality and agility. Delaying these activities to the end of the iteration undermines these principles and can lead to significant issues.


by Jennifer at Nov 18, 2024, 11:29 AM

Limited Time Offer

25%

Off

Get Premium SAFe-SASM Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paulene
9 months ago
Surprised this has been a pattern for three iterations!
upvoted 0 times
...
Tien
9 months ago
Managing dependencies is a nightmare when you do it this way.
upvoted 0 times
...
Eleni
10 months ago
Wait, are they really meeting commitments if it's all last minute?
upvoted 0 times
...
Ronnie
10 months ago
Totally agree, integration should happen earlier!
upvoted 0 times
...
Halina
10 months ago
It's a classic case of waterfalling.
upvoted 0 times
...
Heike
10 months ago
I feel like the Product Owner should be involved throughout, not just at the end. But I’m not clear if that’s the main reason it’s an anti-pattern.
upvoted 0 times
...
Audra
10 months ago
I thought we practiced a question similar to this, and it was about how it affects the team's ability to adapt during the Iteration.
upvoted 0 times
...
Norah
11 months ago
I’m not entirely sure, but I think it might have to do with how dependencies can pile up if they wait until the last day.
upvoted 0 times
...
Rebecka
11 months ago
I remember we discussed how integrating at the end can lead to issues with quality and feedback. It feels like a waterfall approach.
upvoted 0 times
...
Devorah
11 months ago
I've got this one. The anti-pattern here is that the team is delaying integration and testing until the end, which means they won't be able to identify and fix issues early on. Agile is about delivering working software incrementally, not all at once at the end.
upvoted 0 times
...
Deonna
11 months ago
This is a good one. The key is that by waiting until the last day, the team is missing out on the opportunity to get early feedback and make adjustments. Agile is all about adapting based on frequent inspection and adaptation.
upvoted 0 times
...
Crista
11 months ago
Ah, I see what they're getting at. Integrating and testing at the last minute goes against the Agile value of continuous integration and testing throughout the iteration. It's a sign the team is falling into a waterfall-like approach.
upvoted 0 times
...
Sherrell
11 months ago
Hmm, I'm a bit confused on this one. I know Agile is all about delivering working software frequently, but I'm not sure why waiting until the last day would be a problem. I'll have to re-read the question carefully.
upvoted 0 times
...
Lisha
11 months ago
This seems like a tricky one. I'll need to think through the key principles of Agile and why integrating and testing at the last minute would be considered an anti-pattern.
upvoted 0 times
...
Bonita
2 years ago
Waterfalling the Iteration? Sounds like they're trying to bring back the good old days of waterfall development. Where's the Agile spirit, people?
upvoted 0 times
Hannah
2 years ago
B) Because the team demonstrates the full Stories to the Product Owner during the Iteration review
upvoted 0 times
...
Tiffiny
2 years ago
A) Because the team is waterfalling the Iteration
upvoted 0 times
...
...
Tanesha
2 years ago
Integrating and testing on the last day? That's like trying to bake a cake while it's already in the oven. Doesn't work very well, does it?
upvoted 0 times
...
Katie
2 years ago
But maybe they do it because they want to show the full Stories to the Product Owner during the Iteration review.
upvoted 0 times
...
Gayla
2 years ago
Wait, what? They're consistently meeting their commitments and the Product Owner is happy? Isn't that a good thing? I'm a bit confused here.
upvoted 0 times
Karma
2 years ago
D) Because it is difficult to manage dependencies with other teams
upvoted 0 times
...
Genevieve
2 years ago
C) Because the team consistently meets their commitments, and the Product Owner accepts the Stories
upvoted 0 times
...
Brett
2 years ago
B) Because the team demonstrates the full Stories to the Product Owner during the Iteration review
upvoted 0 times
...
Stevie
2 years ago
A) Because the team is waterfalling the Iteration
upvoted 0 times
...
...
Cyndy
2 years ago
Managing dependencies with other teams? That's a classic problem in Agile. I bet they're struggling to coordinate everything across the board.
upvoted 0 times
...
King
2 years ago
I agree with Yong. It's not agile to wait until the last day to integrate and test.
upvoted 0 times
...
Yong
2 years ago
I think it's an anti-pattern because the team is waterfalling the Iteration.
upvoted 0 times
...
Ilene
2 years ago
Integrating and testing on the last day? Sounds like the team is trying to cram it all in at the last minute. That's definitely an anti-pattern to me!
upvoted 0 times
Huey
2 years ago
D) Because it is difficult to manage dependencies with other teams
upvoted 0 times
...
Mariann
2 years ago
B) Because the team demonstrates the full Stories to the Product Owner during the Iteration review
upvoted 0 times
...
Lorita
2 years ago
A) Because the team is waterfalling the Iteration
upvoted 0 times
...
...

Save Cancel