Scaled Agile Exam SAFe-SASM Topic 1 Question 1 Discussion

Actual exam question for Scaled Agile's SAFe-SASM exam

Question #: 1
Topic #: 1

[All SAFe-SASM Questions]

An Agile Team decides they want to use pair programming in future Iterations. Where should this be captured?

AIn the Inspect and Adapt meeting notes

BIn the team retrospective notes

CIn the Program Backlog

DIn the team's improvement backlog

Show Suggested Answer

Suggested Answer: B

The decision to implement pair programming in future iterations is a team-level improvement action that stems from reflecting on their current processes and identifying areas for enhancement. This is best captured during the team's retrospective:

Retrospective Purpose: The retrospective is a regular meeting where the team reflects on what went well, what didn't, and what could be improved.

Action Items: Decisions and action items, such as adopting pair programming, are documented in the retrospective notes to ensure they are followed up in future iterations.

Continuous Improvement: Capturing this in the retrospective notes ensures the team is committed to continuous improvement and has a clear record of their decisions and plans for process enhancements.

SAFe Scrum Master Reference:

SAFe Advanced Scrum Master Training Material, Chapter on Team Retrospectives.

by My at Aug 08, 2024, 03:48 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Becky

3 months ago

I think capturing it in both the team retrospective notes and the team's improvement backlog would be the best approach.

upvoted 0 times

...

Lottie

3 months ago

I believe it should also be included in the team's improvement backlog to ensure it gets implemented.

upvoted 0 times

...

Martha

3 months ago

I agree with Casie, it's important to document it there for future reference.

upvoted 0 times

...

Casie

3 months ago

I think we should capture it in the team retrospective notes.

upvoted 0 times

...

Justine

3 months ago

In the Program Backlog? Really? That's like putting my grocery list in the company's strategic plan. Not happening!

upvoted 0 times

Myong

2 months ago

D) In the team's improvement backlog

upvoted 0 times

...

Kanisha

2 months ago

A) In the team retrospective notes

upvoted 0 times

...

Fabiola

3 months ago

I think capturing it in both the team retrospective notes and the team's improvement backlog would be the best approach.

upvoted 0 times

...

Yun

4 months ago

Pair programming, huh? Sounds like a great way to make sure everyone stays awake during the standup meetings!

upvoted 0 times

Chanel

2 months ago

C) In the Program Backlog

upvoted 0 times

...

Kimberely

3 months ago

Pair programming can definitely help keep things interesting during meetings!

upvoted 0 times

...

Stevie

3 months ago

B) In the team's improvement backlog

upvoted 0 times

...

Ivan

3 months ago

A) In the team retrospective notes

upvoted 0 times

...

Chandra

4 months ago

I believe it should also be included in the team's improvement backlog to ensure it gets implemented.

upvoted 0 times

...

Zena

4 months ago

Option D all the way! Gotta keep that improvement backlog updated, otherwise how will we remember what we promised to try next iteration?

upvoted 0 times

Shawna

3 months ago

Yes, it's important to have a clear record of what we want to try in future iterations.

upvoted 0 times

...

Helga

4 months ago

I agree, keeping track of our improvement backlog is crucial for our progress.

upvoted 0 times

...

Viva

4 months ago

I agree with Henriette, it's important to document it there for future reference.

upvoted 0 times

...

Vallie

4 months ago

I'm going with B. The team retrospective is the perfect place to discuss and document new practices like pair programming.

upvoted 0 times

Danica

3 months ago

Pair programming can really improve collaboration and code quality, so it's great that the team is considering it.

upvoted 0 times

...

Kristian

3 months ago

It's important to document it there so the team can reflect on how it's working for them in future iterations.

upvoted 0 times

...

Janey

3 months ago

I agree, the team retrospective is the best place to capture decisions like using pair programming.

upvoted 0 times

...

Henriette

4 months ago

I think we should capture it in the team retrospective notes.

upvoted 0 times

...

Ozell

4 months ago

Definitely the team's improvement backlog. That's where we should capture any process improvements like pair programming.

upvoted 0 times

Dalene

3 months ago

I think it's important to document these decisions so we can track our progress over time.

upvoted 0 times

...

Jacob

4 months ago

We can review the team's improvement backlog regularly to see how pair programming is benefiting us.

upvoted 0 times

...

Brice

4 months ago

It makes sense to keep track of process improvements like pair programming in one place.

upvoted 0 times

...

Suzi

4 months ago

Agreed, the team's improvement backlog is the best place to capture that.

upvoted 0 times

...