SAP ROI — Enterprise Architecture & Business Solutions

Strategic SAP & IT Program Development for Measurable Business Value

SAP Service Delivery versus Value Delivery

April 30th, 2012

SAP Value Delivery

SAP Value Delivery

In my review of academic literature around SAP or ERP implementations I find some thought provoking items.  Recently I reviewed a study which helped me to form a more complete picture of important issues in IT delivery.  Even though I’ve been writing about it for years I gained a new clarity around evaluating some of the existing delivery models [FN1].  What it comes down to is are you looking for service delivery or business results for your SAP project?

SAP Service Delivery or Business Value Delivery – You Determine Your Future

Because my career started in business and later was exposed to SAP as part of the client core team, and then finally moved on to consulting, I have always recognized the importance of business value.  At the same time much of the System Integrator marketplace has been promoting the same old service delivery model they are familiar with.  To that end something has to change.  SAP, ERP, or Enterprise Application customers are looking for something more.  As a recent article I read noted, CIOs do NOT command the respect of the other key disciplines within the enterprise.  In fact, many of their “C” suite peers question whether or not the technology organization serves much of a useful purpose at all.  That my friends is a frightening and shocking perspective to me.  Stop and think about that a minute, many organizations question whether IT organizations serve a useful purpose in the enterprise.  Is it any wonder outsourcing and offshoring have become so popular?

What Does This Mean for SAP Projects?

At the end of your SAP project are you satisfied that a project was delivered?  Hopefully on time and on budget, but delivered nonetheless?  If you are satisfied that your SAP project was delivered on time and on budget then you are focused almost exclusively on service delivery. 

Many senior level IT leaders and delivery folks just want something to get in as quickly as possible.  This is exclusively a service delivery oriented project.  The only thing you are concerned about are the skills needed to address the particular technology / application / solution need right now.  This will NOT however provide you any type of ROI (Return on Investment) or ROE (Return on Equity) because ROI and ROE (along with other measures) are pure business metrics.  These are not IT metrics and do not measure things like uptime, response time, # of service tickets closed, etc.  The idea of ROI, ROE, or Asset Turns are USEFUL reflections of business activity and investor / owner value.  Although they may be seen as “relics” by IT folks they are still useful to understand if any value was delivered for the investment that is made.

Do you want services delivered or business benefits delivered?

Truth is, if you just want services delivered then no matter WHAT the sales pitch is ALL of the system integrators are the same.  For that matter, why even bother with a system integrator or SAP consultants at all?  Why not just go to your nearest college and recruit a bunch of really smart graduates for a temporary project and pay them about half what the system integrators charge for a temporary contract?  Seriously, why even bother with experienced consultants at all?  If SAP service delivery is your focus and not business results it is just a game of who can best make it through the sales process.  Whether it is IBM and their premium rates or Rajakrishna’s Consultant Shack and their all you can eat offshore rates.  If they can’t speak the local language it really doesn’t matter.  On the other hand if you are looking for business results that is entirely different.

If your only focus is on time and on budget then you are only looking for service delivery.  You are not looking for results, or business change, or IT transformation, or business strategy.

Let me make clear I am NOT suggesting on time and on budget projects are not important.  What I am suggesting is that if your only focus is on time and on budget then you are only looking for service delivery.  You are not looking for results, or business change, or IT transformation, or business strategy.  You are merely looking for resources to deliver services to get you to some date at some budget amount.  Any offshore or consulting shack fake will get you to a dollar amount (maybe not what you expect, but they will deliver “services”).

Where is the SAP Value Proposition Focus on Business Results?

While SAP Implementation is an Investment NOT an Event many organizations fail to consider their enterprise application deployments as strategic assets designed to produce business results.  The good news is that is changing.  So the next question is Where do you Start with SAP Return on Investment or SAP ROI?  This goes right back to the basics, you must focus on the WHY of Achieving Business Value from SAP Investment.  Is the effort about technology replacement or is there some business reason behind the initiative?

A recent IBM study under the heading of “The CIO as change catalyst” noted:

