SAP Project Rescue & Recovery

SAP Project Rescue & Recovery

We admit: not every project needs rescue. But once you are in trouble can realign your project. And since we know to fight fire, we also know how to avoid it from the beginning!

EXPERIENCE IS OUR WEAPON

Working with SAP R/3 since the early beginnings in 1993 (and before with R/2) we know all the technology components and constraints around the SAP world. We configured many systems, we wrote tons of ABAP code to fill the missing gap of the software and we did not rest to teach our clients the pros and cons of certain components.

INTEGRATE SAP AND THE REST

Let us be honest: not everything that has the label "SAP" deserves the label. We believe that SAP is amazingly strong in ERP and its derivates, but we are also aware that SAP is only a component in an agile and dynamically changing IT ecosphere. Therefore we work on integrating SAP and other amazing software components. If you need e-Commerce you better take a professional web shop that uses SAP as back end, if you need special reporting needs you choose the best data analysis tool and if yur portal is already SharePoint: why not make it work smoothly with SAP alone? Thebuzzword of the decse for all this integration is "Cloud" and used to be "SOA" (Service-oriented architecture) right before. For us it is still integration as we are used to work for two decades now: once it was LapLink to allow data exchange between to PCs through a printer cable and now we exchange data in real-time through the internet cloud.

SAP is our passion. We like to make it work!

PROJECT RESCUE

Project Rescue - Putting out fire before it starts

WKB & PARTNERS offer dedicated task forces for project rescue of international SAP, ERP and SOA projects. The group is formed from a number of extremely experienced trouble-shooters who have spent their whole professional life not in a cosy planning bureau but right in the middle of the project battlefields. They solve seemingly intractable project contention and they mentor project managers to avoid paths that lead to trouble.

Project Rescue is in high demand in the recent years. The reports of failing projects soar. While this is a normal corollary when the number of real projects rise it is true that the number of failing projects is exorbitantly high. Pessimistic estimates of the big analyst firms speak of more than 50% failure ratio if they include those project whose initial ambitious goal has been changed.

A failing project is like your house burning down: it simply must not happen. And we know that there are proven precautions that prevent a house from suffering damage from a fire outbreak.

Project rescue is like the fire brigade whose holy duty is in assisting people to avoid a fire from breaking out. But if the disaster happens they are prepared to extinct fire through a well-trained set of methods. The skills to be a project rescuer are not taught in IT project management but rather in classical political and diplomatic schools, where you learn the art of mediation, compromise and risk containment. Project rescue is hence a complement to traditional project management bodies. While the latter design ideal landscape architectures a fire man deliberately shakes up the whole system to find out if the parts would fall back in consistent places after a disaster.

Project rescue is a sensitive issue. You know your project is failing but calling for external help could be extremely embarrassing. Therefore we promise maximum discretion when getting in touch with us. A rescue mission Task Force is handled by a Task Force Captain and one more First officers who lead their own Special Action Team (SAT). You normally meet the captain first who discusses with you the severity of trouble and the general strategy and constraints of action. Depending on the outcome of the talks the project manager and the Task Force Captain agree to bring in special skills SAT to resolve issues in a dedicated area.

A SAT normally acts in a form of disguise. They do not take over project management nor do they decide on behalf of the people in charge. However, they rather suggest changes in project structure and project goals and prepare the decisions accordingly. Crucial decisions will not be ordered top-down but are normally made in incubating the ideas until everybody can consent and signal White Smoke.