SAFe-Agilist Establishing Team and Technical Agility — 20 Questions

Question 1

An Agile Team discovers during a Iteration Review that they cannot complete a critical user story because an external supplier failed to deliver a required API interface. What is the most effective immediate action for the Scrum Master to take?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Work with the Product Owner and developers to create a temporary mock interface so internal integration can proceed.. Facilitating the creation of a realistic stub or mock allows the team to continue development and testing without blocking internal progress entirely. Managing cross-team dependencies proactively is a core Agile team responsibility that protects flow, reduces idle time, and maintains predictability during iteration execution.

Answer

Extend the current iteration boundary to accommodate the late delivery from the external supplier.

Answer

Reassign the blocked team members to unrelated backlog items until the external API becomes available.

Answer

Escalate the vendor delay directly to enterprise executive management to demand contractual penalties.

Question 2

An Agile Team in a SAFe ART has just completed its first Program Increment (PI). During the Inspect and Adapt (I&A) workshop, the team identifies that their automated tests are not providing fast enough feedback, leading to integration issues. Which SAFe practice directly addresses this concern?

Accepted Answer

Test-Driven Development (TDD). Test-Driven Development (TDD) directly addresses the need for fast, reliable automated test feedback. By writing tests before code, TDD ensures that tests are focused, fast, and provide immediate validation of code changes. This practice is a key enabler of Built-in Quality in SAFe and helps teams avoid integration issues by catching defects early and often.

Answer

Continuous Deployment (CD)

Answer

Continuous Integration (CI)

Answer

Behavior-Driven Development (BDD)

Question 3

A SAFe Agile Team is adopting Built-in Quality practices. The team's Scrum Master/Team Coach is facilitating a workshop to identify which practices are essential for establishing technical agility. Which TWO of the following are core SAFe practices for achieving Built-in Quality? (Choose two.)

Accepted Answer

Continuous Integration. The two core SAFe practices for achieving Built-in Quality are Continuous Integration and Test-Driven Development. CI ensures that code changes are integrated and tested frequently, while TDD ensures that tests are written first, driving good design and fast feedback. Together, they form the foundation for technical agility and enable teams to deliver high-quality increments reliably.

Answer

Pair Programming

Answer

Behavior-Driven Development

Answer

Refactoring

Question 4

A Scrum Master observes that the team is consistently failing to complete their Sprint Commitment due to unanticipated technical debt. How should the team address this within the SAFe framework?

Accepted Answer

Allocate a fixed percentage of capacity in each Sprint for refactoring and technical debt resolution.. SAFe emphasizes building quality in by addressing technical debt explicitly. By allocating a percentage of capacity for maintenance and refactoring, teams ensure that the codebase remains sustainable. This is critical because ignoring technical debt leads to a decrease in velocity and predictability over time, ultimately jeopardizing the Agile Release Train's ability to deliver value incrementally and maintain high standards of system quality.

Answer

Extend the Sprint duration to allow more time for completing unfinished stories.

Answer

Ask the Product Owner to prioritize all technical debt as high-priority user stories.

Answer

Stop all new feature development until the technical debt is completely eliminated.

Question 5

A newly formed Agile Team is struggling to define their 'Built-in Quality' standards. What is the most effective way for them to establish these practices?

Accepted Answer

Create a shared Definition of Done (DoD) that includes specific quality criteria and automation requirements.. Built-in quality is foundational to SAFe, ensuring the system is robust and scalable. By defining a common Definition of Done (DoD) that includes automated testing and architectural standards, teams ensure consistency. This matters because quality cannot be inspected into a product at the end; it must be an inherent part of the development process to ensure rapid, sustainable delivery of value.

Answer

Allow each developer to decide their own quality standards based on personal preference.

Answer

Wait for the System Architect to provide a comprehensive list of quality requirements.

Answer

Prioritize speed of delivery over quality to meet the upcoming PI objectives.

Question 6

Which TWO of the following are primary responsibilities of the Scrum Master in a SAFe context? (Select TWO)

Accepted Answer

Removing impediments to the team’s progress.. The Scrum Master acts as a servant-leader, focusing on removing impediments and fostering high-performing team dynamics. In SAFe, they also facilitate flow and coordinate with other teams. These roles are critical because the Scrum Master ensures that the team can execute effectively without distractions, which is essential for maintaining the cadences required for program-level alignment and value delivery.

Answer

Prioritizing the Team Backlog.

Answer

Defining the technical architecture for the team.

Answer

Approving the final product release for the customer.

Question 7

During a Sprint Review, a stakeholder expresses dissatisfaction with a feature. What should the team do next?

Accepted Answer

Document the feedback and collaborate with the Product Owner to prioritize the necessary changes.. Agile relies on rapid feedback loops to ensure alignment with customer needs. When a stakeholder identifies a gap, it is an opportunity for the team to adjust their approach. This process is vital because it ensures the team delivers what the market truly wants, rather than what they initially thought, minimizing waste and maximizing the value delivered at the end of every iteration.