As the executive working at the nexus of business and technology, CIOs are uniquely qualified to help their companies leverage available tools to meet current economic challenges and to exploit the opportunities that will arise during this crisis—and opportunity will arise for those businesses bold enough to disrupt competition and restructure their industries. CIOs can help transform their companies by better capitalizing on the value of information assets.  They can help manage and mitigate business risk through better, more timely information. They can improve service management. They can lower enterprise-wide operational costs—including IT’s—through automation. [FN2]

SAP and IT organization heads are gaining insight and experience but at the same time they are being squeezed to cut costs and find value.

Focusing on value entails cutting discretionary spending, deploying resources for the highest return, bolstering core competencies and redefining relationships. Cash flow is central to survival and strategic flexibility, which means businesses and business units need to do more with less. Corporations must conserve capital and cut spending where it produces minimal return. Funds must then be redeployed to activities, products and markets that generate growth, improve margins and truly differentiate one business from another. [FN3]

Make Sure You Are Headed Down the Right SAP Path

To make the transition your SAP project must begin with Creating a Knowledge Centered Learning Organization for Business Transformation for IT Leadership.  Whether you are already live with SAP, in the middle of a project, or just starting out, I would strongly encourage you to get serious about Organizational Change Management Inside the SAP IT Support Organization

What most customers do not know is that SAP has offered the “Value Delivery” methodology as part of the ASAP Methodology for many years

If you want to know Why Use the SAP ASAP Methodology? for your SAP project consider the fact that SAP has offered the “Value Delivery” methodology as part of the ASAP Methodology for many years.  Over the years it has taken many forms, all the way back to the early versions of the ASAP Methodology with the old “KPI” lists.  Today it is integrated into the ASAP Methodology structure. 

Isn’t it time to pursue the value delivery method regardless of whether your system integrator is capable of this or not?

====================

[FN1]  Kieninger, A. and Satzger, G., Risk-Reward Sharing in IT Service Contracts – A Service System View, 2011 Proceedings of the 44th Hawaii International Conference on System Sciences.

[FN2]  From fear to value: CIO strategies for propelling business through the economic crisis, pg. 5.  Retrieved 4/24/2012 ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/ciw03057usen/CIW03057USEN.PDF

[FN3] Ibid. pg. 6.

Related Posts:

SAP IT Governance, SAP Program Management, SAP PMO Metrics

January 9th, 2012
Successful SAP Project Delivery
SAP Program Success

SAP Program and SAP Project Management can be tough.  In a recent Focus.com expert discussion the issue was raised about who a Project Manager or a Program Manager should be accountable to on business application projects.  Should it be the business or IT?  To help clarify the accountability I asked a simple question of what deliverables, metrics, and tasks would be required of the manager?  By knowing what the program or project manager(s) would be accountable for provides guidance to determine who they should answer to.  There was a nearly universal lack of response.  In other words, how do you measure PMO performance and how do you help to ensure results if you don’t even know what the individual, group, program, or business endeavor is going to use to measure accountability?

On this forum the most frequent response from the project and program managers was a call for ”independence.” So when I raised the issue of project manager or program manager accountability, metrics, performance, and how to ensure project messes are avoided there were no takers. 

Is it any wonder so many business application projects and programs get into trouble, go over budget and time when the individuals responsible for coordinating and evaluating them don’t want clear accountability?

SAP Program and Project Management Office Success

A good Program or Project Management Office provides the resources needed for delivery project participants to be successful.  Without this focus the value of an SAP Program or SAP Project Management Office is not realized.  The U.S. Department of Energy did a good review of performance and benchmarking for project management.  And while this was applied to a government program there is a lot of valuable insight for any SAP project or business application project [FN1].  

The U.S. Department of Energy had a committee evaluate success criteria and offered four sets or categories of performance measures to cover the 30 possible discrete measurements of project or program success.  Those four sets or categories were [FN1, pg. 1]:

  • Project-level input / process measures. Assess the resources provided to deliver an individual project and the management of the project against standard procedures.
  • Project-level output / outcome measures. Assess the cost and schedule variables of an individual project and the degree to which the project achieves the stated objectives.
  • Program- and department-level input / process measures. Assess the total resources provided for all projects within a program or department and the degree to which program- and department-wide goals for projects and their management are met.
  • Program- and department-level output / outcome measures. Assess overall project performance and the effectiveness of completed projects in supporting program and department missions.

Without this type of analysis and evaluation your project may be headed for trouble before it even begins.  When you start your large business application project what type of deliverables, output, or results do you expect from those who are leading the projects?  How will you measure and evaluate their performance?  If your evaluation of their performance is focused on how well they support the success of delivery teams, along with how well the projects are delivered (budget, scope, schedule, and quality) then you will be measuring the key project delivery values for success.

Is it any wonder so many business application projects and programs get into trouble?  One key factor for why projects go over budget and time is because so many of the individuals responsible for planning and coordinating them don’t want clear accountability.

That same U.S. Department of Energy study provided guidance on the key components for a successful performance measurement system of program or project managers which can be applied to business software projects like SAP.  They noted key components of an effective performance measurement system include [FN1, pg. 7]:

  • Clearly defined, actionable, and measurable goals that cascade from organizational mission to management and program levels;
  • Cascading performance measures that can be used to measure how well mission, management, and program goals are being met;
  • Established baselines from which progress toward the attainment of goals can be measured;
  • Accurate, repeatable, and verifiable data; and
  • Feedback systems to support continuous improvement of an organization’s processes, practices, and results.

The Answer for SAP Program and SAP Project Management Results

Over the years I have found the SAP ASAP Methodology helps to ensure SAP Project delivery.  The entire methodology is focused on project participant success; budget, time, and scope control; and quality control for project delivery. 

My non-cynical assessment for why it is not more widely used is because many SAP Program Managers and SAP Project Managers have not be trained to use these tools (or Solution Manager which contains them).  On the other hand there are some SAP Project and Program Managers who have a financial motive that can not be ignored.  They do not use the ASAP Methodology because it makes a client less dependent on them.  After all, why do you need an expensive program manager to deliver tools, templates, resources, guidance, quality control, and measurement utilities if you have a methodology that already contains all of this with step by step instructions to use it?

==============

[FN1]  Measuring Performance and Benchmarking Project Management at the Department of Energy. http://management.energy.gov/documents/performance_measures_final.pdf

Related Posts:

SAP Program Management Requires a Type of CMMI

November 7th, 2011

SAP Program Management

SAP Program Management

Many may be unaware that SAP provides a broad set of tools and resources for Program Management and Capability Maturity Model (or CMM). Very few are familiar with SAP’s broad set of supports for this purpose such as the “new” ASAP Methodology Phase 6 “Run” enhancement. It is loaded with key information which aligns with Program Management responsibilities and CMMI (Capability Maturity Model Integration) [FN1].

 

So, what is CMM (or CMMI as it is more properly referred to)?

“CMMI (Capability Maturity Model Integration) is a process improvement approach that provides organizations with the essential elements of effective processes, which will improve their performance… CMMI models are collections of best practices that help organizations to dramatically improve effectiveness, efficiency, and quality” [FN1].

The entire CMMI methodology and development is maintained at Carnegie Mellon’s Software Engineering Institute. These CMMI standards have been applied in a vast number of organizations together with various methodologies. The CMMI approach is well suited to engineering and software development, design, or implementation. SAP’s entire ASAP methodology, and especially the “new” Run methodology incorporates a number of CMMI principles.

SAP Program Management is all about Capability Maturity Management (or CMM)

The contract SAP program manager is accountable for providing the key tools, templates, techniques, and resources to ensure projects are properly managed and delivered for business benefit. If they are not providing this type of methodology guidance, including key templates and techniques to deliver business benefit, what are you paying them for?  In other words, if the contract program manager is not helping to deliver the key tools, templates, and resources to enhance your project delivery capability then why do you need them at all?

SAP Program Management or Project Management Gaps

After all these years one of my biggest frustrations is the lack of SAP contract program or project managers use of the ASAP Methodology. They all talk about it, and during sales presentations they use lots of SAP’s material, but as soon as the project begins you never see it. They seem to have absolutely no idea what they are doing.

What is the contract SAP Program Manager, or SAP Project Manager accountable for? What are they on the hook to deliver and how is their performance measured?

As I have often said, I never believe that a client / customer of project management or program management services has the primary responsibility for this knowledge. If they did why bother hiring outside help and paying the rates for this service except for that contract “expertise?”

