Agile Lean BB

54
ASAP 7 Business Add On for Agile Implementations Agile Business Blueprint

Transcript of Agile Lean BB

Page 1: Agile Lean BB

ASAP 7 Business Add On for Agile Implementations Agile Business Blueprint

Page 2: Agile Lean BB

Introduction

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

Agile Business Blueprint Approach

© SAP 2010 / Page 2

Page 3: Agile Lean BB

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

Page 4: Agile Lean BB

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

Page 5: Agile Lean BB

Our Customer Expectations are ChangingThese 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

Page 6: Agile Lean BB

Business Blueprint Approach

SAP’s 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

Blueprint Quality ReviewBlueprint Quality Review

© SAP 2010 / Page 6

Page 7: Agile Lean BB

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

Acceleration =Reduction of Friction [Organizational Readiness] Elimination of Re-Work

[Process Blueprint, PoC, Solution Demo, Iterations]Parallelization [Productized Services]

Smallest possible increments (projects) along a value based roadmap (strategy)

IP Re-Use[Processes &Industry Solutions]

Managing the speed of value becomes a competitive advantage for SAP

x x

Legend:

IP – Intellectual Property

POC – Proof of Concept

© SAP 2010 / Page 7

Page 8: Agile Lean BB

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)

Parallelization of Services Integrated Service Delivery Value Prototyping Rapid Deployment Solution

Iterative Build Value Based Roadmap and Product Strategy [Program] Incremental build and test cycles [Project] Frequent Q-Gates - Time boxed and inspected increments [Project]

Co

mp

lem

enta

ry T

ech

niq

ues

© SAP 2010 / Page 8

Page 9: Agile Lean BB

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

Page 10: Agile Lean BB

BLUEPRINT COMPONENTSAgile Business Blueprint

© SAP 2010 / Page 10

Page 11: Agile Lean BB

Data ManagementData Management

RunRun

Organizational Change MangementOrganizational Change Mangement

Hybrid Agile ASAP 7 Acceleration Add-On

WorkingSoftware

Release 1

Project Backlog

Sprint Sprint

Sprint Sprint

Sprint Sprint

Time

Evaluate

16151413121110090807060504030201

SupportSupportITITFinal Prep.Final Prep.

Prep.Prep. Sprint Sprint

Sprint Sprint

Release 2

SprintSprint

4518273422433645

Rank Eff.

AcceleratorsAccelerators

EnablementEnablement

Realization Release 2Realization Release 2

PrepPrep Realization Release 1Realization Release 1Business BlueprintBusiness Blueprint Final PrepFinal Prep Go-LiveGo-Live RunRun

© SAP 2010 / Page 11

Page 12: Agile Lean BB

Agile Business Blueprint

DeliverablesPurpose

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

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

Process and Solution Design Business Process Hierarchy and

Design Value Association on Process

Level Solution Design Gap Identification and Resolution Solution Landscape and

Architecture Scoping - Plan for Sprint cycles Baseline Build Project Backlog

Milestones & Key Decisions

Completed and signed off Process Design

Completed and signed off Solution Design

Delta List Phase Quality Assessment Communication Plan Final Backlog – prioritized Sprint Definition

© SAP 2010 / Page 12

Page 13: Agile Lean BB

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 pre-configured 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

Page 14: Agile Lean BB

Agile Business BlueprintProcess Workshop and Solution Architecture

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

Deliverables■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

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

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

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

Page 15: Agile Lean BB

Agile Business Scooping

© SAP 2010 / Page 15

Page 16: Agile Lean BB

Agile Business BlueprintProcess Workshop

Business Process Agility Workshop

Business Process Agility Workshop

Executive Alignment WorkshopExecutive Alignment Workshop

Input Output

Engagement Proposal and Statement of WorkEngagement Proposal and Statement of Work

Process Workflow SAP MatchProcess Workflow SAP Match

Initial Project BacklogInitial Project Backlog

Issue listIssue list

Customer deliverables listCustomer deliverables list

Business Process Reference Content/ Map = Scope

Business Process Reference Content/ Map = Scope

Solution Demo Accelerators: SAP Best Practices / IDES / RDS

Solution Demo Accelerators: SAP Best Practices / IDES / RDS

