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:
![](https://static.packt-cdn.com/products/9781788470360/graphics/867b2e97-8312-4ba6-a26b-3faebdf72d13.jpg)
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:
![](https://static.packt-cdn.com/products/9781788470360/graphics/8488e01e-6723-498b-b327-3d8f1f9708ff.jpg)
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:
![](https://static.packt-cdn.com/products/9781788470360/graphics/c5bc1f6d-5a38-4128-897e-aa2bfe22446a.png)
Iterative realize phase of SAP Activate