Answer

Explain that the work was done according to the original requirements and move on.

Answer

Immediately stop the Sprint to fix the issue identified by the stakeholder.

Answer

Ignore the feedback, as the stakeholder was not present during the planning session.

Question 8

Refer to the exhibit. The Agile Team is struggling to maintain their CI/CD pipeline due to flaky tests. Based on the configuration policy shown, what is the best approach for the team?

Accepted Answer

Quarantine the flaky tests and fix them immediately as part of the team's capacity.. The exhibit shows a mandatory 85% test threshold. Flaky tests undermine this requirement by creating false positives or negatives, rendering the automated policy ineffective. The team must address this by prioritizing test maintenance and refactoring. This matters because a reliable pipeline is the heartbeat of Agile, enabling continuous delivery and ensuring that every code change is validated against the quality standards defined by the organization.

Answer

Lower the threshold to 70% to ensure the pipeline continues to pass.

Answer

Disable the automated test policy until the end of the current Program Increment.

Answer

Ask the DevOps team to rewrite all tests to meet the threshold requirements.

Question 9

Which THREE practices support the SAFe principle of 'Apply Systems Thinking'? (Select THREE)

Accepted Answer

Managing the flow of work across the entire value stream.. Systems thinking encourages teams to consider the entire value stream rather than optimizing individual components. By focusing on the whole, organizations can reduce delays, improve throughput, and enhance overall quality. This is vital in SAFe because isolated optimizations often create bottlenecks elsewhere, hindering the flow of value to the customer and preventing the organization from achieving true business agility.

Answer

Optimizing individual developer velocity.

Answer

Focusing exclusively on local team metrics.

Question 10

What is the primary purpose of the Iteration Review in SAFe?

Accepted Answer

To inspect the increment and adapt the backlog based on feedback.. The Iteration Review provides a cadence for the team to demonstrate their progress to stakeholders and get feedback. It is a critical event for alignment, ensuring that the team is building the right thing. This event matters because it transforms the team's internal work into transparent progress, allowing for course correction based on real-world feedback rather than assumptions, which is essential for maintaining alignment with business goals.

Answer

To identify process improvements for the next iteration.

Answer

To assign specific tasks to team members for the next iteration.

Answer

To approve the team's velocity for the next Program Increment.

Question 11

A team is struggling with frequent context switching. Which SAFe concept should the Scrum Master coach the team on to resolve this?

Accepted Answer

Applying Work in Process (WIP) limits to the team's Kanban board.. Context switching is a significant source of waste, reducing throughput and increasing error rates. SAFe promotes Work in Process (WIP) limits to manage the flow of work. By restricting the amount of active work, teams focus on finishing current tasks before starting new ones, which is vital for maintaining high performance and ensuring that value is delivered incrementally and predictably.

Answer

Implementing stricter individual performance reviews.

Answer

Increasing the team size to handle more parallel tasks.

Answer

Creating a separate team for each of the ongoing features.

Question 12

An Agile team has a high velocity but is still missing their PI Objectives. What is the most likely cause?

Accepted Answer

The team is prioritizing output over the outcomes defined by the PI Objectives.. Velocity measures output, but PI Objectives measure outcomes. If a team is busy but not meeting their goals, they are likely focused on the wrong work. This happens when the team is not aligned with the Program Board or the business value. It matters because high velocity without goal alignment is essentially 'fast failure,' delivering many features that do not contribute to the overall business strategy.

Answer

The team is not using the correct estimation technique for their stories.

Answer

The team is suffering from technical debt that slows down their delivery.

Answer

The Scrum Master is not facilitating the daily stand-up efficiently.

Question 13

Which THREE items should be included in a team's Definition of Done (DoD)? (Select THREE)

Accepted Answer

Code reviewed by another team member.. The Definition of Done is a vital agreement that defines the quality and completeness of a product increment. It prevents 'done-ish' work from accumulating as hidden technical debt. Including these specific criteria ensures that the team consistently delivers high-quality increments, which is essential for integration on the Agile Release Train and for maintaining the trust of stakeholders throughout the Program Increment.

Answer

Approved by the customer representative.

Answer

Budget approved for the next sprint.

Question 14

What is the primary role of the Product Owner in the team's Iteration Planning?

Accepted Answer

Ensuring the team backlog is prioritized to maximize business value.. The Product Owner is the voice of the customer and is responsible for maximizing the value of the team's work. By clearly defining priorities, they ensure the team works on the most important items. This matters because it provides the team with a clear direction, reducing ambiguity during planning and ensuring that the team's efforts are always aligned with the program's strategic objectives and business value.

Answer

Assigning stories to specific team members based on their skills.

Answer

Deciding the technical approach for each user story.