Business RequirementsBusiness RequirementsProcess Value DeterminationProcess Value Determination

Roles and Responsibilities SAP/CustomerRoles and Responsibilities SAP/Customer Sign off Baseline scopeSign off Baseline scope

Authorization ConceptAuthorization Concept

Main Objectives

1. Demo SAP Standard2. Buy-In for SAP Standard/Best Practices3. Verify Processes and Scope

© SAP 2010 / Page 16

Page 17: Agile Lean BB

Business BlueprintBusiness 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

Page 18: Agile Lean BB

Agile Business Blueprint Baseline Build

Activities■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

Deliverables■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

Accelerators■Templates:

■ Customizing documentation■ Cross functional documentation■ Security documentation■ Lean Blueprint documentation

■Other:■ SAP Modelling Handbook

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

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

© SAP 2010 / Page 18

Page 19: Agile Lean BB

Business Blueprint Baseline Build

Detailed planning

Detailed planning

Realize Baseline Process

-(Standard SAP)

Documentation, continuously

updated

Realize Baseline Process

-(Standard SAP)

Documentation, continuously

updated

Checkpoint Checkpoint

Realize Baseline Process

(Standard SAP)

Documentation, continuously

updated

Realize Baseline Process

(Standard SAP)

Documentation, continuously

updated

Realize Baseline Process

(Standard SAP)

Documentation, continuously

updated

Realize Baseline Process

(Standard SAP)

Documentation, continuously

updated

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

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

Demo& Baseline evaluation

Demo& Baseline evaluation

Qualify new requirements

Baseline review

Qualify new requirements

Baseline review

© SAP 2010 / Page 19

Page 20: Agile Lean BB

Agile Business BlueprintBaseline Build Check Point / Solution Demo

Baseline Build Checkpoint

(Solution Demo)

Baseline Build Checkpoint

(Solution Demo)

Solution DemoSolution Demo

Input Output

Solution/Process realized so farSolution/Process realized so far

Initial Project Backlog (Product Backlog)Initial Project Backlog (Product Backlog)

SAP Standard / Best Practices / RDS Documentation

SAP Standard / Best Practices / RDS Documentation

Process and Solution Documentation

Process and Solution Documentation

Updated Project Backlog (Product Backlog)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

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

Page 21: Agile Lean BB

Business Blueprint PhaseBaseline Solution Demo

Activities■Baseline evaluation workshop (Fit/Gap Analysis)

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

■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

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

© SAP 2010 / Page 21

Page 22: Agile Lean BB

Agile Business BlueprintBaseline Evaluation – Solution Demo

Solution DemoSolution Demo

Baseline SolutionBaseline Solution

Input Output

Baseline SolutionBaseline Solution

Process DocumentationProcess Documentation

Solution DocumentationSolution Documentation

Updated and approved Baseline Solution Documentation

Updated and approved Baseline Solution Documentation

Revised and approved Process documentationRevised and approved Process documentation

Approved Requirements in Project Backlog

Approved Requirements in Project BacklogBusiness RequirementsBusiness Requirements

Approved by

CustomerApproved by

Customer

© SAP 2010 / Page 22

Page 23: Agile Lean BB

Solution Demo ApproachRefer to ASAP 7 WBS 2.5.1 Blueprint Approach

Visualize, Engage, Stay Focused!

Visualize solution to Improve collaboration and mutual

understanding Mitigate risk to rework Allow for early buy in and incremental

acceptance

Iterative Approach to Process and Solution Design driven by process de-composition

© SAP 2010 / Page 23

Page 24: Agile Lean BB

Solution Demo Approach

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 (KPI’s / PPI’s) Set the stage for Scope Management

Prerequisite: Knowledge transfer from CVR or Pre-Sales

Reference

Tool Set

Business Process Library / Customer Process Innovation CPI

Collaborative Value Realization Results

© SAP 2010 / Page 24

Page 25: Agile Lean BB

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

Tool Set: Show and Trial Solutions / IDES for SAP Standard iRise to visualize development objects and

end to end walk through sessions

© SAP 2010 / Page 25

Page 26: Agile Lean BB

Solution Demo Approach

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 [KPI’s / PPI’s] Close the loop to the Business Case Challenge to drive improvement/change

