Every article on this topic.
16 articles, newest first
SAP testingS/4HANA testing strategy: cycles, criteria and roles
What an S/4HANA testing strategy has to decide: the test cycles, who owns each one, the entry and exit criteria between them, and the sections the strategy document needs before Realize starts.
· 10 min read
SAP testingSAP testing explained: types, phases and owners
What SAP testing is, the six types every S/4HANA programme needs, where each sits in SAP Activate, who should own it and how much of the programme it takes.
· 10 min read
SAP testingSAP user acceptance testing: who owns it and how to run it
SAP user acceptance testing is where the business proves the system runs its processes before go-live. Who owns it, how long it takes, and how to run scripts, defect triage and sign-off.
· 10 min read
ECC to S/4HANAS/4HANA migration timeline and project plan by path
How long an ECC to S/4HANA migration takes on each path, what the project plan holds in each SAP Activate phase, and where migration timelines slip.
· 9 min read
StrategyBest SAP implementation strategies to avoid costly mistakes
SAP implementations rarely fail because of the technology. They fail because the strategy does not fit the business, or the team cannot hold the discipline behind it.
· 13 min read
StrategySAP implementation templates: the SAP Activate set by phase
The SAP Activate templates that matter in each phase, who owns them and when they are signed off, from scoping and fit-gap to the cutover plan and go-live readiness checklist.
· 14 min read
Consulting frameworksSeven consulting frameworks for SAP and AI delivery
Most SAP and AI programmes stall for structural reasons: scope never agreed, decision rights never clear, priorities never ranked. Seven simple frameworks make those problems visible early.
· 12 min read
Consulting frameworksWhat consultants actually do: a realistic view
What exactly is a consultant doing that your team cannot? The honest answer: fixing things that should not have broken, asking questions that should already have been asked, and adding capacity when the internal team runs out.
· 9 min read
Planning & SelectionECC to S/4HANA migration: paths, steps and SAP ECC deadlines
What SAP ECC is, what changes in S/4HANA, how to choose between greenfield, brownfield and selective data transition, and the steps, tools and deadlines that matter.
· 14 min read
StrategyRequirements gathering template: 7 hacks I use on projects
A requirements gathering template only works if it forces the hard conversations early. Here is the outline I use, the five sections I never skip and seven hacks that keep stakeholders honest.
· 11 min read
StrategyHow to create an SAP implementation project charter
A project charter is the document you point to when someone contests a scope decision in month three. What an SAP charter must cover, a section-by-section outline and the mistakes that cost the most.
· 9 min read
StrategySAP project scope template: what to define and exclude
Most SAP scope disputes come from things nobody wrote down. A nine-section scope template, what to exclude in writing, and the controls that stop scope creep.
· 8 min read
StrategySAP stakeholder management: stop conflicts before they start
Conflicts on SAP programmes build from unmanaged expectations. Map the roles, write down who decides what, and run a cadence by phase before anyone has a complaint.
· 12 min read
Planning & SelectionWhat is SAP implementation? Steps, phases and process
SAP implementation explained: the six SAP Activate phases, the planning that has to come first, the team you need and what RISE, GROW and clean core change. SAP will not fix broken processes; it will expose them.
· 12 min read
StrategySAP implementation timeline: phase durations and 5 mistakes
How long an SAP implementation takes on GROW, RISE and ECC paths, how long each SAP Activate phase runs, and the five planning mistakes behind most overruns.
· 11 min read
Crisis & RecoveryHow to start your SAP implementation project right
Most SAP implementation problems are visible in month one. What to settle before configuration starts, and the six failure patterns to watch for.
· 9 min read
Tell me what you're working on.
A 30-minute call. You describe the programme, the decision or the problem. I'll tell you whether I can help, and if I can't, who might.