Answer

Tracking the team's velocity and reporting it to management.

Question 15

Refer to the exhibit. A team wants to deploy a new feature to production, but the automated deployment process is blocked by the policy shown. What is the best way to handle this?

Accepted Answer

Request a meeting with the Security Lead and Architecture Board to integrate approval into the pipeline.. The exhibit shows that the deployment policy has hard constraints requiring manual sign-offs. In SAFe, teams must operate within organizational governance while striving for continuous delivery. The team should work with the Architecture Board and Security Lead to automate these approvals or incorporate them into the workflow. This is important because it balances the need for security and architectural governance with the requirement for rapid, automated release cycles.

Answer

Bypass the policy, as it is outdated and hinders speed.

Answer

Manually email the approvers every time the team is ready to deploy.

Answer

Ask the Product Owner to approve the deployments instead.

Question 16

What is the primary benefit of the Daily Stand-up for the Agile Team?

Accepted Answer

To synchronize the team’s activities and identify impediments.. The Daily Stand-up is a short, daily check-in that facilitates synchronization and progress tracking. It allows team members to align on their daily tasks and identify impediments early. This event matters because it keeps the team focused on the Sprint Goal and allows for rapid, daily adjustments to the plan, which is essential for maintaining flow and achieving the commitments made during Iteration Planning.

Answer

To solve complex architectural problems.

Answer

To update the team's project management tool.

Answer

To report daily status to the Product Owner.

Question 17

An Agile Release Train is struggling with frequent integration bottlenecks because team members work in isolation on their own branches for weeks. As a SAFe Agilist, which approach should you recommend to establish technical agility and resolve this issue?

Accepted Answer

Adopt extreme programming practices such as Test-Driven Development, pairing, and Continuous Integration to merge and validate code daily.. Continuous Integration is fundamental to technical agility in SAFe. By merging code changes daily or multiple times a day into a shared trunk, teams discover integration conflicts early and maintain a continually working system. This practice directly addresses the root cause of long integration delays by enforcing automated build and test pipelines.

Answer

Extend the Iteration length to provide teams more time to stabilize their complex feature branches before attempting integration.

Answer

Implement a separate release branch freeze period during the final week of every iteration to manually verify all changes.

Answer

Assign a dedicated integration team responsible for merging all developer branches at the end of each Program Increment.

Question 18

A Scrum Master observes that a team is struggling to meet their Sprint Goals because they spend significant time resolving technical debt during the sprint. How should the team apply the concept of Built-in Quality to address this?

Accepted Answer

Adopt practices such as Test-Driven Development and Pair Programming to prevent defects.. Built-in Quality requires that quality is not an afterthought but integrated into the development process through practices like Test-Driven Development and pair programming. By incorporating these technical practices, the team reduces rework and prevents defects from accumulating. Addressing technical debt incrementally within the sprint ensures that the team maintains a sustainable velocity, allowing them to deliver high-quality increments that reliably meet the Definition of Done in every iteration.

Answer

Allocate a separate sprint strictly for technical debt resolution every quarter.

Answer

Increase the velocity estimate to account for the time needed for bug fixes.

Answer

Escalate the issue to the Release Train Engineer to request additional team members.

Question 19

An Agile Team is struggling to complete their planned Stories within the iteration, often carrying over 30% of their work to the next Iteration. During backlog refinement, the Product Owner insists on adding more scope to fill the velocity cap. Which action should the team and Scrum Master take to establish sustainable flow?

Accepted Answer

Negotiate a realistic scope with the Product Owner based on historical throughput and establish a Work in Process limit.. Re-establishing predictable flow requires matching work-in-process to actual capacity rather than artificially inflating commitments. By negotiating realistic scope based on historical throughput, the team reduces context switching, finishes stories completely, and builds trust with the Product Owner. This practice supports sustainable pace and drives continuous delivery value in SAFe.

Answer

Increase the planned velocity by 20% to account for carryover work and maintain pressure on the delivery schedule.

Answer

Work extra hours during the final days of the iteration to ensure all committed backlog items meet the Definition of Done.

Answer

Delegate story splitting entirely to the Product Owner outside of team planning sessions to maximize developer coding time.

Question 20

Which TWO practices are essential for an Agile Team practicing Built-in Quality in a SAFe environment? (Choose two.)

Accepted Answer

Implementing Test-Driven Development to design and verify code behavior before implementation.. Built-in Quality requires technical practices that ensure quality is embedded into every increment rather than inspected at the end. Test-Driven Development provides immediate feedback and drives clean architecture, while automated regression suites guarantee that new functionality does not break existing features across the system.

Answer

Performing manual integration testing in a dedicated hardening iteration prior to release.

Answer

Submitting all completed code to an independent quality assurance department for final verification.

Answer

Deferring refactoring tasks to dedicated technical debt sprints scheduled every six months.