Contract SAP program management or SAP project management that is not able to deliver on a clearly understandable methodology development are fakes. Anyone can call themselves a program manager, but what does that mean? What is the contract SAP Program Manager accountable for? What are they on the hook to deliver and how is their performance measured?

Using SAP ASAP and CMMI to Mature the SAP Enabled Enterprise

The SAP ASAP Methodology, in particular the Phase 6 Run section, should be studied by every SAP program manager before they start doing project or program work. Even though it is in the last ASAP Methodology phase, its greatest effectiveness is realized when you begin your internal SAP delivery maturity planning from the beginning of your SAP project.

One of the critical benefits of starting your CMMI related planning right from the beginning is your SAP project can be structured to support business integration at the outset. Using this type of maturity model integration as part of your project guidance can have significant benefits to the enterprise:

“Many CMMI using businesses have beneficial results to their bottom line… including improvements in schedule and cost performance, product and service quality, forecasting accuracy, productivity, customer satisfaction, return on investment, and other measures of performance” [FN2].

SAP has already done a significant amount of the work for you. All your program manager has to do is adjust the plans, alter the templates, follow the ASAP Methodology instructions, and build the resources to support this transition. You really must question SAP program manager service providers who do not keep up with the ASAP tools and delivery methodology that SAP provides and supports.

SAP’s Capability Maturity Model Starting Point

The following maturity model is just one small example of a powerful tool that is critical for long term technology and business integration [FN3]:

Maturity Level

Action Area

Characteristics

IT Support Provider

  • Vision & strategy
  • Governance
  • Processes
  • Technology
  • Culture and skills
  • Vision and strategy not formulated
  • Controlled by IT costs, focus on IT operations
  • Processes not defined
  • Isolated tool decisions
  • Focus on IT knowledge

IT Service Partner

  • Vision & strategy
  • Governance
  • Processes
  • Technology
  • Culture and skills
  • Strategy derived from IT goals
  • Controlled by IT-focused KPIs
  • Satisfies minimum criteria for SAP solution operations
  • Joint decision about selection
  • Service-oriented, knowledge of SAP solution

Business Support Partner

  • Vision & strategy
  • Governance
  • Processes
  • Technology
  • Culture and skills
  • Strategy developed in cooperation with IT management
  • Controlled by measurable service level
  • Established, role-based process organization
  • Defined standards, SLA reporting
  • Customer-oriented

Business Partner

  • Vision & strategy
  • Governance
  • Processes
  • Technology
  • Culture and skills
  • Strategy derived from company goals
  • Decisions guided by business requirements
  • Aligned with business process model
  • Integrated business processes and tools
  • Expertise in the areas of business processes, SOA, and integration

Value Partner

  • Vision & strategy
  • Governance
  • Processes
  • Technology
  • Culture and skills
  • Strategy as business enabler
  • Controlled on the basis of value contribution for the company
  • Holistic service management lifecycle
  • End-to-end management of business processes
  • Value-oriented, ongoing improvements

This model, provided freely by SAP as part of their standard ASAP methodology is a great starting point. Your contract SAP program manager should be able to use this as it is, or adjust it to fit your particular organizational needs. This is just one very small component of the Run Phase and an even smaller component of the entire ASAP Methodology toolset.

In many cases you would be better off sending your own internal employees to SAP ASAP certification courses and Microsoft Project classes and making use of their new found knowledge. At least then you would have a knowledgeable employee who could help keep an integrator who claims to use ASAP honest. And if they claim to use ASAP in their sales materials or sales pitches GET THAT CLAIM IN YOUR STATEMENT OF WORK AND YOUR CONTRACT WITH THEM!

=====================

For more information on related topics please see:

=====================

[FN1] CMMI Overview: Software Engineering Institute at Carnegie Mellon University, retrieved November 5, 2011. http://www.sei.cmu.edu/cmmi/

[FN2] Why CMMI: Software Engineering Institute at Carnegie Mellon University, retrieved November 5, 2011. http://www.sei.cmu.edu/cmmi/why/

[FN3] SAP ASAP Methodology version 7.1, WBS 6.2.1 – Table 1: Maturity Level Characteristics. For more information on the SAP ASAP Methodology please go to http://www.sap.com/services/more/servsuptech/asap.epx

Related Posts: