SAFe-Agilist Establishing Team and Technical Agility Practice Question
An Agile Team is preparing for its first Program Increment and wants to build the Team and Technical Agility competency. The Scrum Master is facilitating a working session on which attributes the team must develop. Which two attributes are core to this competency? (Choose two.)
⚠ Common exam trap
Watch out — candidates often confuse general program governance artifacts, such as roadmaps and individual metrics, with the specific team-level attributes that define the Team and Technical Agility competency.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The team organizes around the flow of value and applies cross-functional skills so it can deliver end-to-end without handoffs.
Team and Technical Agility rests on cross-functional teams organized around value flow and on a shared Definition of Done that embeds Built-in Quality practices. These two attributes let teams deliver working, tested Increments without handoffs and keep quality designed into the product. Long roadmaps, individual velocity metrics, and externalized quality assurance all work against the competency's intent.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The team tracks individual velocity and uses it as the primary input for performance reviews and compensation decisions.
Why it's wrong here
Using individual velocity for performance reviews destroys the psychological safety and collaboration that technical agility requires. Velocity is a team-level planning metric with significant variance, not a measure of individual productivity. SAFe explicitly cautions against using velocity for comparison or evaluation, so this attribute would actively work against building the competency rather than support it.
- ✓
The team organizes around the flow of value and applies cross-functional skills so it can deliver end-to-end without handoffs.
Why this is correct
Organizing around value flow with cross-functional skills is a core attribute, because it lets the team deliver a working, tested Increment without depending on external handoffs. This is what makes teams truly agile rather than component-focused. It also supports fast feedback and collective ownership, both of which are central to the Team and Technical Agility competency in SAFe.
- ✓
The team establishes a shared Definition of Done that includes Built-in Quality practices and applies it to every Increment.
Why this is correct
A shared Definition of Done that embeds Built-in Quality is a defining attribute of Team and Technical Agility. It gives the team a common standard for what finished means and ensures quality is designed in rather than inspected later. Applying it consistently to every Increment is what turns the competency from an aspiration into a repeatable behavior across the Agile Release Train.
- ✗
The team delegates all testing and quality decisions to a separate quality assurance department to preserve developer focus.
Why it's wrong here
Outsourcing testing and quality decisions to a separate department contradicts Built-in Quality and collective ownership. When developers do not own quality, defects flow downstream and feedback loops lengthen, which is the opposite of what Team and Technical Agility requires. Cross-functional teams in SAFe own testing, automation, and quality outcomes as part of delivering each Increment.
- ✗
The team maintains a detailed three-year technology roadmap that the System Architect approves before each Iteration.
Why it's wrong here
Long-range technology roadmaps approved by the System Architect are not an attribute of Team and Technical Agility. SAFe plans at the Program Increment cadence precisely because detailed multi-year roadmaps cannot absorb change. Requiring architect approval before each Iteration would also undermine the team's self-management and slow its ability to respond to feedback.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.