Setting expectations

When initially defining the project approach to the sponsor, there are some key differences that should be highlighted to the client.

Working software over documentation

An Agile approach favors working software over documentation. What this really means is that we need to avoid documentation for documentation sake. In SAP, we typically create a high number of documents, and not all documents have direct value to the customer. In traditional SAP projects, customers wait a long time before seeing working software. Blueprint phases can be quite long, as the team attempts to gather all details and predict the required design. As you will see, an Agile blueprint phase can be much shorter, as we focus ...

Get Agile SAP: Introducing flexibility, transparency and speed to SAP implementations now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.