In an Agile approach, particularly within the SAP Activate methodology, planning is iterative and adaptive. At the beginning of the Realize phase, the project team employs a "rolling wave" planning technique. This means they focus on preparing and refining user stories to a "Ready" state (fully defined, estimated, and actionable) for only the initial sprints, typically the first two or three. This just-in-time approach ensures the team works on well-understood requirements while maintaining the flexibility to adapt the backlog for subsequent sprints based on feedback and evolving priorities. The remainder of the product backlog exists at a higher, less-detailed level (as Epics or larger user stories) to be refined later.

A. Scope and duration of testing are finalized.

This is incorrect. In Agile, testing is a continuous activity within each sprint. The detailed scope and effort for testing evolve as user stories are developed, not finalized upfront.

B. Durations of all sprints for the full release are defined based on planned complexity.

This is incorrect. Sprint durations (cadence) are typically fixed and consistent (e.g., two weeks) to establish a rhythm. The amount of work (scope) within a sprint varies, not its duration.

D. Project scope and planning are completed and final.

This is incorrect. This describes a Waterfall approach. A core principle of Agile is that scope is flexible and planning is continuous throughout the project lifecycle, not finalized before execution begins.

---

1. SAP Activate Roadmap Viewer: In the "SAP Activate Methodology for RISE with SAP S/4HANA Cloud

private edition" roadmap

navigate to the Realize phase. The deliverable "D020 - Product Backlog" is described as a living artifact that is continuously prioritized and refined. The associated task "Refine the Product Backlog" is an ongoing activity

implying that only the top items are fully detailed at any given time. This supports the concept of having only the next few sprints ready.

2. SAP Activate - Agile Project Delivery (Whitepaper): On page 11

under the section "Realize Phase

" it states

"The team starts the Realize phase with a series of sprints... The team details out the requirements in the Product Backlog just-in-time for the development in the upcoming sprint." This directly confirms that user stories are prepared for immediate sprints

not the entire release.

3. SAP Press Publication - "SAP Activate: Project Management for SAP S/4HANA" (ISBN: 978-1-4932-1937-8): In Chapter 6

"The Realize Phase

" the concept of sprint-based execution is detailed. It explains that sprint planning meetings occur at the start of each sprint to select and commit to a set of "Ready" user stories from the top of the product backlog

reinforcing that not all stories are in a "Ready" state at the phase's outset.