On your S/4HANA project, something isn't quite right...
The moon hangs low in the sky, the hours of daylight are becoming unpredictable, your colleagues are starting to exhibit unusual behaviours and Sturgill Simpson’s "The Dead Don’t Die" is resonating around the office.
Your RAID Reports are scary and the C-Suite are concerned, but no-one has foreseen the strangest and most dangerous repercussion that will soon start to plague your project: hordes of the undead will rise from their graves and start to feast on the programme.
The threat level is catastrophic - you're in a full scale zombie apocalypse.
Don't venture outside unprepared, these are the 5 most disastrous threats for Project Managers on SAP projects out of the 77 failure points identified in our SAP Success Benchmark.
It all starts with a late night in the office. You notice it’s still light after 8pm, whilst your colleague is concerned that his watch, phone and laptop have all stopped working.
If your SAP projects are managed by generalist Project Managers who don't have a background in ERP or SAP you're in trouble.
PMs are not all cut from the same cloth and that isn’t necessarily a bad thing, but generalist PMs with no background in SAP or even ERP are not going to come with:
This will result in lots of time wasted on issues that could have been avoided as well as poor design governance.
Failure can be avoided, and it isn’t just by asking a recruiter for exactly the right fit, what you need is more nuanced than a prescriptive Job Spec.
Depending on project or programme size you should create a team of Project and Programme Managers with experience in SAP, your Industry, your IT context and Business. Skills, experience, composure and cultural fit to do their jobs are equally important.
Ensuring the lead business Project Manager has experience on similar scale projects within your company or at a competitor should mean they’re primed to avoid the pitfalls of someone greener.
The next day, following a PMO meeting you realise that project reporting has altered the Earth’s rotation and the whole of the finance team have disappeared...
If you don't tend to allocate business people to SAP projects and requirements are passed through Business Analysts then watch out.
A common mistake on projects is for the wrong and often too junior Business People being allocated simply because they can be released easily from their role, this will result in decisions being made that are simply not aligned to the direction of the company.
By allocating your best possible people to SAP projects, even if that means backfilling their day-to-day roles you’ll ensure the project runs smoothly, decisions can be made authoritatively and are aligned to strategic goals.
Two coffee obsessed zombies reanimate when night finally falls, they maul a couple SAP Consultants inside the office. Adam from HR summons you to the office when he discovers their bodies in the morning. He suggests a zombie apocalypse is to blame for their deaths.
If your projects focus on technical delivery of a solution rather than business change then it could be fatal.
So many projects fail because of lack of adoption. Embedding adoption at the heart of your project rather than having it as an afterthought is critical to success. If the focus is purely on technical delivery with IT sponsorship and inadequate business ownership then the solution delivered is unlikely to be used to the best effect and won’t deliver on the benefits it has the potential to.
At the start and heart of any project is the business case. It should underpin the Business Strategy, and be all about implementing change in the business supported by IT. If adoption is at the heart of what you’re doing then the business and embedded business resources will drive your project - through design, build, test, implementation and beyond.
You find open graves when you investigate the IT department. Adam gives you some guidance on how to kill zombies and the C-Suite discuss what weapons to use.
More zombies rise from the dead that evening...
If you don't formally track Issues or Risks why are we even here.
You might think you’ve got it all covered, you’ve got a PMO analyst updating a risk log, but somehow risks keep realising, and issues appear that no one seemed to anticipate. Effective risk and issue management is central to good project control, but too often items are logged and not acted upon, or worse still not logged because of a political culture of fear and blame. This is catastrophic for any project or programme, and will definitely result in plan or budget overrun.
Risk and issue management is not just about keeping a log. To avoid catastrophic failure such as massive cost and time overruns you need to think about:
You’re overrun by zombies whilst being held up in the meeting room.
You’re stuck.
Unable to deal with her anxiety any longer one of your colleagues exits the rooms and lets the horde of zombies kill her.
Ad-hoc SAP project governance can be truly catastrophic.
From small projects to larger scale programmes, governance needs to be strong to be able to exercise the appropriate control over delivery teams and suppliers. Ad-hoc set up without clearly defined accountable internal roles can result in suppliers running rings around you, resulting in increased costs. Conversely, you might end up with a custom solution that the supplier was trying to guard against.
A good governance model is central to effective project delivery, so what is good?
You decide to go on the attack, you and Adam burst out of the meeting room and start killing the undead.