.svg){kind=small}
.svg)
.avif)
.avif)
.avif)
No items found.
Language
.svg)
.svg)
SAP Activate? Oh yeah, that’s just SAP doing Agile. Isn’t it?
...At least, that’s what everyone says?!
In reality, it’s a bit more complex than that. Let’s take a look at Activate in more detail and break it down into bite-sized chunks.
Activate is SAP’s S/4HANA implementation toolkit. It builds on and supersedes SAP’s two previous implementation approaches: ASAP (On-Premise) and Launch (Cloud). It employs both Waterfall and Agile elements and is far more prescriptive than either of its ancestors.
Unlike the older approaches, Activate is applicable to On-Premise, Cloud and Hybrid implementations. Despite being designed for S/4HANA, it can actually be used for all SAP products.
This article looks at the main elements that underpin SAP Activate and structure your implementation:
First, though, let’s address potentially the most significant change from previous SAP models…
ASAP implementations were fundamentally bespoke. During the Blueprinting stage you’d plan out what you want your SAP system to do, and then you’d build that system. No matter how much customization was required.
I’ve seen so many complicated, cumbersome, and frankly un-upgradable SAP systems. I’m sure you’ve got ever more stories of weird and wonderful implementations. It’s fair to say that before S/4HANA, no 2 SAP systems looked the same.
Activate strives for standardization. Instead of planning a system and building, you map standard functionality to as much of your business as possible, then analyze the gaps. This makes your system much easier to implement and maintain, but you might need to change your business processes to reflect the solution, rather than vice versa.
Activate consists of 3 core components. These are primarily focused on implementing and extending S/4HANA Cloud, although they also apply to other SAP Solutions.
The components feature in the SAP Activate logo (above) and are as follows:
The SAP Activate Best Practices include Predefined processes, Test scripts, Process flows, Fact sheets, Configuration guides, and General information to call on throughout your implementation project. You can think of these as a common language and rule book to keep your teams aligned.
A neat front end that lets developers quickly change aspects of the solution configuration. It automatically carries out the more complicated checks and propagation behind the scenes. Check out the video below for a look at the guided configuration in action.
The step-by-step approach. This is the element that supersedes the earlier methodologies (ASAP and Launch). We will look at these stages in the next section...
Learn about S/4HANA: Get to grips with S/4HANA in 3 easy steps
The image above shows Activate flowing through a number of stages. It wouldn’t be much of a methodology if it didn’t. Activate is a recursive process, in that each of the stages builds on the previous, then loops back on itself with continuous cycles. It can be thought of as meta-Agile.
The 6 stages of SAP Activate are:
This looks at where you are as an organization, and where you want to get to with your SAP implementation. Discover is not focused on tech for tech’s sake, but more so on how you can leverage SAP tech to get a competitive advantage.
This builds on Discover, converting those aspirations into a plan. This stage is where you get your people, hosting, and general IT needs lined up. This is also your chance to carry out training in broader concepts such as Agile or more specific SAP skills.
Explore gets into the nuts and bolts of your solution; documenting everything, creating your development environments, identifying gaps (see above), and designing your UX. You will also look at the post-live operation of the solution and make sure you have the team and infrastructure lined up.
During the Realize stage, you plug the gaps between standards and get the system ready to roll out. It ties up the loose ends and irons out any integration, performance, or other issues. If you’ve followed the previous stages and used the core components, this should be a lot more straightforward than with ASAP projects.
Pre-cutover and cutover. So, lots of testing, proving and any final training is needed ahead of the big day (weekend?).
Once you have your system in place, it meets the real world – both internal and external. Essentially BAU ops.
Learn About S/4HANA Migrations: S/4HANA Migration – The 4 Approaches
Activate has a series of quality gates to help you check your progress. These also provide a good ‘external’ voice if you’re having internal challenges about what is required and what state your project should be in.
Unfortunately, and somewhat strangely, there’s not a quality gate following the initial Discover phase. Though it may be due to the theoretical nature of Discover, it could have been a useful addition.
This gate opens when all the stakeholders have agreed on the project scope
All the stakeholders agree that the in-scope processes meet the project scope and there are no outstanding configuration questions
Systems, data, and people are in place and ready to cut over from the legacy system
Cutover has been completed successfully, and business operations are in place to use and support the system
Activate is SAP’s implementation toolkit, not just a methodology. It includes elements of both Agile and Waterfall and sits somewhere in between.
You get a vast array of elements to help you implement S/4HANA and other SAP solutions. These include 3 core Components, 6 distinct Stages, and 4 Quality Gates.
You can use Activate as a common language between disparate teams. It gives you (and your stakeholders) reassurance that you’re on the right implementation path.
SAP Activate is a prescriptive approach that will simplify and streamline your SAP implementation, without reaching the velocity of a true Agile project.
If you’re looking for a tried and trusted delivery methodology and tools, if you have rigid requirements, if you’re in a more traditional/large-scale enterprise, if you’re working with multiple partners, then Activate could be for you.
Level up your Salesforce DevOps skills with our resource library.
.svg)
.svg)
.svg)