Вы находитесь на странице: 1из 54

ASAP 7 Business Add On for Agile Implementations Agile Business Blueprint

Introduction
Agile Business Blueprint Approach
After this session, you will

Understand the context of implementation acceleration Understand how the lean blueprint approach enables an accelerated agile implementation

Be able to identify the key deliverables of the lean blueprint approach


Understand how Solution Manager is being used for a lean implementation approach

SAP 2010 / Page 2

Agenda

1. Implementation Acceleration

Market Demand Conceptual View on Implementation Acceleration

2. Agile Business Blueprint

Blueprint Components Key Deliverables

3. Solution Manager and the Lean Blueprint Approach

SAP 2010 / Page 3

Agenda

1. Implementation Acceleration

Market Demand Conceptual View on Implementation Acceleration

2. Agile Business Blueprint

Blueprint Components Key Deliverables

3. Solution Manager and the Lean Blueprint Approach

SAP 2010 / Page 4

Our Customer Expectations are Changing


These Trends are Impacting Services Significantly
Key TRENDS from Services point of view Deliver Fast, packaged, low TCI offerings Need to respond as buying power shifts from IT to business Holistic, quality implementations focused on quick time to value Insight optimization for fast access to information on a suite of devices Organizations have short attention spans, therefore early and frequent delivery of benefits is needed

Enhanced visibility and measurable results

SAP customers are looking to receive early and frequent confirmation that their requirements can be met cost effectively, in order to minimize risk and build confidence in the solution. There is a need to demonstrate capability to solve customer pain points early in or at the beginning of a project, through Proofs of concept, Proofs of vision, and Solution Demos
SAP 2010 / Page 5

Business Blueprint Approach

SAPs Blueprint Approach is based on the following proven methodologies Value Management, which creates the method for scope and delivery of expected benefits Business Process Management (BPM), which provides the framework for process decomposition Agile Acceleration Techniques at SAP, that support the speed to market; they incorporate visualizations, iterative feedback loops and frequent control points

Business Process Management / SOA


BPM Field Service Modeling Handbook

Acceleration Techniques
Solution Demo & Visualization Best Practices and Preconfigured Solutions Sprints Value Prototyping Visualization Techniques

Value Management
Value based scope management Value maps and enablers Industry Benchmarks Value Audits

Blueprint Quality Review

SAP 2010 / Page 6

Implementation Acceleration
Broader than Agile

Acceleration is based on the re-usable content, tools, and supporting technologies Acceleration means visibility to the progress Acceleration means getting it right the first time Acceleration is time compression - parallelization of services Acceleration is lean and has minimum redundancy in deliverables Acceleration means organizational readiness
Smallest possible increments (projects) along a value based roadmap (strategy)

IP Re-Use Acceleration = [Processes & Industry Solutions]

Reduction of Friction [Organizational Readiness]

x
Parallelization [Productized Services]

Elimination of Re-Work [Process Blueprint, PoC, Solution Demo, Iterations]

Managing the speed of value becomes a competitive advantage for SAP

Legend: IP Intellectual Property POC Proof of Concept


SAP 2010 / Page 7

Major Acceleration Techniques


Supported through ASAP 7
IP Re-Use Business scoping and Blueprinting Best Practices / Preconfigured solutions / RDP Business Add Ons - Jump Start for Content & Solutions Project Launch Services / IP Environment Solution Demo Approach

Early visualization of solution and development objects Iterative solution design process (workshop approach)

Iterative Build

Value Based Roadmap and Product Strategy [Program]


Incremental build and test cycles [Project] Frequent Q-Gates - Time boxed and inspected increments [Project]

Parallelization of Services

Integrated Service Delivery Value Prototyping Rapid Deployment Solution

SAP 2010 / Page 8

Complementary Techniques

Agenda

1. Implementation Acceleration

Market Demand Conceptual View on Implementation Acceleration

2. Agile Business Blueprint

Blueprint Components Key Deliverables

3. Solution Manager and the Lean Blueprint Approach

SAP 2010 / Page 9