Listen and Complement Models

Tool Set: SolMan - Business Process Hierarchy /

Graphics Visio / ARIS, as applicable SAP Modeling Handbook

© SAP 2010 / Page 26

Page 27: Agile Lean BB

Solution Demo Approach

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

Document and Drive Acceptance

Tool Set: Solution Manager [SOLAR01] Upcoming pilot on Collaborative Blueprinting Road-shows and ASE-like workshops Visualizations of end-to-end walk through’s (e.g

with iRise)

© SAP 2010 / Page 27

Page 28: Agile Lean BB

Agile Business BlueprintEvaluation and Release Planning

Activities■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

Deliverables■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

Accelerators■Templates:

■ Sprint and Release plan■ Sprint Schedule

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

Main Objectives■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

Page 29: Agile Lean BB

Agile Business BlueprintEvaluation and Release Planning

Evaluation and Release PlanningEvaluation and

Release Planning

Prioritized and Signed Off Project Backlog and

Release Plan

Prioritized and Signed Off Project Backlog and

Release Plan

Input Output

Project BacklogProject Backlog

Process DocumentationProcess Documentation

Solution DocumentationSolution Documentation

Resource PlanningResource Planning

Story MapStory Map

Sprint ScheduleSprint ScheduleBusiness RequirementsBusiness Requirements

Estimate for remaining phases, as applicable

Estimate for remaining phases, as applicable

Approved by

CustomerApproved by

Customer

© SAP 2010 / Page 29

Page 30: Agile Lean BB

KEY DELIVERABLESAgile Business Blueprint

© SAP 2010 / Page 30

Page 31: Agile Lean BB

Lean Blueprint Deliverables

Approach Minimalistic Solution Manager Based

Fit Suited for implementations without Solution Manager

Suited for implementation leveraging Solution Manager as a repository for the solution build

Considerations Limited number of authorsManual document management required

Goal to leverage life cycle functionality of Solution ManagementComprehensive approach to manage the solution

Accelerated Implementation – Lean Blueprint Template.xls

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

© SAP 2010 / Page 31

Page 32: Agile Lean BB

Lean Blueprint Approach and Key Deliverables

A Blueprint is defined through a body of documents A Blueprint is defined through a body of documents

Business ScenarioBusiness Scenario

Business ProcessBusiness Process

Business process

step

Business process

step

Activity/Transactio

n

Activity/Transactio

n

Business Area/ Process Group

Business Process or Variant

(Transaction e.g. VA01 )

(Data entry e.g. customer name)

Lean Blueprint Template: Organizational Structure Req.

& Design

Lean Blueprint Template: Organizational Structure Req.

& Design

Lean Blueprint Template: Business Process Map /

Scenario Overview

Lean Blueprint Template: Business Process Map /

Scenario Overview

Lean Blueprint Template:Business Process Design

Lean Blueprint Template:Cross Functional Business

Objects

Lean Blueprint Template:WRICEF list incl. Functional

Specifications

Technical Solution DocASAP 7 Core

Lean Blueprint Template: Cross Functional Business

Objects

Lean Blueprint Template: Cross Functional Business

Objects

Business ProcessFlow diagrams

Optional in SolMan

ProjectProjectLean Blueprint Template:

Scope Key Decisions

Lean Blueprint Template: Scope Key Decisions

Value Maps - Optional

* Guideline documents to facilitate Blueprinting * Guideline documents to facilitate Blueprinting

Lean Blueprint Approach Guide*

Solution Manager Process Decomposition

Solution Manager Process Decomposition

SAP Modeling Handbook*

© SAP 2010 / Page 32

Page 33: Agile Lean BB

Key Decision Document - Lean

Document Focus Capture decisions that impact scope and/or solution

Expected Outcome Update in key decision log Key decision to be reviewed and signed of by project management office One line per key decision If applicable, key decisions are associated to process hierarchy

Document Ownership Project Sponsor

Completion Considerations Understand the decision to be made Discuss potential solutions / options

– Pros– Cons– Cost impact

Capture accepted solution / decision Capture approval of document

Optional Core Document Scope and Key decision template

SolMan Destination: Project Level

© SAP 2010 / Page 33

Page 34: Agile Lean BB

