SA Team and Technical Agility

Question 1

Which two dimensions make up the SAFe core competency of Team and Technical Agility?

Accepted Answer

Agile Teams and Technical Practices

Answer

Scrum and Kanban

Answer

XP and Lean Thinking

Answer

DevOps and Continuous Delivery

Question 2

What is the recommended size for an Agile team in SAFe?

Accepted Answer

5–11 members

Answer

2–4 members

Answer

12–20 members

Answer

Any size as long as productivity is maintained

Question 3

What is the primary purpose of Built-in Quality in SAFe?

Accepted Answer

To ensure every increment meets quality standards so defects are not passed downstream

Answer

To conduct formal audits at release milestones

Answer

To assign quality responsibility to a dedicated QA team

Answer

To perform user acceptance testing at PI boundaries

Question 4

Which SAFe practice requires teams to define what 'done' means for a Story before beginning work?

Accepted Answer

Definition of Done (DoD)

Answer

Iteration Review

Answer

Program Increment Objectives

Answer

Backlog Refinement

Question 5

In SAFe, what is the purpose of the Iteration Retrospective?

Accepted Answer

To inspect team processes and identify improvements

Answer

To demonstrate completed features to stakeholders

Answer

To plan the next iteration's Stories

Answer

To update the Program Board with new risks

Question 6

What is a 'Spike' in SAFe Agile team terminology?

Accepted Answer

A time-boxed research or exploration Story used to gain knowledge

Answer

A sudden increase in team velocity

Answer

An unplanned defect that must be fixed immediately

Answer

A dependency between two Agile teams on the ART

Question 7

Which XP technical practice involves two developers working together at one workstation, one writing code while the other reviews in real time?

Accepted Answer

Pair Programming

Answer

Continuous Integration

Answer

Test-Driven Development

Answer

Collective Ownership