Iterative Kanban and Scrum Modes For SAP Agile Development Factory

Agile with lean delivery methodology is the most adapted delivery process in modern software deployment, including that of SAP. The two popular lean methods for SAP projects are called 'Iterative Kanban' and 'Scrum'. Both use time-bound iterative cycles which focus on early demonstration, improving the end product through continuous feedback. Such delivery gives higher business value and customer satisfaction. Business is engaged in all phases appropriately and participates throughout the lifecycle of the product. The delivery risk decreases with time, it is more predictable and stable. Let us understand the difference between the two and appreciate which type of work packages can be routed to them.  

Iterative Kanban Mode Of Delivery: This methodology, leverages Kanban to deliver the work package in waves, that consist of multiple sprint cycles that make up each wave. Each sprint is 3 to 4 weeks long and each wave could have 2 to 3 sprints making the wave 6 to 12 weeks long. After every wave, the product is demonstrated and feedback is incorporated as a retrospective for further prioritization of features in a subsequent wave. When the new requirement is prioritized, the current work-in-progress backlog is put to hold to preserve the schedule. Every wave generates a release backlog, which then is integration-tested, user-accepted, and approved for deployment as a release. This release deploys multiple story points together. 

Scrum Mode Of Delivery: This project methodology includes scrum backlog management, scrum execution, iteration, demonstration, and retrospect. Each scrum typically lasts 3 to 4 weeks. When new changes are brought in, it adjusts the scope backlog to preserve the schedule. Changes can be deployed in a quick turnaround.

Iterative Kanban Way	Scrum Way
Major Projects With Milestones       Where work is based on a major milestone generally with one big bang go-live. Examples: Greenfield Implementation, Package Upgrades, S/4 Conversions, Mergers, and Acquisitions, etc…	Urgent Changes       Ideal for delivering urgent or emergency changes that comes in from the application support organization. This is not just a temporary workaround, but getting the permanent change moved in quickly.
Periodic Maintenance Activities       Periodic maintenance of applications, Service pack upgrades, Scheduled Planned activities, etc…	Service Request       All Service Requests that are part of the run organizations, for example: Adding a new element to a Fiori app, configuring a new plant, configuring a new routing logic, etc...
Application Development       Large development work which has a linear workflow. These could be allocating support to other external projects or doing staff augmentation. Ideal for projects where we block dedicated capacity.	Agile Application Development       These work packages are generally built for early value realization in an MVP way. In this type of work, it is okay to release various features over time as soon as they are ready. The work generally is executed at a service level and not capacity.
Business Process Change       These are moderate-size projects where the customer has to adapt to a new business function or adapt changes for regulatory compliance. Generally, this type of work has a company-wide impact and must be handled with organization change management track, training, etc… Example: Adapting a new GST Add-on, Onboarding of Treasury module.	Release Window-Based Activities       Work here is built in sprints and is tested and kept ready in a release backlog. This backlog is reviewed and prioritized to be deployed in release windows. This is the most popular way to develop SAP in an Agile factory model.
Work Package Size       All sizes of work can be delivered	Work Package Size       Work order that has less than 400 hours of effort and can be deployed within 4 weeks goes to Scrum by default. All small and large work order that follows Agile Scrum is delivered through this engine.