Agile Project Delivery Fundamentals by SAP

Agile Project Implementation Methodology

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2
© 2014 SAP AG. All rights reserved. 2
Key Take Aways
 Drive for better “Time to Value”; customers are looking for early confirmation that
requirements can be met.
 Best Practices and Rapid Deployment Solutions greatly shorten deployment of SAP
solutions.
 SAP offers a proven set of Acceleration Techniques and Deployment Strategies in
SAP Activate Methodology
 Agile has been used successfully in SAP projects of various sizes and solution scope
 Level of acceleration and approach need to be tailored to the customer’s situation,
requirements and culture

SHORTEN TIME TO VALUE
AND REDUCE COSTS
REDUCE RISKS, WHILE
MOVING FORWARD
Visibility
Incremental Approach
Better Engagement between
Business and IT
FLEXIBILITY AND CHOICE
Solution and Product Fit
Business Expectations Changed
On cloud On
premises
Mobile
Hybrid
Cost Time to Value
Cost Time to Value

The Basics of Agile Methods
ITERATIVE
Frequent Inspection & Adoption
PEOPLE CENTRIC
Trust, Self-organizing teams and
individuals
FOCUS
Team focuses on one thing at a
time until it’s done
CROSS-FUNCTIONAL TEAMS
Face to face communication
/ no silos
CONSTANT LEARNING
Better fail early to learn fast, and
improve
ADAPTIVE PLANNING
To hit a moving target

SAP Activate for managed cloud and on-premise [ASAP successor]
Jump-start project
with pre-assembled
solution
Identify & validate
delta requirements
and gaps
Build customer
solution in short,
time-boxed sprints
Safeguard build
and run with ICC**,
OCC** and MCC**
Prepare
Pre-
Assembly
Solution Scope
and Value
Determination
Initial Roadmap
and Approach
Explore
Delta
Design
Deploy
Technical and
System testing
Realize
Baseline Build
Sprint Execution
Solution Validation including
Gap Validation**
Prioritize Backlog
Release and
Sprint Plan
Integration Testing
Value Audits
Setup Operations
or OCC**
Organizational
and Production
Readiness
Cutover
Support after
Go-Live
Run
Operations
Control Center
Application
Lifecycle
Management
Value
Management
** Deliverables, milestones and activities are only applicable in SAP Premium Engagements.
Best Practices
that fit customer
scope

Agile Project Execution and Benefits
Prepare Realize
Explore Deploy Run
Sprints
1-3
Iterations / Demos
Demo
Support
Release Planning
Tests
Final
Prep.
Organizational
Readiness
Pre-built
system or
pre-
assembled
solution
Solution
Validation
Must
Should
Could
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
Would
4
5
1
8
2
7
3
4
2
2
4
3
3
6
4
5
Backlog
Priority [d]
WS A WS B
String
String
Sprints
4-6
Epic
Epic
Delta Design
Jump Start Buy In
Drive
Priorities
Visibility

Agile Project Delivery
Fundamentals

SCRUM Methodology – leading Agile approach
Sprint Backlog
Sprint Retrospective
Sprint Execution
Sprint Planning Meeting
Sprint Review Meeting
Scrum Process
Recurring Cycle
Design
Scope
Product
Backlog
Usable
Software

Agile Implementation Methodology
Business Value Focused Explore Phase
Evaluation
& Release
Planning
• Define & Analyze, Scope,
• Demo Standard SAP
Explore
Process WS and
Sol. Architecture
Demo
Checkpoint
Checkpoint
Checkpoint
Baseline Build
Product Backlog
Must
Should
Could
Would
Priority days
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
Key components of Scope
Validation
 Iterative Baseline Build
 Solution Demo
 Visualization
 Focus on Business Value
through-out
 Prioritized Product Backlog
 Lean documentation
templates

Fit/Gap Workshops Approach
1. Reference Value
 Provide Process, Value and
Strategic Context
 Set Boundaries
 Tie to Business Case, Value
Drivers
2. Validation of SAP
Solution
 Show and tell SAP
standard key design
elements
3. GAP Identification
 Identify gaps to Standard
 Log additional scope
items
5. Delta Design
 Update Business Models
and Process Design
 Solution Design and
Visualize
6. Verify & Accept
 Verify process & solution
design
 Drive Acceptance
