SAFe, LeSS & Nexus Scaling Flashcards
7 cards from real CST practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 SAFe, LeSS & Nexus Scaling flashcards as text
Which SAFe event directly replaces the individual team Sprint Review at the ART level?
Answer: System Demo
The System Demo is an ART-level event held each Iteration where all teams demonstrate their integrated work to stakeholders.
In LeSS, how many Product Owners are there for all teams?
Answer: One overall Product Owner for the whole product
LeSS maintains a single Product Owner who owns the one Product Backlog shared across all teams, preserving the Scrum principle of one PO per product.
What is a key differentiator of the Nexus framework compared to SAFe and LeSS?
Answer: Nexus is designed specifically for 3–9 Scrum teams and adds minimal roles/events
Nexus is a lightweight scaling framework for 3–9 teams that adds only one role, a few events, and one artifact on top of standard Scrum.
In SAFe, what is the role of the Release Train Engineer (RTE)?
Answer: Serving as the chief ScrumMaster who coaches ART practices and facilitates ART-level events
The RTE is the ART's servant leader and coach, facilitating PI Planning, ART Syncs, and System Demos while removing impediments at the ART level.
Which LeSS principle emphasizes that teams should be organized around customer-facing features rather than technical components?
Answer: Feature Teams over Component Teams
LeSS strongly favors Feature Teams—cross-functional teams capable of delivering end-to-end customer features—over siloed Component Teams.
In Nexus, the Nexus Daily Scrum is attended by whom?
Answer: Representatives from each Scrum team (often ScrumMasters or delegates)
The Nexus Daily Scrum involves representatives from each team who inspect cross-team integration progress and surface impediments that affect multiple teams.
In SAFe's Continuous Delivery Pipeline, which stage focuses on verifying that features meet customer needs through testing in production-like environments?
Answer: Continuous Deployment
Continuous Deployment deploys to staging or production-like environments to verify that built features meet quality and performance standards before release.