Which statements describe the ART planning principles?

• A. Frequent, periodic planning; dates and quality fixed; scope floats; decentralized scope and schedule planning; continuous integration of all teams on ART; system demo every two weeks
• B. Infrequent planning; fixed scope; centralized scheduling; no integration; system demo yearly
• C. Planning only at program level; teams operate independently; no system demos; quarterly releases
• D. Planning is unnecessary; teams self-manage without integration; system demo never

Answer: (A)

In SAFe, the ART planning approach centers on coordinating multiple teams on a shared cadence with a predictable schedule, while preserving flexibility in what gets built. Planning happens frequently on a regular rhythm, and the date of the Program Increment is fixed so the teams align to a common milestone and quality is non-negotiable. Because the date is fixed, the exact scope can be adjusted or renegotiated to fit that schedule and quality bar. Planning is decentralized to the teams and the train, so teams collaborate and plan together rather than waiting for a single central authority. Continuous integration keeps the work from different teams merging smoothly, producing a genuinely integrated increment. The system demo occurs every iteration, typically every two weeks, to provide ongoing visibility into progress and enable course corrections with stakeholders.

This combination—frequent, cadence-driven planning with fixed dates and quality, flexible scope, decentralized planning, continuous integration, and regular system demos—best reflects how ART planning is conducted. The other options describe planning that is infrequent or centralized, isolates teams, omits integration, or eliminates demonstrations, all of which would break the coordinated, empirical flow that SAFe relies on for ARTs.