4. Delta Scope
Prioritization
Workshop Type A
Solution Validation
Workshop Type B
Delta Design
7. Release &
Sprint Planning

Iterative, Incremental Realize Phase
Agile Release of working software
Business
Priority
Product Backlog
Must
Should
Could
Would
Priority days
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
Realize
… Explore
Iterations / Demos
Sign-Off
(Organization
readiness)
Sprint 1
Sprint 2
String Test
Unit
Unit
Epic / Scenario
Sprint 3
Sprint 4
String Test
Integration
Test
UAT
Unit
Unit
Epic / Scenario

Closer look at a Sprint / Iteration
2-4 weeks time box
2.1
Sprint
Planning
2.3 Sprint Execution
2.2 Daily Team Meeting
2.4
Sprint
Demo
2.5
Sprint
Retrospective
Design
Build
Test
Document
Delta Requirement A
Design
Build
Test
Document
Delta Requirement C
Design
Build
Test
Document
Delta Requirement B
Design
Build
Test
Document
Delta Requirement D

Prepare Explore Realize Deploy
SBX (Pre-Assembled) DEV DEV/QA QA QA QA PROD
Project Preparation
Completion
Business Solution Validation
Completion
Sprint 1 Solution Tested Start of Production
User
Acceptance
Testing
Testing Assessment
Project Testing
Strategy
Test
Plan
Unit
Testing
Epic (String)
Testing
Unit
Testing
Integration
Testing 1
Integration
Testing n
Finalize Testing
Tools & Installation
Data Migration Testing 1
Data
Migration
Testing n
Data
Migration
Testing n
Test Case Development
Test Team Mobilization &
Training
Regression Testing
Security Testing
Performance Testing
Project System
Environment
Project Milestone / Q-
Gates
Testing Work Packages
User Story Definition
Sprint n Epic
Testing Overview
Baseline Build

Scaling Agile
Agile is not only for small projects, is also scales for large programs on a
global level
Characteristics of larger teams
 Higher functional, technical and integration complexities and dependencies
 Higher integration demands
 Multiple stakeholder groups and conflicting interests in product features and design
 Cultural differences
 Distributed decision making processes
 Higher communication demands, geographically dispersed
 Higher needs for organizational adoption of Agile principles
 Planning and execution requires more coordination
 Sign off and review processes require input from dispersed team members
 Logistically more challenging, in particular across time zones and work environments

How to start scaling Agile teams
Guiding Principles Global Agile Programs
 Start with a small core team to setup project structure and identify initial product
back log
 Onboard team members gradually over time and identify leads and coaches as
scrum teams are build out
 Stick to the agile principles but replicate them in “scrum of scrums”
 Identify a core team to focus on planning activities
 Identify a dedicated integration team to focus on integration aspects including
architecture, functions, technology and organizational change management
 Leverage a hierarchical product backlog that has multiple product owners and is
decomposed into work stream backlogs
 As necessary start with a pilot project to demonstrate Agile success

Program
Product Backlog
Work Stream
Sprint Backlogs
(Scrum teams)
Work Stream
Product Backlogs
(Scrum teams)
Product Owners
Product Backlogs
Scrum of Scrum Backlog Development
• Feature A
• Feature B
• Feature C
• Feature D
• Feature E
• Feature A
• Feature E
• Feature F
• Feature G
• Feature F
• Feature H
• Feature I
• Feature J
• Feature A
• Feature B
• Feature C
• Feature D
• Feature E
• Feature F
• Feature G
• Feature I
• Feature H
• Feature J
Finance
• Feature A1 (Org.)
• Feature B
• Feature C
Manufacturing
• Feature A3
• Feature F
• Feature G
Procurement
• Feature A4
• Feature H
• Feature I
• Feature J
Priorities
Priorities
Priorities
Priorities
Sales and
Distribution
• Feature A2
• Feature D
• Feature E
• Sprint 0 (A)
• Sprint 1 (B1)
• Sprint 2 (B2)
• Sprint 3 (C)
• Sprint 0 (A3)
• Sprint 1 (F)
• Sprint 2 (G1)
• Sprint 3 (G2)
• Sprint 0 (A4)
• Sprint 1 (H)
• Sprint 2 (I)
• Sprint 3 (J)
• Sprint 0 (A2)
• Sprint 1 (D)
• Sprint 2 (E1)
• Sprint 3 (E2)

