Sprint cycles and their importance
Sprint is a 2-4 week of timebox of work during which—analysis, design, code, and the test is performed. Each Sprint has a little bit of all. A typical Sprint cycle looks as follows:

Sprint cycle
The Sprint execution inside the Sprint cycle will have a structure as shown in the following image, that is, it will have a design, build test, and document steps for all the delta requirements. So, at a given moment, for a user story X, Y, Z, and R, we will see this:

The following is the overview of the iterative realize phase of SAP Activate. SAP Activate (realize) uses the agile philosophy of Sprints and iterative build:

Iterative realize phase of SAP Activate