Skip to Content

Being Agile with SAP Projects!

Sprints, standup meetings, retrospectives and kanban boards are not words that you expect to be part of a SAP implementation project. But, guess what? Here they are! Just below the latitude 33. We are fully using the ASAP Hybrid Agile model to come across with a successful SAP project. At least we expect that.

Although the whole endeavor it quite hard, and perhaps risky, we decided to run agile (Scrum) to involve (and evolve) our key users more on the project, to prioritize our developments (gaps) and to promote a high level of interaction between all team members. In doing so, we will control better our time and costs, and hopefully deliver what an IT project should always accomplish: business results.

So far we have run sprints for our business blueprints, including several modules, and the interfaces. By the way, lots of them. I will share more experiences here as the project goes on. Even because our experiences will not finish there. We have a quite extensive technical scope, from ECC to BPM, from PI to Afaria.

Hasta pronto!

You must be Logged on to comment or reply to a post.
  • Hi Roberto,

    I am (hopefully!) going live with a project later this week (BPM & PI) that has been run using a hybrid waterfall/Agile (Scrum) type methodology.  It has certainly had it’s ups and downs but I feel the ultimate aim, improving the quality of the delivered solution, has certainly been met.

    The biggest challenge I found was ensuring the correct level of engagement from all stakeholders at the right time.  This has always been a challenge on projects of course but its essentiall to get this right from day 1.

    Hope your project goes well.


    • Hi Gareth,

      Good to hear your that you are also engaged to agile. Please share more about your experiences with BPM and Agile when the workload gives you some opportunity.

      Hope you have a successful go live.


      • Hi Roberto,

        A resource that I found more recently but think would have been really handy a few years ago when we starting doing projects using Scrum, is this Kindle book –  I’m not sure if there is a printed version as well unfortunately.

        It obviously doesn’t have the depth or detail that is needed but may be a useful reference for people who aren’t necessarily primary stakeholders in your project, or who don’t have the relevant skills/experience to dive straight in to project methodologies.  It might also just be a useful reference to have around generally.