SAP & ERP Consulting from the Customer Point of View

SAP implementation ROI, SAP architecture, & SAP business solutions

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?  By knowing what mechanisms the program or project manager(s) would be accountable it would be possible to determine who they should answer to.  There was a nearly universal lack of response.  In other words, how do you measure 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?

The most frequent response around accountability for program or project 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?

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.

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 Competency Maturity Management (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.

 

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 Competency 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?

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.

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 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 Competency 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:

How the SAP Consulting Peter Principle Works

September 12th, 2011
SAP Peter Principle

SAP Peter Principle

Most of us working in business for any period of time have heard of the “Peter Principle.”  It was “formulated by Dr. Laurence J. Peter and Raymond Hull in their 1968 book The Peter Principle, a humorous treatise which also introduced the ‘salutary science of Hierarchiology’ …” [FN1]  While the exact quote is a little different, it has come to mean that people tend to rise to their level of incompetence in organizations built on hierarchies.

As an important caveat before getting into this topic, I have known many really hard working folks who have risen through the ranks the “old-fashioned” way –, through hard work and “paying their dues.”

My Experiences with the SAP Consulting Hierarchy

After over 20 years in IT, and over 20 SAP projects, I have seen the Peter Principle again and again.  It’s the nature of how the IT consulting world works.  It is frustrating, and it is enough to drive the competent, diligent, and most talented consultants absolutely crazy.

The “Peter Principle” happens in the consulting world because this is what organizations who implement SAP demand of their implementation vendors.  Sure, that sounds counter-intuitive and crazy, but unfortunately it is a sad reality.

You might be asking yourself right now, IS HE CRAZY?  Maybe a little, but on this point, let me assure you, it is quite true and in a moment you will see exactly how it happens and why.

Enter the Crazy World of Consulting – Why Consulting Incompetence is Rewarded

Once inexperienced, incompetent, or “less than optimal” consultants get onto your SAP, ERP, or other IT project, you are now set up for seeing the “Peter Principle” in effect.  On your implementation or upgrade project an inexperienced or incompetent consultant will ultimately make a mess, however it won’t be seen right away.  There may be signs along the way, but only deep experience will recognize this unless it is blatantly obvious.  There is always some reasonable sounding explanation, or some gibberish, or some babble that is pronounced with confidence but you don’t really understand it. Or, they have become polished and provide entirely rational and reasonable explanations, whether true or not.  After all, they are the “expert” you hired so they must know what they are talking about, right?  Nonsense!

First Sign of the SAP Peter Principle

“Blah, blah, blah”  I have no idea what you just said but just so I don’t look stupid I’m not going to challenge it.

As I’ve written on many occasions, part of the key skills and experience a good consultant or business analyst MUST possess is the ability to take the complex and make it simple.  ANYONE can take something complicated and keep it complicated, or worse still, make it more complicated, or, worst of all, make it a mess.  It takes experience and competence to take the complex and simplify it.  But all that “technical babble” and jargon sounds so convincing, so educated, so, foreign.  It’s a foreign language that you don’t completely understand and these incompetents know it.  Unscrupulous consultants know if they can make something up and sound as though they know what they are talking about you will believe them –, you hired them for their expertise.  They can game you to increase scope, or extending project timelines, or busting your budget and they do this because they are personable and manipulative.

How Can You Identify the SAP Con Artists?

Accountability, Responsibility, and Quality.  The cons avoid accountability or direct responsibility.  On a project where they are discovered they must be nearly forced to have clear accountability for delivery.  They must be pressed into doing what I call “due diligence” around a solution to make sure it will work correctly.

If you catch it early enough you can keep these incompetents from being rewarded for blowing your budget, causing project delays, and creating even MORE complicated and convoluted processes than you had BEFORE you did your SAP implementation.

How Customers Provide Perverse Rewards for Incompetence

The incompetent consultant’s area seems to have users who struggle with problems / issues / bugs that need the most fixing and the most attention.  By this time many companies have invested so much time and effort with the incompetent consultant that they don’t see any other options but to continue with this fraud.  The incompetent consultant is needed badly to support the mess they make for some time after you go live.

One way you can tell you have been manipulated or gamed during the project is by the quality, completeness, and accuracy of the solution the consultant delivers at go-live. 

From a consulting firm’s perspective, the incompetent consultant puts in lots of extra billable hours, helps them get extensions and budget increases, and needs to have lots of extra consulting support.  They are always behind, and no matter how hard “they try”, they always have another excuse for why the problems they cause really aren’t their fault–, it’s always someone else.

These consultants stay on long after go-live to ensure that their questionable solutions are supported by the same person who made the mess to begin with.  This is what customers insist on because by the time go-live happens they are “stuck” with the mess and “stuck” with the “con”sultant who made the mess.

Incompetent consultants tend to be VERY personable most of the time, and ingratiate themselves with the customer / client so that there is no question that they are working SO hard, and doing such a GREAT job.  It could never be their fault.

How SAP Consulting Vendors Reward and Promote the Peter Principle

For the consulting vendor, billing hours go up, staffing and utilization numbers are high, additional “backfill” support is needed and more people are staffed.  From their metrics and possible compensation incentives the incompetent consultant is doing a great job!  On the other hand the highly experienced, competent, and diligent consultants “work themselves out of a job.”  The competent consultants tend to have fewer go-live support issues, they usually have more engaged, involved, and knowledgeable users.  And they are just plain better prepared.  They are not “needed” as you go-live and you, as the customer, get rid of them to cut the blown budget wherever you can.

In a partner oriented firm the incompetent consultant is headed for being a manager, senior manager, managing partner, etc.  The incompetent consultant has great utilization, helps to get more staff on projects, and is always busy.

In the consulting companies incompetence is rewarded and incentivized by the consulting firms.  The most competent and diligent consultants are passed over for career enhancement precisely because of their competence – they may finish projects earlier than their incompetent peers and may be “on the bench” more frequently.

The more skilled the incompetent consultant is at being personable, at presenting a compelling case for why they are doing such a great job but you need more resources, the better positioned they are for higher level promotions.  After all, in consulting firms, senior level positions are focused on getting billable resources out and billing.  The more experienced and capable at this the better positioned you are for partner or senior management.

Stay tuned next week – details on how to spot them and then ferret them out…

Related Posts: