Skip to Content
Author's profile photo Former Member

Who makes the best AGILE SAP scrum masters

If you are considering implementing some SAP functionality via the AGILE methodology one of the first decisions you need to make is the appointment of your scrum master (project master in old money).


There are two main options here – you can bring in a scrum master who does not know your industry and will probably not know SAP. The other option is to cross train an existing project manager in your organisation in the AGILE methodology. There are obviously pro’s and con’s with both options and ideally within time you would have an experienced scrum master who knows, the methodology of AGILE, your organisation, and your software.


So let’s start with a scrum master with no experience of SAP and your organisation. For them to play a successful part in your implementation they need to be flexible to learn quickly how your organisation works and the technology you are implementing on. At the same time, they need to provide a strong and clear message to your entire business of the benefits of the AGILE methodology plus they need to gain support of the methodology by all key stakeholders in the company (not just the project). OK so this is quite a task, and let’s not generalise here, people and employees are individuals. Some scrum masters can adapt quicker and more efficiently than others. There are a number of risks here, the scrum master not being flexible or has not got the high level approval of the approach within the business. It is sometimes good to have a fresh pair of eyes, and if the project is sold in the right manner to the implementation team and business community then their support of the methodology will in turn help the project and the change aspect of the methodology.


The other option you have is cross training an existing project manager. If this is the approach that you plan to take my first suggestion is after the project manager has been cross trained, they playback the methodology to the key business users and the whole implementation team. A working party need to review how this could work to either accept the new methodology as a whole or try to amend the approach so it fits the current organisation. The benefits of cross training an existing project manager is that they will know the project team and the key individuals in the Company. The relationships that have been built over time should help the project manager sell the new methodology to the stakeholders. The key to the sale of the methodology to the business, is the buy-in (understanding) of the benefits of the new methodology. If the project manager can get their support, the sale to the rest of the company and implementation team would be easier. The key downside to this, is that the project manager does not have any real experience – they only have text book experience. Would you have your lead CRM functional consultant role be delivered by a user who had not done it before?


The role of the scrum master is critical to the success of the implementation. The whole project team need to be trained in the methodology. Following the process to the letter of the law may be hard first time out. The expectation levels of the project should be set accordingly, it will be hairy; people may be waiting around for work to do, or issues to be resolved, but as with everything the more you do it, the better you become.


So if you are considering switching from a waterfall methodology to an AGILE methodology, the choice of project is also critical. Doing this on a brand new implementation of new functionality would be a substantial risk, however if there was a small stand alone piece of functionality that needed implemented that would be a more suitable project to test drive your new methodology.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi, 2016 here. Thank you for this blogpost!

      Some scrum masters can adapt quicker and more efficiently than others. There are a number of risks here, the scrum master not being flexible or has not got the high level approval of the approach within the business.


      As a Scrum Master I see it as a core skill (and I aim to improve it everyday) to be able to change.

      Thus I am following the approach of Transparency, Inspection and Adaption by;
      1) bringing up any pending decisions, impediments or pain points,
      2) to than gather any implications of the Scrum Team members upon this given transparency,
      3) and to adapt a specific (corresponding) part of the information-flow in the project.

      Best Regards,