Issue Log Document - Lean

Document Focus Capture issues that impact scope and/or solution

Expected Outcome Updated issue log One line per issue If applicable, key decisions are associated to process hierarchy

Document Ownership Project Sponsor

Completion Considerations Identification of issue Classification of issue Status management of issues Identification of owner Identification of action items / activities Identification of time frame for resolution Captured resolution

Optional Core Document Issue List

SolMan Destination: Project Level

© SAP 2010 / Page 34

Page 35: Agile Lean BB

Business Scenario Design - Lean

Document Focus Focus is on define the scenario and associated processes and

understanding business objectives and drivers

Expected Outcome Update Business Scenario Overview, graphically

Document Ownership Process Owner

Completion Considerations Identify all processes that are part of the scenario Identify Ownership List Improvement Opportunities and Pain Points Identify associated KPI’s Business Process Hierarchy build out in Solution Manager

Optional Core Document Business Scenario Design Document

SolMan Destination: Scenario Level

© SAP 2010 / Page 35

Page 36: Agile Lean BB

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

Expected Outcome Updated process description Note: this document can replace process flows and the business process

document

Document Ownership Process Owner

Completion Considerations Identify process ownership Identify all processes steps Associate requirements / delta list Identify gaps (standard SAP vs. development) Identify associated KPI’s / PPI’s Business Process Hierarchy build out in Solution Manager Updated Backlog

Optional Core Document Business Process Design Document Business Process Flows

SolMan Destination: Process / process step level

© SAP 2010 / Page 36

Page 37: Agile Lean BB

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

Expected Outcome Updated delta list

Document Ownership Process Owner

Completion Considerations Identification of SAP gaps Association with SAP business process Priorization of log items Association with Sprint cycle

Optional Core Document Business Process Requirements Document

SolMan Destination: Process / process step level

© SAP 2010 / Page 37

Page 38: Agile Lean BB

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

Expected Outcome Updated WRICEF list

Document Ownership Process Owner

Completion Considerations 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

Optional Core Document WRICEF list Functional specification

SolMan Destination: Process / process step level WRICEF structure node

© SAP 2010 / Page 38

Page 39: Agile Lean BB

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

Expected Outcome Updated Cross Functional Bus. Object document

Document Ownership Process Owner

Completion Considerations Identification of all cross functional business objects Identification of Ownership Capture attributes for each object type Determine gaps and delta lists items

Optional Core Document Master Data Design Documents Organization Structure Design Documents

SolMan Destination: Scenario / Process level

© SAP 2010 / Page 39

Page 40: Agile Lean BB

Organizational Hierarchy - Lean

Document Focus Capturing SAP Organizational Hierarchies Translation of business view to SAP hierarchy view

Expected Outcome Updated Business Process Hierarchies

Document Ownership Process Owner

Completion Considerations Identification all organization hierarchies Identification of hierarchy elements Integrated functional views

Optional Core Document Organization Structure Design Documents

SolMan Destination: Scenario / Process level

© SAP 2010 / Page 40

Page 41: Agile Lean BB

User Role Concept - Lean

Document Focus Identification of User roles per process

Expected Outcome Updated user role concept as a basis for the authorization and OCM

concepts

Document Ownership Process Owner

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

Optional Core Document Organization Structure Design Documents

SolMan Destination: Scenario / Process level

© SAP 2010 / Page 41

Page 42: Agile Lean BB

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

Page 43: Agile Lean BB

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

Page 44: Agile Lean BB

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

Page 45: Agile Lean BB

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

Page 46: Agile Lean BB

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

Optional graphical modelling 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

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

© SAP 2010 / Page 46

Page 47: Agile Lean BB

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

Page 48: Agile Lean BB

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

Page 49: Agile Lean BB

Test Case Association

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

© SAP 2010 / Page 49

Page 50: Agile Lean BB

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

Page 51: Agile Lean BB

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

Page 52: Agile Lean BB

Thank you!

Page 53: Agile Lean BB

ContactFor accelerated implementations, it is recommended to facilitate one of our Agile coaches, please contact

Jan MusilKlaus Skov KristensenJens BroetzmannRaimar Hoeliner

Page 54: Agile Lean BB

Copyright 2010 SAP AGAll 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.