1. For internal use of Gartner only. © 2003 Gartner, Inc. and/or Gartner Holdings Ireland. All Rights Reserved. Page 0 Enterprise Systems Knowledge Community Business Case January 2003 consulting Definition (thanks Mr. Keller) A business case is a systematic identification, analysis and documentation of the relative attractiveness of multiple investment alternatives. A business case can help executives:  Select and prioritize funding from among competing projects  Select a vendor or consultant once the project is determined  Track project milestones to confirm that the project is meeting expectations  Confirm the final results of the project Business Case Components: Business Case  Problem Statement  Impact on the future  Objectives in specific terms that will be understood by all critical stakeholders  Design - Rationale and Approach. Include an analysis of alternatives discarded.  Benefits. Tangible and intangible.  Costs (and Funding Sources for Public Sector)  Cost-benefit analysis  Performance Measures  Assessment of the risk of unacceptable outcomes

2. For internal use of Gartner only. © 2003 Gartner, Inc. and/or Gartner Holdings Ireland. All Rights Reserved. Page 1 Enterprise Systems Knowledge Community Business Case January 2003 consulting For each Engagement Type (row on the ES Matrix) Methodology First (execution kits: Sales, Delivery and References follow)  Components (using the Sourcing terminology - Aren’t these really “Steps”?) to be carried out - basic structure will be similar for each Engagement Type with some variations for each. Each step can consist of rules (items considered mandatory if employing the Gartner Consulting Methodology) and guidelines (items considered good practice but optional). This is at a lower level of detail than the Sourcing “x” and “o”.  Any item within each step may include references to standard Gartner Consulting Techniques to be deployed. Any "Technique" will be a detailed methodology to provide a specific result and be supported at a very granular level of detail. Techniques support modularity (may be replaced by a technique considered mandatory by the client) and reusability (may be deployed from a variety of cells in the ES Matrix). Examples of "Business Case" techniques would be NPV calculation and Sensitivity Analysis. Techniques in the risk assessment area may be shared between "Business Case", "Planning" and "Independent Project Management". Each Engagement will require an additional step  Deciding which parts of the methodology to use.  Needs to be carried out during proposal development and not necessarily visible to the client - it will impact pricing and schedule.

3. For internal use of Gartner only. © 2003 Gartner, Inc. and/or Gartner Holdings Ireland. All Rights Reserved. Page 2 Enterprise Systems Knowledge Community Business Case January 2003 consulting Proposed Steps to Develop Business Case Methodology Explore history - what have we done in real engagements? Choose some exemplary Engagement Types Identify Steps and Techniques for these examples Provide first iteration of steps and techniques for the ES Matrix Identify gaps to be filled in  Development of Gartner Consulting Standard Techniques  Expand to other Engagement Types  Changes to the ES Matrix  Completion of the Execution kits in each of the ES Matrix cells Move to next iteration