Agile Business Blueprint

BLUEPRINT COMPONENTS

SAP 2010 / Page 10

Hybrid Agile
ASAP 7 Acceleration Add-On
Prep Working Software Release 2 Business Blueprint Project Backlog
Rank Eff.

Realization Release 1

Final Prep

Go-Live

Run

Realization Release 2

Release 1 Should Checkpoint Checkpoint Business Process Agility Workshop Checkpoint

Setting the scene

Sprint

Evaluate

Accelerators Project Prep. Process WS & Sol.Archit. Evaluation & Release Planing Baseline Build Sign-Off

Getting the organization ready

16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01

4 5 1 8 2 7 3 4 2 2 4 3 3 6 4 5

Would

Sprint Sprint Prep. Sprint Sprint IT Final Prep. Sprint

Business Priority

Could

Support

Demo

Must

Time

Demo

Demo

Demo

Go Live

Demo

Data Management Run Organizational Change Mangement Enablement


SAP 2010 / Page 11

Demo

Agile Business Blueprint

Scoping based on process reference content e.g. SolMan Process Hierarchy

Business Process Workshops

Solution Architectur e

Baseline Build

Solution Demo

Evaluation and Release Planning

Purpose To create a body of work, know as Business Blueprint that Aligns business requirements to the SAP business model Documents the TO-BE process models

Deliverables Process and Solution Design Business Process Hierarchy and Design Value Association on Process Level Solution Design

Milestones & Key Decisions Completed and signed off Process Design Completed and signed off Solution Design Delta List Phase Quality Assessment

Describes the solution design Identifies function Gaps Obtains business sign-off the design Provide early confidence for the SAP solution Plan for releases and sprints

Gap Identification and Resolution Solution Landscape and Architecture Scoping - Plan for Sprint cycles Baseline Build Project Backlog

Communication Plan Final Backlog prioritized Sprint Definition

SAP 2010 / Page 12

Agile Business Blueprint


Guiding Principles and Concepts

The Agile Blueprint Approach follows two Guiding Principles: Lean Documentation: While maintaining the characteristics of ASAP7 key deliverables of Blueprinting, documents are lean and reduced to a minimum set of information needed for the Business Process and Solution Design Baseline Build for the Solution Demonstration: During Blueprinting a Baseline system is build that serves as the system for the solution demo approach as well as the system for further configuration and development during Realization (Sprints). As applicable, the Baseline system is build with preconfigured solutions such as Best Practices or Rapid Deployment Solution. Blueprint Deliverables All Blueprinting deliverables need to be agreed upon prior to Blueprinting and have to be formally included into the Blueprint Q-gate process A lean Blueprint contains the minimum set of information needed to define or verify Business Processes and the Solution The minimum set is defined as the Lean Blueprint deliverables template Lean Blueprint deliverables may be augmented with ASAP 7 Core Blueprint deliverables If not specifically indicated, core blueprint deliverables remain in place Process are captured based on the lean Blueprint templates, optionally flows are modeled according to the SAP Modeling Standards Usage of Solution Manager It is recommended to leverage Solution Manager as an enabling tool for the implementation Solution Manager offers optional modeling capabilities in the graphical representation of the process hierarchy

SAP 2010 / Page 13

Agile Business Blueprint


Process Workshop and Solution Architecture

Scoping based on process reference content

Business Process Workshops

Solution Architecture

Baseline Build

Solution Demo

Evaluation and Release Planning

Activities

Deliverables

Execute Business Process Agility Workshop Illustrate SAP Standard Functionality leveraging the Solution Demo Approach Define Solution Architecture

Accelerators

Templates: Business Process Design Documents (lean) Project Backlog Cross functional requirement slide Security Requirement slide Issue list Customer deliverable list Sign off document Base line scope

Process and Solution Design Documents (lean) Business Process Requirements Role Concept and Authorization Requirements Solution Gaps per process (initial Project Backlog) Issue list Customer deliverable list Customer feedback on solution fit gap Signed off Baseline scope

Main Objectives

Demonstrate Standard SAP (Solution Demo Approach) Verify SAP Standard processes Define and agree on baseline scope Prepare the baseline system Identify Business requirements Identify Solution Gaps Refine Process Scope and Solution Architecture

SAP 2010 / Page 14

Agile Business Scooping

SAP 2010 / Page 15

Agile Business Blueprint


Process Workshop

Input
Executive Alignment Workshop Engagement Proposal and Statement of Work Process Value Determination Business Process Reference Content/ Map = Scope Solution Demo Accelerators: SAP Best Practices / IDES / RDS Roles and Responsibilities SAP/Customer

Output
Process Workflow SAP Match

Business Process Agility Workshop

Initial Project Backlog

Business Requirements

Issue list

Main Objectives
1. Demo SAP Standard 2. Buy-In for SAP Standard/Best Practices 3. Verify Processes and Scope

Customer deliverables list

Sign off Baseline scope

Authorization Concept

SAP 2010 / Page 16

Business Blueprint
Business Process Agility Workshop

Main Objectives

Business Process must be known before delivery starts Define Group 1 & Group 2 Processes , which will be supported by SAP Best Practice (standard) Apply Group 1 & 2 Process Parameters As Group 3 processes are identified, a separate BPM-Business Process AS- IS Analysis is necessary (not part of Agility BPM)
SAP 2010 / Page 17

Agile Business Blueprint


Baseline Build

Scoping based on SolMan Process Hierarchy

Business Process Workshops

Solution Architecture

Baseline Build

Solution Demo

Evaluation and Release Planning

Activities

Deliverables

Planning Baseline, based on process blueprint Customizing of SAP Standard functionality Verify and complement process and solution documentation Check points every second week Optional Activities Use of Value Prototyping Service Use of Predefined Services as a starting point Enhancements to SAP Standard Mock ups and Visualizations of development object and end to end scenarios through software such as iRise

Detailed Baseline build plan Lean Customizing documentation Lean Cross functional documentation Lean Authorization and Security documentation

Optional Deliverables Extended documentation of enhancements (functional specification) Mock ups, or Visualizations

Main Objectives

Accelerators

Templates: Customizing documentation Cross functional documentation Security documentation Lean Blueprint documentation Other: SAP Modelling Handbook
SAP 2010 / Page 18

Enable SAP processes in scope in customer environment with Standard SAP (Customization only preferred) Baseline for Project Backlog Baseline for Lean Blueprint

Business Blueprint
Baseline Build

Checkpoint Realize Baseline Process -(Standard SAP) Detailed planning Documentation, continuously updated

Checkpoint Realize Baseline Process (Standard SAP)

Realize Baseline Process (Standard SAP)

Documentation, continuously updated

Documentation, continuously updated

Demo & Baseline evaluation

Qualify new requirements Baseline review

Main Objective

The Baseline Build objective is to compare customer requirements against the SAP Standard functionalities. The outcome serves as input for the Project Backlog of the Evaluation phase

SAP 2010 / Page 19

Agile Business Blueprint


Baseline Build Check Point / Solution Demo

Input
Solution/Process realized so far

Output
Solution Demo

Initial Project Backlog (Product Backlog)


SAP Standard / Best Practices / RDS Documentation

Baseline Build Checkpoint (Solution Demo)

Process and Solution Documentation

Updated Project Backlog (Product Backlog)

Main Objectives
Checkpoints are mini reviews for process owner(s) to show progress and to explain how Standard SAP works. As a rule of thumb checkpoints should be planned every 2 weeks

SAP 2010 / Page 20

Business Blueprint Phase


Baseline Solution Demo

Scoping based on SolMan Process Hierarchy

Business Process Workshops

Solution Architecture

Baseline Build

Solution Demo

Evaluation and Release Planning

Activities

Deliverables

Baseline evaluation workshop (Fit/Gap Analysis)

Accelerators

Revised Process Map / Process flow (Product backlog showing fits and gaps) Project Backlog (gap list) Lean Business Blueprint

Templates: Baseline evaluation slides Lean Business Blueprint Other: Link to

Main Objectives

Demonstrate SAP processes to stakeholders Re-evaluate Project Backlog Customer to understand what the fit-gap is

SAP 2010 / Page 21

Agile Business Blueprint


Baseline Evaluation Solution Demo

Input
Baseline Solution

Output
Baseline Solution

Solution Demo
Process Documentation

Updated and approved Baseline Solution Documentation Revised and approved Process documentation

Solution Documentation

Business Requirements

Approved Requirements in Project Backlog

SAP 2010 / Page 22

Solution Demo Approach


Refer to ASAP 7 WBS 2.5.1 Blueprint Approach
Iterative Approach to Process and Solution Design driven by process de-composition
Visualize, Engage, Stay Focused! Visualize solution to Improve collaboration and mutual understanding

Reference Set Boundaries Business Case and Value Drivers Provide Context

Mitigate risk to rework Allow for early buy in and incremental acceptance Verify & Accept Verify process & solution design Drive Acceptance Complement Process Models Solution Design Visualize Show and tell SAP standard key design elements Visualization for Development objects

Listen & Engage Capture business requirements Identify gaps to Standard

SAP 2010 / Page 23

Solution Demo Approach


Reference
Workshop Part 1: Set Boundaries Provide End-to-End Scenario context Demonstrate continuity of the SAP engagement Provide value context relevant to the Business Process being worked on Business case relevance Pain Points and Value Drivers Define measures of success (KPIs / PPIs) Set the stage for Scope Management

Prerequisite: Knowledge transfer from CVR or Pre-Sales

Reference Business Case and Value Drivers Use predefined standards and content to illustrate end-to-end processes

Tool Set

Business Process Library / Customer Process Innovation CPI

Verify & Accept Verify solution design Drive Acceptance

Visualize Use sandbox to show and tell SAP standard key design elements Visualization for Development objects

Collaborative Value Realization Results

Complement Models Solution Design Listen & Engage Determine / capture business requirements and potential Gaps to Standard

SAP 2010 / Page 24

Visualize, Listen for Gaps, and Negotiate

Workshop Part 2 - Visualize and Listen


Make sure business SMEs understand our standard solution Provide a good visual of the proposed Solution Show Standard functionality in a Sandbox environment or IDES system Show process flows / Solution Manager Process Hierarchy Leverage Prototypes, as applicable Mock up Development Objects, refer to iRise Be prepared for negotiations

Reference Business Case and Value Drivers Use predefined standards and content to illustrate end-to-end processes

Tool Set:

Show and Trial Solutions / IDES for SAP Standard iRise to visualize development objects and end to end walk through sessions

Verify & Accept Verify solution design Drive Acceptance

Visualize Use sandbox to show and tell SAP standard key design elements Visualization for Development objects

Complement Models Solution Design Listen & Engage Determine / capture business requirements and potential Gaps to Standard

SAP 2010 / Page 25

Solution Demo Approach


Listen and Complement Models
Workshop Part 3: Listen, Learn, Challenge and Complement

Capture and verify requirements What do you need to do? How does that work? Why is that important? Identify Gaps Complement Process Models Determine Process Owner Associate Measures [KPIs / PPIs] Close the loop to the Business Case Challenge to drive improvement/change

Reference Business Case and Value Drivers Use predefined standards and content to illustrate end-to-end processes

Tool Set:

SolMan - Business Process Hierarchy / Graphics Visio / ARIS, as applicable SAP Modeling Handbook

Verify & Accept Verify solution design Drive Acceptance

Visualize Use sandbox to show and tell SAP standard key design elements Visualization for Development objects

Complement Models Solution Design Listen & Engage Determine / capture business requirements and potential Gaps to Standard

SAP 2010 / Page 26

Solution Demo Approach


Document and Drive Acceptance

Document Capture key decisions Produce design deliverables Verify Hold follow-up meetings to validate/refine Blueprint requirements, and to obtain closure to open issues Perform integration sessions to define linkages, input and output handoffs (as required) Drive Approval / Get Buy In Visualizations and end-to-end walk throughs Roadshows, ASE-like workshops Obtain Sign-off in written format
Reference Business Case and Value Drivers Use predefined standards and content to illustrate end-to-end processes

Tool Set:

Solution Manager [SOLAR01] Upcoming pilot on Collaborative Blueprinting Road-shows and ASE-like workshops Visualizations of end-to-end walk throughs (e.g with iRise)
Verify & Accept Verify solution design Drive Acceptance Visualize Use sandbox to show and tell SAP standard key design elements Visualization for Development objects

Complement Models Solution Design Listen & Engage Determine / capture business requirements and potential Gaps to Standard

SAP 2010 / Page 27

Agile Business Blueprint


Evaluation and Release Planning

Scoping based on SolMan Process Hierarchy

Business Process Workshops

Solution Architecture

Baseline Build

Solution Demo

Evaluation and Release Planning

Activities

Deliverables

Process owner activities Qualify delta requirements per process Prioritize delta requirements Maintain story map Sign off on Project Backlog Define scope of first release High level effort estimate on identified requirements Release planning / critical path analysis Estimate of remaining work

Signed off process definition including fit/gap analysis Signed off Project Backlog (to be realized during sprints) Resource sheet Story map Release plan Sprint schedule Quotation for remaining phases, as applicable

Main Objectives Accelerators

Templates: Sprint and Release plan Sprint Schedule

Final Project Backlog from process owner Final priorities from business & technical perspective (ranked list) High Level Effort Estimation Release Planning Preparation of first Sprint

SAP 2010 / Page 28

Agile Business Blueprint


Evaluation and Release Planning

Input
Project Backlog

Output
Prioritized and Signed Off Project Backlog and Release Plan

Evaluation and Release Planning


Process Documentation

Resource Planning

Solution Documentation

Story Map

Business Requirements

Sprint Schedule

Estimate for remaining phases, as applicable

SAP 2010 / Page 29

Agile Business Blueprint

KEY DELIVERABLES

SAP 2010 / Page 30

Lean Blueprint Deliverables

Lean Content

It is recommended to Blueprint with Solution Manager. However, Blueprints may be produced based on the ASAP templates only if SolMan is not leveraged

Accelerated Implementation Lean Blueprint Template.xls

Approach Fit

Minimalistic Suited for implementations without Solution Manager Limited number of authors Manual document management required

Solution Manager Based Suited for implementation leveraging Solution Manager as a repository for the solution build Goal to leverage life cycle functionality of Solution Management Comprehensive approach to manage the solution

Considerations

SAP 2010 / Page 31

Lean Blueprint Approach and Key Deliverables

Project

Lean Blueprint Approach Guide*

Lean Blueprint Template: Organizational Structure Req. & Design

Lean Blueprint Template: Scope Key Decisions

Business Scenario

Business Area/ Process Group

Lean Blueprint Template: Cross Functional Business Objects

Lean Blueprint Template: Business Process Map / Scenario Overview

SAP Modeling Handbook* Lean Blueprint Template: Business Process Design Business Process or Variant

Business Process

Lean Blueprint Template: Cross Functional Business Objects

Business Process Flow diagrams Optional in SolMan

Business process step

(Transaction e.g. VA01 )

Lean Blueprint Template: WRICEF list incl. Functional Specifications

Value Maps - Optional

Activity/ Transaction

(Data entry e.g. customer name)

Technical Solution Doc ASAP 7 Core

A Blueprint is defined through a body of documents


Solution Manager Process Decomposition
SAP 2010 / Page 32

* Guideline documents to facilitate Blueprinting

Key Decision Document - Lean

Document Focus

Capture decisions that impact scope and/or solution Update in key decision log Key decision to be reviewed and signed of by project management office One line per key decision

Expected Outcome

If applicable, key decisions are associated to process hierarchy


Project Sponsor Understand the decision to be made Discuss potential solutions / options

Document Ownership

Completion Considerations

Pros Cons Cost impact Capture accepted solution / decision Capture approval of document
Scope and Key decision template Project Level

Optional Core Document

SolMan Destination:

SAP 2010 / Page 33

Issue Log Document - Lean

Document Focus

Capture issues that impact scope and/or solution Updated issue log One line per issue If applicable, key decisions are associated to process hierarchy Project Sponsor Identification of issue Classification of issue Status management of issues

Expected Outcome

Document Ownership

Completion Considerations

Identification of owner Identification of action items / activities Identification of time frame for resolution Captured resolution
Issue List Project Level

Optional Core Document

SolMan Destination:

SAP 2010 / Page 34

Business Scenario Design - Lean

Document Focus

Focus is on define the scenario and associated processes and understanding business objectives and drivers Update Business Scenario Overview, graphically

Expected Outcome

Document Ownership

Process Owner
Identify all processes that are part of the scenario Identify Ownership List Improvement Opportunities and Pain Points Identify associated KPIs Business Process Hierarchy build out in Solution Manager Business Scenario Design Document Scenario Level

Completion Considerations

Optional Core Document

SolMan Destination:

SAP 2010 / Page 35

Business Process Design - Lean

Document Focus

Focus is on define the processes, associated business requirements, objectives and drivers, as well as inputs, outputs, impacts, integration, authorization and realization considerations Updated process description Note: this document can replace process flows and the business process document Process Owner Identify process ownership Identify all processes steps Associate requirements / delta list Identify gaps (standard SAP vs. development) Identify associated KPIs / PPIs Business Process Hierarchy build out in Solution Manager Updated Backlog

Expected Outcome

Document Ownership

Completion Considerations

Optional Core Document

Business Process Design Document Business Process Flows


Process / process step level

SolMan Destination:

SAP 2010 / Page 36

Delta List - Lean

Document Focus

The delta list captures functionalities to be build as part of realization (sprints) Focus is on defining requirements that are not covered with SAP standard functionality in order to feed them into the back log Updated delta list Process Owner Identification of SAP gaps Association with SAP business process Priorization of log items Association with Sprint cycle Business Process Requirements Document Process / process step level

Expected Outcome

Document Ownership

Completion Considerations

Optional Core Document

SolMan Destination:

SAP 2010 / Page 37

Functional Specifications / WRICEF List - Lean

Document Focus

The lean WRICEF list serves two functions: It identifies the development objects as a basis to plan for sprints and estimates It contains core elements of Functional Specifications Note: this document serves as direct input to technical specifications Updated WRICEF list Process Owner Identification of all WRICEF objects Association with processes Functional information captured per object Priorization of WRICEF object Identification of complexity and estimated effort to realize WRICEF list Functional specification Process / process step level WRICEF structure node

Expected Outcome

Document Ownership

Completion Considerations

Optional Core Document


SolMan Destination:

SAP 2010 / Page 38

Cross Functional Business Objects - Lean

Document Focus

Identification of Business Objects, such as Master Data, Organizational Elements, or General Settings Understand the solution design considerations and data migration consideration per object Detect governance processes This list is complemented with the Master Data List and Organization Hierarchies Updated Cross Functional Bus. Object document Process Owner Identification of all cross functional business objects Identification of Ownership Capture attributes for each object type Determine gaps and delta lists items Master Data Design Documents

Expected Outcome

Document Ownership

Completion Considerations

Optional Core Document

Organization Structure Design Documents


Scenario / Process level

SolMan Destination:

SAP 2010 / Page 39

Organizational Hierarchy - Lean

Document Focus

Capturing SAP Organizational Hierarchies Translation of business view to SAP hierarchy view Updated Business Process Hierarchies

Expected Outcome

Document Ownership

Process Owner
Identification all organization hierarchies Identification of hierarchy elements Integrated functional views

Completion Considerations

Optional Core Document

Organization Structure Design Documents


Scenario / Process level

SolMan Destination:

SAP 2010 / Page 40

User Role Concept - Lean

Document Focus

Identification of User roles per process Updated user role concept as a basis for the authorization and OCM concepts