Scaling Agile – Product Ownership Complexities
Chief
Product
Owner
Finance
Process
Owner
Planning
Experts
Assets
Manage
ment
Sales
Process
Owner
Manufac
turing
Owner
Procure
ment
Owner
 Product ownership can be complex in
large organizations.
 Establish product ownership hierarchy
to involve all key stakeholders in the
right stages of the project.
 Align the SCRUM teams with the
product owners for maximum impact.

Sprint Planning and Execution
Sprint Planning
 Add Sprint Zero for Product Backlog, Release
Plan, Infrastructure and Organizational
Structure Setup
 Develop common themes for sprints
 Align product development across sprints
based on dependencies
 Pay attention to common master and
organizational structures
Sprint Execution
 Add Integration sprints for integrated
functions
 Coordinate master and transactional data
needs
 Work with aligned cross functional story lines
Working Software
Product Backlog
Must
Should
Could
Would
Priority days
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
Sprint 1
Sprint 2
Integration
Sprint
Epic
Sprint 3
Sprint 4
Integration
Sprint
Epic
Unit
Sprint 0
Workstream 1 Finance
Workstream 2 Sales and Distribution
Workstream 3 Manufacturing
Workstream 4 Procurement

Scrum of
Scrums 2
Agile Project Governance
Work Stream /
Scrum Team 1
e.g. Finance
Work Stream /
Scrum Team 2
Sales and Distribution
Work Stream /
Scrum Team 3
Manufacturing Core Team,
Project Manager,
Chief Product Owner,
Chief Architect,
Agile Coach
Work Stream /
Scrum Team 4
Procurement
Scrum of
Scrums 1-n
Core Team
Focus on program
leadership, backlog
management, planning
and decision making,
guiding principles
Scrum Master (s)
responsible for consistent scrum
execution and standards,
1 for 3 scrum teams
Focus on integration topics and
cohesive solution build,
Consists of the lead consultants and
product owners from the individual
scrum teams
Agile Coach
Guides through the
execution of the overall
Agile program
Executive Steering
Committee
Strategically directs project

Working with parallel Scrum teams
Finance
Sales and
Distribution
Manufacturing
Procurement
Agile
Coach
Project Manager
Chief Product Owner
Scrum Master
Product Owner
Scrum Master
Product Owner
Scrum Master
Product Owner
Scrum Master
Product Owner
Solution Architect
Weekly or
Biweekly
Product Owner
Meeting
PM Review
(Daily)
Technical
Scrum of Scrums
(Weekly or
biweekly)
 Regular cadence of
meetings between
SCRUM Masters of
all SCRUM teams
 Goal is to coordinate
and align work;
highlight
dependencies;
discuss cross-topics
 SCRUM Masters
have responsibility to
debrief their
respective teams on
the results

Typical Deliverables per phase

SAP Activate for on-premise [ASAP successor]
Jump-start project
with pre-assembled
solution
Identify & validate
delta requirements
and gaps
Build customer
solution in short,
time-boxed sprints
Safeguard build
and run with ICC**,
OCC** and MCC**
Prepare
Pre-
Assembly
Solution Scope
and Value
Determination
Initial Roadmap
and Approach
Explore
Delta
Design
Deploy
Technical and
System testing
Realize
Baseline Build
Sprint Execution
Solution Validation including
Gap Validation**
Prioritize Backlog
Release and
Sprint Plan
Integration Testing
Value Audits
Setup Operations
or OCC**
Organizational
and
Production
Readiness
Cutover
Support after
Go-Live
Run
Operations
Control Center
Application
Lifecycle
Management
Value
Management
** Deliverables, milestones and activities are only applicable in SAP Premium Engagements.
Best Practices
that fit customer
scope

Prepare Phase Typical Deliverables
Engagement Model
Project Organization
Project Charter
Kick-Off Workshop
Scope Statement
Project Governance
Project Schedule and
Budget
Project Management Plan
Project Management
Plans
Project and Organizational
Standards
Execution Standards for
Agile
ICC/MCC standards in
Premium Engagements
Project Standards and
Policies
Organizational Change
Management Roadmap
Project Training Strategy
and Plan (team + key-users)
OCM and Training
Strategy
Project Team Training
Ramp up on methodology,
engagement model,
deliverables, SOW,
planning, etc.
Team Onboarding
Project Support Tools and
System Setup
Project Room
Facilities Access and
Security
Project Team
Infrastructure
Value Determination
Capability Business /
Process Needs Mapping
Solution Scope and Value
Determination
Technical Requirements
and Design
Initial Hardware Sizing
Proposal
Technical Infrastructure
and Sizing
Data Readiness Analysis
Data Migration Approach
and Strategy
Data Migration Approach
and Strategy
Determine Baseline Solution
A) Pre-Assembly per RDS
or Best Practice
B) Model Company Setup
C) Prototyping
D) Story Map / User Stories
Baseline Solution

