So everyone is back from SAPPHIRE and TechEd with their heads full of the art of the possible :-
- Optimised Core
- Mobility (M)
- Cloud (C)
- In Memory (iMC)
E = MC(iMC)sq ! – see Keynote
But you don’t need Einstein, now more than ever you need an IT development team with the right skills (or access to one). Without this you just aren’t going to know where to start with most of the cool technologies from SAP.
This doesn’t mean that the traditional skills required to configure the SAP business systems are not important it is more that to make your SAP system stand out from the crowd (and do stuff your competion can’t) you need developers to build (hopefully cool) stuff on top of it.
In this blog from 2010 Stephen O’Grady of RedMonk coined the phase “Developers are the new Kingmakers” when discussing the adoption of open source, I have adapted this for organisations with an SAP strategy to “Good SAP Savvy Developers are the new Kingmakers”.
So why the 3 extra words :
By “Good” I mean Developers who have either set out to be developers as a career and therefore have a strong technical background in topics like data design, object oriented programming and user interface design (or have some how acquired these). Many classic SAP developers do not fall into this class having started doing a bit of ABAP during their first implementation project and have been cutting and pasting ABAP ever since. So for good you could read Professional Developers.
By “SAP savvy”, I mean developers that understand all (or at least many) of the options that are available to them (from SAP and others). With this knowledge they can mix and match technologies to achieve the business outcomes required (or even innovate something themselves – many developers are quite a creative you know). Being fully aware of the SAP supported tools and techniques will ensure that organisations make informed choices about the options they take when implementing solutions. This doesn’t mean that these solution can’t involve others vendors software or open source, but when these are used short and long term support and interoperability should be considered. A good example here is the use of jQueryMobile to create user interfaces instead of WebDynpro, on the upside you get an HTML5 UI, on the downside when the libraries don’t work as planned, who do you turn to ? not SAP. However once SAP NetWeaver User Interface for HTML5 (or what ever it will be called) is shipped next year, we can enjoy the benefits of HTML5 and long term support from SAP.
If you give tools like HANA, Gateway, SUP, BPM, Duet, River etc to developers like those described above great things can be made to happen (look at what happened on the SAP Train Race), so if the wanabe Business Kings can point these GSS developers at the right problems (with the help of a good BPX) they can ride to the top on a wave of IT powered innovation.
So why is the world not full of Wanabe Business Kings fighting for the top jobs based on their innovative development teams ?
To answer this we need to look back to see how developers were viewed about 10 years ago. Many organisations took a look at their IT developers (geeks) and decided that IT development was a commodity that could be given to a 3rd party provider and so IT was outsourced across the globe. Most of these outsourced deals focused on driving down the cost of IT (it was viewed as a commodity after all).
What this often also drove out of the deal was any wiggle room for Developer Innovation. 10 years on this means that many organisations and IT outsource providers have all but forgotten how to innovate – SLAs and Margins are king. In effect organisations have thrown out the baby with the bath water.
So developers like plumbers are not all born equal – if you can find a good one keep their number, you will definitely need it soon.