← All CST Flashcard Decks

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
  1. In SAFe, what is the primary purpose of the Agile Release Train (ART)?

    Answer: To align multiple Agile teams to a shared mission and deliver value together on a fixed cadence

    The ART is a long-lived team-of-teams that aligns up to 125 people around a shared mission, delivering value on a regular cadence through Program Increments.

  2. In LeSS, which role is explicitly ELIMINATED compared to single-team Scrum?

    Answer: Project Manager

    LeSS deliberately removes the Project Manager role, distributing project management responsibilities across the Product Owner, teams, and ScrumMasters.

  3. What is the Nexus Integration Team's primary responsibility?

    Answer: Coaching teams and coordinating integration work across the Nexus

    The Nexus Integration Team coaches teams on integration practices and coordinates the work needed to reduce dependencies and produce an Integrated Increment.

  4. In SAFe's Program Increment (PI) Planning, who is responsible for presenting the Vision and top Features to all teams?

    Answer: Product Management

    Product Management presents the Vision, top Features, and priorities at the start of PI Planning to align all ART teams on what to build.

  5. In LeSS Huge, what structure is used to manage large product domains with thousands of people?

    Answer: Requirement Areas with Area Product Owners

    LeSS Huge introduces Requirement Areas—temporary groupings of related requirements—each served by an Area Product Owner to manage scale beyond 8 teams.

  6. What artifact is unique to Nexus that does NOT exist in single-team Scrum?

    Answer: Nexus Sprint Backlog

    The Nexus Sprint Backlog is unique to Nexus and visualizes all the work selected by the teams for the Sprint plus their cross-team dependencies.

  7. In SAFe, what is the cadence of a Program Increment (PI)?

    Answer: 8–12 weeks with multiple Sprints

    A PI typically spans 8–12 weeks and contains 4–6 Iteration (Sprint) cycles, providing a longer planning horizon for ART-level delivery.