Explore Phase: Typical Deliverables
Phase Initiation
Execution
Monitoring and Controlling
Results
PM Execution,
Management and
Controlling Results
Stakeholder Analysis
Change Impact Analysis
Communication Plan
Change Impact Analysis
and Communication
If no SAP Standard Solution
(RDS) available to address
customer needs
Prioritize features
Baseline Build Plan
Baseline Build
Sign-Off
Baseline Build
Set expectations on Scope
of Modifications
Solution Validation
(Workshop Type A)
Backlog build (translate
features in functions)
Parking lot items identified
Value Realization
Solution Validation
Prioritize Backlog based on
business value drivers
Identify Delta scope items
for current release
Gap Validation via ICC (PE)
Backlog Prioritization
Solution Design for Deltas
(Workshop type B)
Develop BPDs and
Functional Specifications
Sign of design documents
Design for Gaps and
Deltas
Legacy Data Migration
Legacy Data Archive
Design and Plan
Technical Solution Design
User Access and Security
Development Environment
Technology Design and
Setup of DEV environment
Testing Strategy
Test Strategy and Plan
Estimate Backlog items
Plan release executions
Allocate all backlog items to
sprints
Consider technical and
business dependencies and
sequences
Release and Sprint Plan

Realize Phase: Typical Deliverables
Phase Initiation
Execution
Results
PM Execution,
Management and
Controlling Results
Organizational Alignment
Knowledge Transfer / Train
Key Users
End User Training Delivery
Enabled
Organizational Alignment
and User Enablement
Quality Assurance
Environment (QAS) / Switch
to QA
Production Environment
(PRD)
Security and Authorizations
setup
Technology Setup for
QAS and PRD
Sprint Planning
Sprint Execution (Build and
Unit Test)
Sprint Demo
Sprint Retrospective
Firm-up Sprints (Transports
+ String Testing + Solution
Documentation completion)
Sprint Execution
Scenario Tests
Approved Integration Test
(Iterative)
Approved User Acceptance
Test - Test Solution
System and Performance
Test
Integrated Solution and
Non-Functional Testing
SAP Data Archiving
Value Audits
Value Audits
SAP Going Live Check
System User Roles and
Authorization Administration
Technical Operations and
Handover Plan
Technical Operations
Setup Plan including OCC
Preliminary Cutover plan
Cutover and Transition
Plan

Deploy Phase: Typical Deliverables
Phase Initiation
Execution
Results
PM Execution,
Management and
Controlling Results
Pre Go-Live End-User
Training Delivery / Validate
End User training material
Organizational and
Production Support
Readiness Check
System and Performance
Test
Approved Technical System
Tests
Technical and System
Testing
Project Team validates the
integration of the customer’s
IT solution with non-
functional tests
(performance-data
consistency check), and
prepares and implements
Run SAP Like a Factory,
Setup Operational
Support including OCC
Includes organizational and
technical readiness
Readiness for Cutover
Check
Project team will execute
the cutover to the
production software and go
live
Cutover to Production
Operations Control Center
or customer’s operations
team will take over the
solution.
Production Support after
Go Live

Key Take Aways
 Drive for better “Time to Value”; customers are looking for early confirmation that
requirements can be met.
 Best Practices, Rapid Deployment Solutions and Model Company greatly shorten
deployment of SAP solutions.
 SAP offers a proven set of Acceleration Techniques and Deployment Strategies in
Implementation Methodology
 Agile has been used successfully in SAP projects of various sizes and solution scope
 Level of acceleration and approach need to be tailored to the customer’s situation,
requirements and culture

Agile Project Delivery Fundamentals by SAP

Recommended

Recommended

More Related Content

Similar to Agile Project Delivery Fundamentals by SAP

Similar to Agile Project Delivery Fundamentals by SAP (20)

Recently uploaded

Recently uploaded (20)

Agile Project Delivery Fundamentals by SAP