Expected Outcome

Document Ownership

Process Owner
Identification all process related user roles Association of Business Organizational Units with the user role Definition of corresponding SAP organizational units

Completion Considerations

Optional Core Document

Organization Structure Design Documents


Scenario / Process level

SolMan Destination:

SAP 2010 / Page 41

Blueprint Quality Phase Gate

Phase gates are an important concept and control mechanism and mitigate project risks ASAP7 delivers a project management phase gate for Blueprinting that remains AS-IS for a Lean Blueprint with the exception of

Substitution of ASAP core deliverables with Lean Blueprint deliverables Addition of Demo Build Baseline Build Delta List Build Sprint Cycles defined

SAP 2010 / Page 42

Agenda

1. Implementation Acceleration

Market Demand Conceptual View on Implementation Acceleration

2. Agile Business Blueprint

Blueprint Components Key Deliverables

3. Solution Manager and the Lean Blueprint Approach

SAP 2010 / Page 43

Agile Business Blueprint


Guiding Principles for Solution Manager

It is recommended to leverage Solution Manger for Blueprinting If Solution Manager is being used, each lean deliverable will be associated with the Business Process Hierarchy just like any other SolMan supported implementation In addition, it is recommended that Solution manager serves as an organizational tool to

Manage the Project Refine scope and model process Capture solution design characteristics Leverage reporting functionality

The following pages describe core functionalities that should be leveraged in Solution Manager For detail on the usage of Solution Manager refer to the ASAP7 Core Solution Manager Usage Guideline

SAP 2010 / Page 44

Scope Definition Through Solution Manager Only

The Business Process Hierarchy in SolMan serves as the as central and binding element for

Scoping Work management Document repository

It is recommended that the process hierarchy is being set up during Project Preparation For Lean Blueprinting is may also serve as the graphical component of process flows

SAP 2010 / Page 45

Process Modeling / Flows

The Business Process Design is an important step for Blueprinting At a minimum the following documents need to be created to comply with Lean Blueprinting

Lean Blueprint Process Description Business Process Hierarchy Setup in Solution Manager Additional process characteristics in BPD or simple spreadsheet, as needed ARIS Business Process Models Modeling capabilities of Solution Manager Graphical models in Solution Manager can be enhanced Additional manual steps or activities in non SAP systems may be added

Optional graphical modelling


For details on the Solution Manager Usage, refer the Solution Manager Usage Guidelines and the SAP Modeling Notation

SAP 2010 / Page 46

Process Attributes in Solution Manager

Additional Process Attribute may be maintained in Solution Manager in order to document process characteristics On a process lever, the project team may indicate

Whether development is need for the implementation project KPI can be associated Sizing relevant information may be captures Core / commodity processes can be distinguished keyword may be created to associate process to release and sprint cycles

SAP 2010 / Page 47

Enabling Sprint Administration during Blueprinting


Leverage

key word to manage projects

Priorities of scope (determination of product backlog) Release to define shippable Product Sprint Indicators to identify Sprints

Gap Identification TBD, association of functional spec might be sufficient

SAP 2010 / Page 48

Test Case Association

Test cases are loaded as document types and captures in the test case tab of Solution Manager

SAP 2010 / Page 49

Efforts for Realization

Solution Manager may also be leveraged for the Management of effort The Administration Tab allows for the maintenance of planned and actual efforts for Blueprinting and Realization

SAP 2010 / Page 50

Reports as a central Management Tool

As keywords indicate the Sprint and Release Cycles, Solution Manager allows for a simple tracking of cycle status, including work effort Therefore, Solar_Eval as a reporting tool may be leveraged for Product Backlog Sprint scope control Management of RICEFW list (add key word is needed)

SAP 2010 / Page 51

Thank you!

Contact
For accelerated implementations, it is recommended to facilitate one of our Agile coaches, please contact Jan Musil Klaus Skov Kristensen Jens Broetzmann Raimar Hoeliner

Copyright 2010 SAP AG All Rights Reserved


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.