Skip to Content

When I first started to think on how to apply agile to the SAP world, I started here at SDN (of course 😉 For the first time I got disappointed by SDN … There wasn’t much to find on agile nor scrum on SDN. I found 2 blogs, both a bit theoretical.

So I read a bit about the theory, read a bit that SAP was implementing scrum, but I couldn’t find HOW to implement scrum in an SAP project. And that was exactly what I was searching for. We were about to start doing scrum in our SOA SAP project (#cross2010 on Twitter). I decided to share our experiences, on SDN of course 😉

1,5 year later, we successfully delivered 3 projects and we just started the 4th one. Want to know how we did this? How we implemented scrum as project approach in an SOA SAP project? Please join me in session PMC236 at SAP TechEd Berlin on Wednesday October 13th, 12:15 p.m.–1:15 p.m., L6, Hall 4.

Daily scrum meeting, stand up (except for one 😉

Joined design, team effort.

Don’t expect a silver bullet for agile, there is none. I will share our experiences and give you some tips on how to start applying agile to your own SAP project.

More agile at this year’s SAP TechEd:
PMC105, SAP’s Agile Methodology for Implementing your BPM Project by Ann Rosenberg

And for you hungry readers there is a lot more to find on agile and SAP on SDN nowadays.

Recommended:

And on Twitter. First only some rare tweets, now growing and growing with a lot of new job openings.

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. Manas Dua
    “Don’t expect a silver bullet for agile, there is none” – says it all.

    We can’t be rigid in following scrum\ agile methodology and I guess that’s the key.
    Each team starts with prescribed set of guidelines or standard practice but at end of few sprints each team has it’s own way of doing things 🙂

    ex: Some may have daily scrum meetings @ start of day while some opt for end of day scrum meeting; suited to each team’s convenience

    (0) 
    1. Twan van den Broek Post author
      Totally agree, we’re no “Scrumdamentalists”, be pragmatic in your approach. Scrum is not a goal, it’s a road to achieve your goals.

      Our daily scrum is from 10:00 – 10:15. Everyone is in and it gives us a jumpstart of the day.

      (0) 
    1. Twan van den Broek Post author
      Hi Mark
      thanks for your reply. about your experience that project is going too quick for business. We recognize that. Finally IT is not hampering business progress but supporting. And that’s the way it should be. But I guess business still has got to get used to that 😉

      Hope to see/speak to you tomorrow at PMC236.

      Twan

      (0) 
  2. Otto Gold
    Hello,
    just wanted to tell you this looks very nice and promising and I will sit in the “class” to hear your story.
    Cheers Otto
    (0) 
  3. Rammohan Shenoy
    Twan,

    I feel actually the ASAP methodlogy for delivering SAP core implementation projects has many similarities to the SCRUM.
    In ASAP you have a prototype demo to the business which gives them a feel of the SAP vanilla transactions right from Quote to Cash or Requistion to Pay.
    This gives the business idea about what to expect from the SAP implementation. Gaps in the standard process are then taken up & met through custom development that results in business value..

    Just my humble thoughts..

    (0) 
    1. Twan van den Broek Post author
      Great, get as many feedback moments from business and end-users as you can. Involve them during the implementation process.
      Prevent doing an implementation of 1 year or more and then show the results. The reaction might be “OK, nice what you have built, but not exactly what I expected”.

      Twan

      (0) 
  4. Zal Parchem
    Hello Twan – have been following the discussion of “scrum” for some time now in SAP and have the following question.  How does this differ from what most persons responsible for legacy system enhancement/maintenance have been doing for decades?  I always had a small window (30 days), constantly changing priorities and personnel assignments, daily team meetings with total team focus, peer review, etc.  And that applied whether it was an enhancement, new interface, maintentance tasks – well, in short, it was for anything!  LOL – I even had a “war room” with no chairs to avoid the ho-hum meeting attitude and to get down to the task at hand (no sitting is probably the best idea anyone every came up with – another one is to do the team meetings before lunch).  So maybe a word or two on that would be helpful…thanks Zal
    (0) 
    1. Twan van den Broek Post author
      Lots of questions on agile or scrum are about your statements. It isn’t new, no innovative ideas, open doors, …

      BUT combination of all used techniques in scrum and to use these pragmatically in an SAP environment – that is new.
      With SOA and BPM projects growing in numbers, the traditional waterfall approach with an implementation of 1,5 yr or more is not suitable any more.

      Twan

      (0) 

Leave a Reply