Professional Documents
Culture Documents
PowerSession-SAFe SAP SolMan and A4SFundementals
PowerSession-SAFe SAP SolMan and A4SFundementals
Agile /4 SAP
60
min
10
min 1. Agile /4 SAP
40
min 2. SAFe SAP Solman
10
min 3. QA
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 2
• SAP BUSINESS AGILITY
3
SAP BUSINESS AGILITY
Agile /4 SAP
INNOVATION & THOUGHT LEADERSHIP
ROADMAP
European & Global SAFe Summit Main Speaker Accredited AGILE /4 SAP Fundamentals
• May and October 2019 Next Public Training:
• Best in class participant feedback • November 2019
• 2000+ People attending • For registrations reach out to
Accelerate Benefits of ERP With First Steps in Applying Agile & Agile4SAPmax@accenture.com
Enterprise Agile DevOps to ERP Support
Published: 21 February 2019 Published: 18 February 2019
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 4
SAP BUSINESS AGILITY Coaching
Agile /4 SAP Advisory
PROVEN SUCCESS PATTERN FOR ACCELERATED OUTCOMES Assessment
Training
Leadership decision to start the journey
3
1 2 SAFe Value Stream Discovery
and Workshop Preparations
4
Go
Executive Agile /4 SAP Leading Phase 1: SAFe Value Phase 2:
Workshop Fundamentals SAFe SAFe DevOps
SAFe Knowledge & Strategy Alignment Stream Workshop LAUNCH
SAP
Identify the value streams and Agree on an incremental plan to Establish guiding coalition for Execute
understand their flow through the develop organization and ensure change. The Lean-agile center of Implementation
organization PI planning readiness excellence Plan
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 5
SAP BUSINESS AGILITY Coaching
Agile /4 SAP Advisory
PROVEN SUCCESS PATTERN FOR ACCELERATED OUTCOMES Assessment
Training
1
Agile /4
SAP
Fundamentals
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 6
SAP BUSINESS AGILITY Coaching
Agile /4 SAP Advisory
SAFE® SAP SOLMAN Assessment
Training
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 7
INTRODUCTION
This document has been created to document our Point of View regarding working
SAP efforts using agility under the Scaled Agile Framework
Contents:
1. Feature Refinement and Elaboration Process
2. Mapping work structure between SAP and SAFe
3. Refinement > Build > Test process … using Solman and Focused Build
4. Documentation process
5. Roles and responsibilities
Refinement
Integrated
Business
Process Refinement Best Practices
1. Product Managers facilitate Feature
refinement sessions
Refinement
Elaboration
Elaboration
Refinement
Integrated Epic
Business Process
(L3’s) informs…
May be delivered
ERP Capability
via a WRICEF
or Config
ARTs Feature
Phases Key:
Copyright © 2019 Accenture All rights reserved.
Workshops > Program Increments > 16
Iterations > Validation activities
WORKSHOPS > REQUIREMENTS > WORK PACKAGES
Workshops
Gap
Requirements
511R
Create
DSO
Feature
Delivery Object > IWM (goods issue) > STM (shipping) > DLMS (material receipt ack from customer)
• Cancel: (869C) …
• Status: …
• Reporting: …
• Modification: (511M) …
• Follow-up: (869A/869F) …
Other Capabilities TBD
Capability String
511R 511R
Feature
Store associated Fulfill DLMS Fulfill DLMS Fulfill DLMS Identify DLMS Identify DLMS Fulfill DLMS Fulfill DLMS
Contract Number requisition per requisitions per requisition by order types and order types and requisitions by requisitions by
User Story
on WBS element DLMS Advice DLMS NSN IS&G reporting status store/display store/display splitting customer updating ESD
Code rules rules against Original associated DLMS associated DLMS requested and Status Code
Document order details on order details on quantity based after availability
Number and screen screen on full/partial checks and
Suffix Code (SO inventory delivery creation
and Line) availability and
generating
unique Suffix
Code
Phases Key:
Copyright © 2019 Accenture All rights reserved.
Workshops > Program Increments > 20
Iterations > Validation activities
REFINEMENT > BUILD
> TEST PROCESS
21
SAFe REALIZES A
SET OF CONNECTED
KANBAN SYSTEMS Epic
Enabler Portfolio Kanban
VS Epic
Enabler
Capability
Solution Kanban
Enabler
Pr. Epic
Enabler
Feature
Program Kanban
Enabler
Story
Enabl.
Story
Team Kanban
Transitions Key:
= Manual
= Automated
Workshop A/B’s
COMPLETED DURING 12 WEEK PROGRAM INCREMENTS
Requirements Work Package Scoping D Scope To Be In Development To Be Tested Successfully D Handed Over
Created O Finalized Developed (FUT/UAT) Tested O To Release
(Funnel) R (Backlog) (Backlog) (Done) D (Accepted)
WIP limit Sub-tasks related to FUT
NC Work Item
STORY
Sub-task states:
B IP D
Backlog → In Process → Done
Copyright © 2019 Accenture All rights reserved. 24
DOR = Definition of Ready is entrance criteria to be prioritized in Backlog
DOD = Definition of Done is exit Criteria from Done to Accepted
FEATURE REFINEMENT
Create New Work Complete Scope
Define Scope
Package Analysis
D
Requirements Created Scoping O Scope Finalized To Be Developed In Development
R
Requirements in Draft form Area for Features that are Area for Features that are Area for Features that have Area for Features in which at Area for Features with
that are generated from based on one or more actively being defined and completed the Program level least one child User Story is at least one active
Workshop A’s and/or B’s enter Requirements generated from analyzed by the Product analysis, are in priority order, being prepared. child Work Items
the funnel. They are worked parent Capabilities. Manager. and are ready to be picked up (User Stories) in
for approval. for User Story decomposition. Required Fields: development
Description
Required Fields:
• TBD
• Requirements are Approved • PMO Project is identified • Description contains all • Wave (target PI) is defined • A subordinate Work Item
• Requirements are selected in • Requested Release Date is necessary details • An agile team has pulled the state is changed to In
a group to be assigned to a identified (D2/D3/etc. • Success Criteria identified Feature and assigned Development
new Work Package expected) including NFRs and Controls themselves as Development • All attached requirements
• TBD etc. • Product Manager has picked • High Level design is Team state(s) is/are changed to In
Criteria
Legend:
Copyright © 2019 Accenture All rights reserved. = Responsible and required ✓ = Required 26
± = Participates when necessary empty = not involved
USER STORY REFINEMENT
To Be Developed TD Ready to Review TD Released
D
Created Analysis & Refinement Team Refinement O To Be Developed In Development
R
Normal Change Work Items During this state, a limited During this state, the team These are Users Stories that User Stories that are
number of team members members who will build and are ready to be developed in a committed by the agile
Required Fields: (typically leads) review User test meet and review the User future Sprint. Only those team for Sprint and
• Development Team Stories with the Product Stories with the Product stories that are committed by have active work
• Developer
Owner. A New TD is created Owner. TD is put In Review the team should have a Sprint
Description
(business value)"
• Acceptance Criteria using review including agreement
the phrase "Given upon Acceptance Criteria
(conditions) -When (actions) • Define sub-tasks
- Then (expected results)“ • Product Owner will
• Complete detailed design determine Priority (ranked
order for Backlog)
Legend:
Copyright © 2019 Accenture All rights reserved. = Responsible and required ✓ = Required 28
± = Participates when necessary empty = not involved
IN-SPRINT WORK
D
In Development To Be Tested O Successfully Tested
D
User Stories that are User Stories that have been User Stories that the Product
committed by the agile team developed, configured, etc. but Owner has ”Accepted”.
for Sprint and have active work have not been Unit Tested.
Required Fields:
Required Fields: Required Fields: • TBD
Description
• TBD • TBD
State
Acceptance Criteria.
D
Handed Over
In Development To Be Tested Successfully Tested O
R to Release
Area for Features with at least Feature that has all child Work Features that have been Features that the Product
one active child Work Items Items in a Ready for Release completely developed and Manager has ”Accepted”.
(User Stories) in development state and are ready to be FUT. FUT. The team believes that it
has successfully met the Required Fields:
Required Fields: Required Fields: Success Criteria. • TBD
Description
• TBD • TBD
Required Fields:
State
• TBD
Legend:
Copyright © 2019 Accenture All rights reserved. = Responsible and required ✓ = Required 31
± = Participates when necessary empty = not involved
12-WEEK PROGRAM INCREMENT (PI)
Delivery 2
Delivery 3
Delivery Delivery Delivery IP
1 5 1
Iteration Iteration Iteration Iteration Iteration Sprint
PI Planning preparation
1 PI Planning 2 Sprint Planning 3 Story Demo 4 Feature Demo 5 Inspect & Adapt Workshop
FEATURE
Work Package
D D Handed Over
Requirements Work Package Scoping Scope To Be In To Be
Requirements Tested
Work PackageSuccessfully
Scoping HandedScope
Over To Be In To Be Tested Successfully
Created O Finalized Developed Development (FUT/UAT)
Created Tested To Release
Finalized Developed Development (FUT/UAT) Tested O To Release
R D
Features
D D Successfully
STORY
Work Item
Work Item Analysis + Team To Be In Development To Be Tested Handed Over
Created Refinement Refinement O Developed O Tested To Release
R D
User Stories
40
DESIGN PROCESS SPEC DOC
•1 Application Design Document (AD Document) or
Configuration Rationale Document (CRD) shell is
To Be Tested
Development
Handed Over
Successfully
To Release
Developed
and Functional Analyst in collaboration with
Work Package
Finalized
FEATURE
Scoping
Created
D D
Tested
Scope
To Be
appropriate representatives. ADD or CRD may be
In
O O
updated with additional business scenario and
R D
compliance considerations as “New Version”.*
•4 Detailed design is executed by team through
analysis and refinement of stories. ADD or CRD
should be updated with all decisions and linked to
Work Item as a Technical Design document.
•5 Story Definition of Ready: Acceptance criteria
defined and supporting artifacts must be referenced
(not attached) to Work Item.
4 5 6 7 •6 Updates to the ADD or CRD may continue as the
detailed design is “baked”.
To Be Tested
Development
Successfully
•7 Story Definition of Done: ADD or CRD must be
Refinement
Refinement
Developed
Analysis +
Work Item
Created
D D
Tested
Work Item
To Be
STORY
42
Permissions Key: Solman role
D D
Requirements Work Package WP Scoping O WP Scope WP To Be WP In To Be Tested Successfully O Handed Over
Work
Repair (as
needed)
Work Item
STORY
Developer
PO + Developer + PO + PO + Dev/Test +
Product Owner
Functional Analyst Dev/Test Developer Functional Analyst
Design / Refine Build / Test / Fix
Q&A
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 45
SAP BUSINESS AGILITY Coaching
Agile /4 SAP Advisory
In ASGR, we have the globally leading SAP Lean-Agile coaching capability Assessment
to help you on your journey to unlock BUSINESS AGILITY.
Training
Global Leading
SAP Agile
Academy 2018
700+ 1st
People Trained in Agile /4 SAP 9 weeks results
driven intensive
executive training
Copyright © 2019 Accenture. All rights reserved. NOT JUST A PROCESS OR METHODOLOGY, IT'S A MINDSET. 46