SA Team and Technical Agility 1 — Questions and Answers
Question 1: Which two dimensions make up the SAFe core competency of Team and Technical Agility?
- Agile Teams and Technical Practices (Correct answer)
- Scrum and Kanban
- XP and Lean Thinking
- DevOps and Continuous Delivery
Correct answer: Agile Teams and Technical Practices
Team and Technical Agility consists of Agile Teams (the people and culture) and Technical Practices (the engineering disciplines that ensure quality).
Question 2: What is the recommended size for an Agile team in SAFe?
- 2–4 members
- 5–11 members (Correct answer)
- 12–20 members
- Any size as long as productivity is maintained
Correct answer: 5–11 members
SAFe recommends Agile teams of 5–11 members, small enough to communicate easily yet large enough to deliver meaningful increments each iteration.
Question 3: What is the primary purpose of Built-in Quality in SAFe?
- To conduct formal audits at release milestones
- To ensure every increment meets quality standards so defects are not passed downstream (Correct answer)
- To assign quality responsibility to a dedicated QA team
- To perform user acceptance testing at PI boundaries
Correct answer: To ensure every increment meets quality standards so defects are not passed downstream
Built-in Quality ensures that every increment of work meets defined quality standards continuously, preventing defects from accumulating and being passed to later stages.
Question 4: Which SAFe practice requires teams to define what 'done' means for a Story before beginning work?
- Iteration Review
- Definition of Done (DoD) (Correct answer)
- Program Increment Objectives
- Backlog Refinement
Correct answer: Definition of Done (DoD)
The Definition of Done (DoD) specifies the acceptance criteria every Story must meet before it is considered complete, ensuring consistent quality across the team.
Question 5: In SAFe, what is the purpose of the Iteration Retrospective?
- To demonstrate completed features to stakeholders
- To plan the next iteration's Stories
- To inspect team processes and identify improvements (Correct answer)
- To update the Program Board with new risks
Correct answer: To inspect team processes and identify improvements
The Iteration Retrospective is a dedicated ceremony for the team to reflect on its process and practices, identify what went well, and determine improvement actions.
Question 6: What is a 'Spike' in SAFe Agile team terminology?
- A sudden increase in team velocity
- A time-boxed research or exploration Story used to gain knowledge (Correct answer)
- An unplanned defect that must be fixed immediately
- A dependency between two Agile teams on the ART
Correct answer: A time-boxed research or exploration Story used to gain knowledge
A Spike is a time-boxed Story specifically intended to research or explore a technical question or design approach, producing knowledge rather than a deliverable feature.
Question 7: Which XP technical practice involves two developers working together at one workstation, one writing code while the other reviews in real time?
- Continuous Integration
- Test-Driven Development
- Pair Programming (Correct answer)
- Collective Ownership
Correct answer: Pair Programming
Pair Programming has two developers collaborating at a single workstation, improving code quality through real-time review and knowledge sharing.
SA Team and Technical Agility 1
Which two dimensions make up the SAFe core competency of Team and Technical Agility?