0% found this document useful (0 votes)

114 views134 pages

FB - Requirement Work Package and Item - L2 - SP06

FB_Requirement Work Package and Item_L2_SP06

Uploaded by

Alison Martins

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

114 views134 pages

FB - Requirement Work Package and Item - L2 - SP06

FB_Requirement Work Package and Item_L2_SP06

Uploaded by

Alison Martins

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Focused Build for SAP Solution Manager 7.

2 (SP6)
Requirement Management, Work Package and Work Item
Customer Experience & Solutions, SAP SE
June 2020

PUBLIC
Disclaimer

This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Content
Change Paces in Requirements-to-
Deploy

Requirements Management Work Items

§ Initial Requirement Backlog Planning § Sprint Backlog Planning
§ Requirements Upload § Create Work Items
§ Create Requirements § Work Items Workflow
§ Requirements Workflow
§ Work Items Document Management
§ Requirements Document Management
§ Work Items Reporting
§ Requirements Reporting
§ Work Packages and Work Items News
§ Requirements News with SP06
with SP06

Work Packages Additional Topics

§ Product Backlog Planning § Manage Changes in SFT and AT with
§ Create Work Packages Defect Corrections
§ Work Packages Workflow § Build the Release
§ Work Packages Document § Go-Live
Management
§ Work Packages Reporting
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Change Paces in Requirements-to-Deploy
Three Different Change Paces in Requirements-to-Deploy
S/4HANA Conversion Project Support provided with Focused
Build SP06 as additional starting point for Requirements-to-
Deploy

Portfolio to Project

Fix Innovate
Trigger Business disruption or Transformation projects,
standard change Trigger
accelerated by
Scope Small Fix Scope
new solutions
Large
Process Impact None
Process Impact Significant
Approval Individual

Innovate
Approval Pre-Approved
Deployment Unbundled on request or
bundled with release Deployment Bundled with release
Focused Build
Time to delivery 1 day – 1 week Time to delivery 3-12 months

accelerated by
Enhance Enhance
Trigger Improvement request
Scope Medium
Process Impact Minimal Focused Build
Approval Individual
Deployment Bundled with release
Time to delivery 1 month

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

SAP Solution Manager Integration Model
Process Flow

The Requirements-to-Deploy
value chain supports the
three different change paces No overhead.
at an optimum.

Demand Design Development Test Deploy

Program fix required Fix immediately, deliver break-fixes and

Fix to resolve disruption standard changes
As fast as needed.

Enhancement Assess enhancement

Bundled in
Enhance required for daily request, negotiate Deliver enhancement
minor release
business operations delivery and cost

Model to-be
Strategic initiative for Plan solution Deliver solution with continuous business Bundled in
Innovate new business model
processes, collect
delivery feedback major release
Requirements

Monitor Solution Readiness

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

SAP Solution Manager Integration Model
Focused Build Document Flow

Demand Design Development Test Deploy

FB Urgent Change Immediately after

Fix Incident FB Request for Change
approval
FB Standard Change

Business
Enhance Requirement
IT Requirement Change Document Minor releases

Work Package,
Innovate Requirement
Scope Change
Work Item Major releases

Solution Readiness Dashboard

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

SAP Solution Manager Integration Model
Transaction Types

Demand Design Development Test Deploy

Immediately after
Fix Incident S1CR S1HF / S1SG
approval

Enhance SMBR SMIR SMHF / SMMJ / SMGC / SMAD Minor releases

Innovate S1BR S1IT S1MJ / S1CG Major releases

Solution Readiness Dashboard

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

S/4 HANA Conversion Project Support
Integration Readiness Check in Focused Build

Focused Build
Focused Build
Project

SAP Focused Build

Requirement
Readiness Check
for SAP S/4 HANA
Focused Build
Excel Simplification Item Evaluation and Work Package
Export/Import Management UI5 App Categorization of
Activities

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Simplification Item Management UI5 Application
§ Graphical display of Simplification Items
and related Conversion Activities by
Condition, Phase, Type, Status and
Follow-Up Type

§ Table display with all Simplification Items

and related Conversion Activities and
their most-important information

§ Powerful and fast multi-filter options

§ Direct Creation of Follow-Up

Requirements or Work Packages and
Assignment of Focused Build Projects

§ Postponement or Rejection of non-

required activities directly possible from
the UI5 application

For more information see L2 presentation for S/4HANA Conversion Project Support
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Requirements Management
Initial Requirement Backlog Planning
Digital Business
Delivery Platform: The Big Picture

Discover & Prepare Explore Realize & Deploy Operate

One Content
Cloud

WBS & Q-Gates

Roadmaps Solution
Readiness
Readiness
Check
Dashboard

Business Process

SAP Best
Practices Work Monitor &
Requirements Packages Support

Trial System Solution Landscape

Cloud Appliance
Library Build
Factories

Innovation Control Center SAP Mission Control Center Operations Control Center

SAP S/4HANA Value Assurance Service Packages

Value Discovery
planning and safeguarding | technical implementation | function implementation | innovation

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Initial Backlog
Definition

A Release can be assigned to a:

§ Project -> more Waterfall approach
§ Wave -> more Agile approach

There must be an aligned and conscious decision how agile the project should be implemented and organized.
This is less a question of implementation tools, but how much a team and management(!) is able to change it’s
way of work .

An Initial Backlog in Focused Build means to have:

§ A list of approved and prioritized Requirements

§ Building the content of the to be implemented Release

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Build Design: Example New Implementation
Fit Gap Analysis and Delta Design – Methodology Overview
Step A Step B
Fit Gap Analysis / Solution Validation Delta Design
Repeat steps 5 & 6
1. Finalize System Setup Best Practices / at the beginning of
Model Companies each Wave 6. Verify & Accept
Prepare additional sample data To sign-off release
uploaded to SAP Verify solution design Functional Specification
Enhance system setup with add.
Scope
Solution Manager Acceptance Procedure in My Work Packages
app and set according
Workshops per Line of Business, Work Package Status
Extend Processes Fit Gap Workshop per
which are not part of Solution Capability, e.g. Create solution design: e.g. Sourcing and Procurement:
2. Fit Gap Workshops / Validation of - Slice the Requirements into Work - Present solution based on delta
Best Practices, [Link] operational procurement:
SAP Solution Packages which need to fit in one design
- Process / Steps
Show and tell SAP standard key - Solution / Function Wave - Capture open issues if required
design elements / Gap Identification - Roles - Document relevant configuration - Obtain sign off
- Frontend (Fiori vs. GUI) - Document solution for identified
Process Management gaps e.g. One Delta Design for
Solution Readiness Sourcing and Procurement 5. Delta Design
Dashboard 3. Gap Documentation
Document and specify identified Gaps 5.2 Design/Specify
in initial Backlog Specify the work to be done, e.g. For real Gaps and
Create Delta Design Documents WRICEF, create
Capture and classify identify Upload Configuration Documents Functional Specification
gaps in backlog: Prepare distribution of work by definition of in My Work Packages app
- Document Requirements Central review of identified gaps: Work Items
- Classification (process gap, - Completeness 4. Delta Scope
Rework
functional gap, etc) - Priorization Prioritization
Requirements via 5.1 Create Create Work Packages to be part of
- Initial solution proposal Prioritization
Requirement Product Backlog the first Wave
- Initial effort estimates according to
Management or with Requirement Management app
My Requirements
Verify Priority, Effort and agreed Prioritization
app
Value with Requirement criteria (e.g. according to
Repeat this Wave planning activity
Management app Business technical for each Wave -> agile
Value, criteria (e.g.
Approve Requirements to
be part of release, Criticality) Development Plan all Waves at once -> waterfall
sequence)
with Mass Change app Result: Product Backlog

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Fit Gap Analysis and Delta Design – Step 1
Prepare a Fit/Gap Workshop

Step A
Fit Gap Analysis / Solution Validation
Step 1: How to prepare a Fit/Gap Workshop with Focused Build?
1. Finalize System Setup Best Practices /
Prepare additional sample data Model Companies
uploaded to SAP FB Role: Business Analyst
Enhance system setup with add.
Solution Manager
Scope Functionality: Process Management
Extend Processes Procedure:
which are not part of
Best Practices, [Link]
§ Choose a Sandbox or On-Premise SAP Solution Manager System
§ Check predefined content offerings from SAP (SAP Best Practice or
Model Company content)
§ Choose and further prepare the business process(es) to be part of the
Fit/Gap analysis
§ In case it is in the knowledge of the consultant or there are already more
documents or process models available, extend and adjust the
predefined process diagrams

Advantage:
§ Accelerated set-up of Sandbox system

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

Create Work Package
Activate Best Practices with Focused Build

Step 1
Baseline build, as basis for Requirements creation in the Fit/Gap Workshops, shall be done on the Sandbox
system:
§ By default, it is not foreseen to maintain Requirements and Work Packages in Discover and Prepare
project phase
§ So, just activate the Best Practices via Solution Builder without explicit Focused Build specific reporting

Step 2
For the configuration of the Development system, it’s recommended to create one Requirement per Business
Process. There are several options dependent of the configuration complexity and duration:

§ Simple and quick configuration done in one Wave: 1 Requirement, 1 WP, 1 WI, 1 Transport
§ Simple but long lasting config. done in several Waves: 1 Requirement, X WPs , 1 WI, 1 Transport

§ Complex but quick config. done in one Wave: 1 Requirement,1 WP , X WIs, X Transports
§ Complex and long lasting config. done in several Waves: 1 Requirement, X WPs ,X WIs, X Transports

The Work Packages which specify the Solution Builder activities are classified as FIT.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17
Release Planning: Roles and Responsibilities

7.2
Create
Requirement
based on
1. Define Product business process
Business Analyst
Responsibility

Backlog 7.2
Business

Use Value points,

effort and priority 7.2
High-Level
to rank Approve, Release Plan
2. Prioritize Product
postpone Based on Master Project
Backlog Requirements
5. What would you like in
the release?

[Link] of
Responsibility

Dependencies
Architect

7.2
Detailed
IT

Create Work Release Plan

[Link] Product Packages
based on Build Project
Backlog [Link] Release :
Build logical and technical
packages

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

Fit Gap Analysis and Delta Design – Step 2
Execute a Fit/Gap Workshop Step 2: How to execute a Fit / Gap Workshop?

FB Role: Business Analyst

Step A Functionality: Process Management
Fit Gap Analysis / Solution Validation
Naming: Gap in Activate is called Requirement in Focused Build
Procedure:
1. Finalize System Setup Best Practices /
Prepare additional sample data Model Companies § Logon to SAP Solution Manager and review the business process
uploaded to SAP (either in Process Structure or Diagram)
Enhance system setup with add.
Solution Manager
Scope
§ Maintain Requirements (= Gaps in Activate)
Fit Gap Workshop per - Document Requirements in SAP Solution Manager as draft in Process View or
2. Fit Gap Workshops / Validation of Solution Capability, e.g. Diagram. Requirements in FB are classified as Gap, WRICEF, Fit, Non-
operational procurement: functional)
SAP Solution
Show and tell SAP standard key
- Process / Steps
- Solution / Function
- Alternatively it is possible to document Requirements in xls or another system
design elements / Gap Identification - Roles e.g. from Model Company, and upload them to On-premise SAP Solution
- Frontend (Fiori vs. GUI) Manager system later
Process Management
Solution Readiness § Release Process to Development Branch (with the help of a Work
Dashboard Package and Work Item)

Reporting:
§ Solution Readiness Dashboard (Unassigned Requirements)
/Requirements Management

Advantage:
§ Efficient Fit-Gap Workshops: Requirements are linked/displayed to
Business Process enabling an efficient discussion and reducing the
duration of the workshops

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

Fit Gap Analysis and Delta Design – Step 3
Detailed Requirement Documentation
Step A
Fit Gap Analysis / Solution Validation
Step 3: How to do detailed Requirement documentation?
1. Finalize System Setup Best Practices /
Prepare additional sample data Model Companies
uploaded to SAP FB Role: Business Analyst
Enhance system setup with add.
Solution Manager
Scope Functionality: Requirement Management, My Requirements
Procedure:
2. Fit Gap Workshops / Validation of § After the Fit/Gap workshops, rework the Requirements in status ‘Draft’.
SAP Solution When ready, set the Requirement status ‘To be Approved’
Show and tell SAP standard key
design elements / Gap Identification § In case the Requirements have been documented in xls, or another
system, upload to On premise SAP Solution Manager. Assign the
Process Management
Solution Readiness Solution Documentation. Check and rework/precise the Requirements.
Dashboard 3. Gap Documentation When ready, set the Requirement status ‘To be Approved’
Document and specify identified Gaps
in initial Backlog
Advantage:
Capture and classify identify § Efficient communication between functional and technical experts:
gaps in backlog: Detailed Requirement description and business context helps the
- Document Requirements
- Classification (process gap, Architect and Development to better understand the Requirements
Rework
functional gap, etc)
Requirements via
- Initial solution proposal
Requirement
- Initial effort estimates
Management or
My Requirements
app

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Fit Gap Analysis and Delta Design – Step 4
Define Initial Backlog
Step A Step 4: How to define the Initial Backlog?
Fit Gap Analysis / Solution Validation
FB Role: Release/Project Manager, Architect
1. Finalize System Setup Best Practices / Functionality: Mass Change Operation
Prepare additional sample data Model Companies
Enhance system setup with add.
uploaded to SAP Procedure:
Scope
Solution Manager
§ Select Requirements in Status ‘To be Approved’
§ Sort Requirements according Priority, Value or Effort Points
2. Fit Gap Workshops / Validation of § Check and adapt the values
SAP Solution
§ Sign-off: Approve those Requirements to be part of the Release
Show and tell SAP standard key
design elements / Gap Identification § Postpone those Requirements to be part of the next Release
Process Management Reporting:
Solution Readiness
Dashboard 3. Gap Documentation
§ Solution Readiness Dashboard (Unassigned Requirements,
Document and specify identified Gaps
Requirements Management
in initial Backlog

Advantages:
§ Efficient prioritization via filter and sort functionality
Central review of identified gaps:
- Completeness 4. Delta Scope § Efficient approval process via mass change functionality
Rework
- Priorization Prioritization
Requirements via
Requirement Prioritization
Management or according to Note:
Verify Priority, Effort and
My Requirements
Value with Requirement
agreed
criteria (e.g.
§ In fix price/waterfall projects, the Initial Backlog is a fixed list of
app
Management app Business Requirements defining the complete content of a Release.
Approve Requirements to Value, So you need only one Release for the whole project and
be part of release, Criticality) you could plan the complete project already at this point in time
with Mass Change app
§ In agile projects, the Initial Backlog might change. So the Architects
check the Initial Backlog each wave again. They plan their product
backlog according the current prioritization.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC So typically you have a Release for each wave. 21
How to come to an Initial Backlog - Summary
Steps
Step 1: Requirements are gathered with the help of Fit-Gap Workshops
§ The creation of an Initial Backlog is a process which typically lasts several weeks or month
§ The Requirements definition process can vary very much, dependent of the SAP Partner and Implementation methodology

Step 2: Working with processes and process structures and diagrams

§ Best Practice is, to start with predefined SAP Content (Best Practice or Model Company) and directly maintain the Requirements in SAP Solution Manager.
The advantage is, that process structure elements are automatically assigned and all documents are automatically stored at the correct place
§ This data is then inherited by each follow-up document, e.g. the Work Packages and Items
§ Working with diagrams coming with the SAP Content and prepared by the SAP consultant beforehand the workshop accelerate the discussion
§ Alternatively it’s as well possible draw processes on brown paper and gather the Requirements in xls. When this is done you can bring the Requirements
with one upload in SAP Solution Manager. Then the process structures in Solution Documentation need to be maintained, optionally the process diagrams
redrawn, and after the Requirement upload, the process structure manually assigned to the Requirements.

Step 3: There is a slim approval workflow for the Requirements

§ During the Fit-Gap Workshops the Requirements are in Status ‘Draft’
§ When the Gap definition for a scenario or process is ready, the responsible Business Analyst sets the Requirement on status ‘To be Approved’

Step 4: The approval procedure for Requirements for each release is done by an Approval Board
§ This is commonly done via the Mass Change Analysis, where the ‘To Be Approved’ Requirements are collected and checked
§ Requirements which are not so urgent are put on status ‘Postponed’ and are re-checked at the next Approval Workshop for the next Release
§ The activity shall be executed by an Architect (having change authorization for the Mass Change) but under the participation of the program and project
managers

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

When to do plan the Initial Backlog

User Stories
Release Epics
User Stories
Content
Initial Backlog Product Backlog Sprint Backlog
Work Item

Require-
ments
Gap Work Packages
Gap, Functional
Prioritized/ Sprint planning
analysis & release Gap, WRICEF, Fit (config) Non Work Item
Fit / Gap Ranked, rough WRICEF, Fit
Planning functional Requirements (Which dev team,
effort estimation (only which order)
analysis configuration) (aggregation or
splitting)
WS Fit
Non functional
duplicates
Requirements
eliminated
Work Item

Time
Sprints
Release Waves Sprints

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

Agile Project Execution with Focused Build

Highlevel Release Detailed Release Detailed

Planning Planning Development
(Master Project) (Build Project) Planning (Wave)

Initial Backlog Product Backlog Sprint Backlog

Requirements Work Packages Work Items
Value Effort Value Effort Value Story

4 8 15 6 20 4
Low

Low

Low
2 10 18 2 5 3

Medium
Medium
Medium

14 7 1 1 4 9
Jump Maintain Support
Start Requirements 6 9 5 6 12 20

12 20
High
13 10 15 1 Wave 1

High
High

FIT/GAP WS 1 20 ARCHITECT 4 2 Development 2 10 DEVELOPER Optional:

Pre-built ANALYST Team

Demo/Test
Repeat Delta

Very High
Very High
Very High

system or 20 8 8 3 4 8 Sprints Design / Sprint

pre- Baseline Sprint 1-3
2 4 4 5 3 7 Planning
assembled Build Solution Delta Planning Meeting for
solution Validation Release Planning Design Wave Planning Meeting Sprint Planning Wave 2

Prepare Explore Realize Deploy Run

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

How to come to a Product Backlog and create Work Packages - Summary
Steps
The Creation of Work Packages is not an activity an Architect executes in one attempt, but in a phased approach:

Step 1: When the Requirements are approved for the first release, the Architects create the Work Packages
§ Create WPs for each Build Project, e.g. Purchase to Pay, Logistics, Controlling, Master Data, …
§ Doing that, they build the Product Backlog for the first or all Waves. So a WP should be developed in one Wave
§ Planning for the first Wave only means a more agile attempt as you are fully flexible for the next wave. Planning for all waves would be typical for a
classical waterfall approach

Step 2: When the Product Backlog Planning for the first Wave is done, the Functional Specifications or
Configuration Guides are created. Ideally, Test Cases or at least the Templates are assigned as well

Step 3: When the planned Development is clearly described in the Functional Specifications, the needed
development activity can be described and distributed. This is done by scoping Work Items for the
Developers

Step 4: Once the Planning activities are finalized, the Architect approves the Scope -> as a result the Work Package
is set to status ‘Scope finalized’
§ This activity can be done by an Architect in his single Work Packages
§ Or in form of an Approval Board Workshop with the help of the Mass Change Application

Step 5: When the Development starts all Work Packages are handed over to development
§ Like above this can be done by each Architect or commonly via the Mass Change Application
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25
Requirements Upload
Transparent Requirements-to-Deploy
Agile Delivery Model with distributed teams

Project Team Onsite

Process and Application

Landscape System Integrators

WRICEF/Gap Gap

Requirements Work Packages / Build Development

Work Items Factories Factories

Fit

Solution Readiness Dashboard Onsite Delivery

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 27

How to start - Methods for Requirement Maintenance or Upload
Overview

Process Management Diagram Process Management Column Browser

è Directly maintain Requirement at Business è Directly maintain Requirement at Library or
Processes or Business Process Steps process structure elements

Requirement
Management

Excel upload Excel down-/upload

è Initial upload of Requirements into Requirements è Initial down- and upload of process structures including
Management (manual assignment to Process Structure Requirements, e.g. from cloud or Model Company systems
Elements as follow-up activity needed)
Download from JIRA
è Initial download of Requirements from JIRA or other
external Requirements Mgmt. tool via API. incl. status update
when processing Requirements in Focused Build
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28
Down and Upload Requirements (since SP03)

Use Case 1 - Other SAP Solution Manager system as data source

Down and upload Requirements with Solution Documentation structure information, e.g. process, process
step, library

Use Case 2 - External data source

Upload without Solution Documentation structure information, e.g. process, process step, library

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

Use Case 1: Down and Upload Requirements from other SolMan

Applications
Requirements Mgmt., Excel
Feature
• Down and Upload Requirements from other
systems like Model Company or CALM
Use Case
The project preparation phase started on another
SolMan system, like a CALM or Model company.
There process structure and Requirements already
have been defined.
Now you can do an initial upload of the
Requirements to the design branch of the on-
premise SolMan with automated assignment to the
process structure.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

Use Case 2: Upload Requirements from External Data Source

Applications
Excel, Requirements Mgmt.
Feature
• Upload Requirements from other data sources
Use Case
The project preparation phase without another
SolMan system, e.g. xls-based or gathered in
documents.
You can do an initial upload of the Requirements
to Requirements Management app. of your SAP
Solution Manager.
Create the process structure/diagrams and assign
them to the Requirements.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 31

Create Requirements
How to start - Methods for Requirement Maintenance or Upload
Overview

Process Management Diagram Process Management Column Browser

è Directly maintain Requirement at Business è Directly maintain Requirement at Library or
Processes or Business Process Steps process structure elements

Requirement
Management

Excel upload Excel down-/upload

SAP Activate provides SAP S/4HANA best-practice process content that consists of process
diagrams, documentation, and configuration.

§ You can download this content into your SAP

Solution Manager
§ From the diagram, you can jump into SAP FIORI 1
apps in a pre-activated
SAP S/4HANA trial system
§ Execute show and tell of the SAP S/4HANA
innovations hands-on 4 2
§ Document Requirements as a result of this
fit/gap analysis

SAP S/4HANA
3 On-Premise Edition

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 34

Document Requirements
Adding Requirements

Best Practice is to add Requirements to process steps and processes, but they can also be
linked to other elements if required.

Requirements
Process

Processes

Requirements can be maintained at

the following SolDoc Elements:
• Structure Elements
Process Step Library
• Process
• Process Step (Reference)

• Library Elements
Executable Library
• Configuration Item
• Process Step (Original)
Configuration
Interface Library Development Library • Executable
Library
• Development
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC • Interface 35
What’s in Focused Build on top of SAP Solution Manager?
Explore Phase

Requirements Management

§ Create Requirements in Validation workshops

with customers for delta identification (Fit/Gap
analysis)
§ Requirements are integrated into process
context allowing better handover to build team
§ Multi-language support for Requirements
§ Tight integration of Requirements Mgmt. into
solution landscape, process models, Work
Packages, Work Items, Solution Documentation,
and the Solution Readiness Dashboard

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36

Document Requirements
Example: Maintain Requirement at a Process Step

Requirements can be assigned within the diagram editor or in the browser by selecting
the process step or other structure elements.

Link to
Requirements
Management app
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37
Document Requirements
Display of Requirements in Process Management

Requirements for Process Steps

Relationship from Requirements to processes in
Solution documentation
Feature details
• Indicate in the process if Requirements are available
• 4 different decorator icon shows the different status of Requirements
• Preview of Requirement in pop up window
• Direct access to all existing Requirements for the
process step to create further Requirements

Benefits
Monitor in the process structure how many
Requirements exist and which status.
Avoid creating redundant Requirements for the same
process.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 38

Requirement Classification

The outcomes of the EXPLORE workshops may initially be referred to as ‘Gaps’ or ‘Deltas’ from which we
create “Requirements” when using Focused Build with SAP Solution Manager.

Within Focused Build the Requirements are classified;

the follow-on Work Packages (WP) and Work Items (WI) are also classified.

The classification options are fixed (& not customizable).

The Classification of the Requirement is for Information only and to help define Work Packages
(and although defaulted to a WP can be changed when a Requirement is assigned to a Work Package).

Requirement
Meaning
Classification
Gap is a completely new development which needs to be specified in detail with significant ‘as-is /to-be’ evaluation, often with no technical information or idea how to realize it in
the beginning. Technical design is fully done by developer in WI with the help of a technical design document. (There will be few Requirements with this classification)

WRICEF is a typical and from SAP expected extension, where no business background needs to be described. The consultant often already knows how to implement and configure.
So the Specification is often already a mixture between functional and technical design

Fit (configuration) there is no coding adjustment, but only customizing.

So specification is often an existing standard configuration guide and only a customizing documentation is needed to be maintained on Work Item level

Non-Functional Is used for documentation upload or a parameter settings without the need to document a Functional Specification (no document KPI maintained in customizing for Work
Package and Work Item).
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 39
Requirement
Practical Tips

§ What is the right Requirements Granularity?

-> From a well defined Requirement you can directly create a Functional Specification or assign a
Configuration Guide

§ Define and discuss within project team how to use priority, category and other attributes across project
teams (!)

§ Decide on categories before starting Requirements gathering in order to simplify searching and filtering
(relevant for Mass Change, SRD); reuse them in WP and WI as well

§ Add meaningful names (naming convention starting with Process abbreviations) and description to
Requirements – especially when working on bigger teams!

§ If required also document Fit Requirements for holistic documentation, e.g. in config library
-> but define how this shall be handled otherwise the amount of Requirements is growing too fast

§ Define the Sign-off process (Requirements and Process Structure) together with the customer to avoid a
bottleneck at the beginning of the configuration/development activities
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 40
Requirements Workflow
Requirements Management Process Flow as of SP05
Detailed Workflow
= manual status setting
= automated status setting
Requirements

Send for Approval To Be Approve Completed

Draft Approved In Realization Realized
Approved (FINI)
Revise

Reject Create Create

WP Set WP Set
Create Set
WP by by by
Recover Set WP WP WP
Rejected
by
WP
Withdraw
Postpone Postpone
Canceled
Withdraw (FINI)

Withdraw

Recover
Postponed Set
by
WP

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 42

Requirements – Document Management
Basic functionality and usage overview

dropDoc Attachments in
Work Package and Work
Item Applications

dropDoc Attachments
integration to
Requirement Application

Note: Attachments are not stored in

Solution Documentation, but are copied into
the related Work Packages.
In Solution Administration and by customizing,
you can define Attachment templates to ensure
a standardized document use.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 44
Basic functionality and usage overview

§ UI5 technology
dropDoc Attachments
§ Mass upload of documents
in Work Package and
Work Item Applications § Access to document templates
§ Drag and Drop functionality

§ Integration into Requirement Application

dropDoc Attachments
§ Mass upload of documents into selected Requirement
integration to
§ Direct access to document templates
Requirement Application
§ Drag and Drop functionality

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 45

Requirements Reporting
Requirements Management
Applications
Requirements Management Application

Feature
• Main purpose is to create Requirements
and Work Packages
• It also allows to get an overview of
Requirements in a specific context, e.g.
Scope, Business Process, Owner etc.

Use Cases
• Filter & sort Requirements to do Release
planning based on Value and Effort Points
• Find Requirements without
Solution/Process Structure assignment
• Check Status of Requirements of a
selected Scope/Business Process
• Etc.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 47

Mass Change

Applications
Mass Change Application

Feature
Mass Change of selected
Requirements

Use Case
Select Requirements to do
collective changes, e.g.
approve them while a Release
planning Q-Gate

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 48

Solution Readiness Dashboard

Applications
Solution Readiness Dashboard

Feature
Predefined reporting based on
Requirement ID and Project

Use Case
Track unassigned Requirements
and Requirements assigned to
your Build Project

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 49

Solution Readiness Dashboard - Requirements Tile in Detail

Overview of all Requirements, either unassigned or assigned via Work

Package to Project. Each bar of the tile is clickable and offers a
filtered list of Requirements
Total Backlog means unassigned Requirements:
§ don't have Work Packages assigned to them or
§ are associated with Work Packages that aren't assigned to any project
§ have the detail status ‘Draft’, ‘To be Approved’ or ‘Approved’

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 50

Solution Readiness Dashboard - Requirements Tile in Detail

Requirements ‘To be scoped’

§ are associated with Work Packages from current Project which still need to
be scoped.
§ have the detail status ‘Approved’

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 51

Solution Readiness Dashboard
Example: Unassigned Requirements

Status overview
with aggregated
numbers

Detailed list view

with filter options

Navigation to each
single Requirement
for all details

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 52

Traceabilty Matrix

Applications
Test Suite Dashboard
Feature
• Predefined reporting based
on Project and Test Plan
Selection
• Starts with Project
• Includes Requirements,
Work Packages,
Work Items, Defect, Defect
Corrections and assigned
detailed information
Use Case
Traceability from Requirement
to Defect & Transport
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 53
Traceabilty Report

Applications
/SALM/Traceability_Report

Feature
• Report starting with
Requirement ID
• Offers all data like
Traceability Matrix
• Includes flexible selection
of additional data

Use Case
Enables customer specific
reporting via xls export

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 54

Key Takeaways Requirements Management
Workflow

Requirements
– Are created on the Design branch and not released to Development branch
– Should be related to any process structure in SAP Solution Manager
process management, process or non-process related
– Should be specific and granular
– Have an 1:m or n:1 relationship to Work Packages
– Are ideally consolidated (not x Requirements for the same need)
– Need to be approved
– Get an automated status update from the Work Package
– Maintain categories reflecting your build projects

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 55

Key Takeaways Requirements Management
How-to Document Requirements

Requirements

Capture Requirements as User Stories

(against the Process/Step)

Do’s and Don’ts

Requirements can be maintained at The ‘Requirements • Ideally define Requirements in a 1:1 Relationship to a Work Package
(in an Agile Development that means it can be realized in one Wave)
the following SolDoc Elements: Management’ • Description should in a clear and agreed user story format
• Structure Elements transaction can be (especially when working in big teams)
used to create/import • Define and follow clear meaningful naming conventions for Requirements
q Process
• Define and discuss within project team how to use priority, category and other
Requirements, or
q Process Step (Reference) attributes across project teams
filter/display lists of
• Library Elements • Decide on Requirements categories before starting Requirements gathering
Requirements. There is (This will help later tracking of the build and also simplify searching and filtering)
q Configuration Item also a link to ‘Mass • Requirements are ideally consolidated (not n Requirements for the same need)
q Process Step (Original) change’ function where • If required also document ‘Fit-Fit Requirements’ for holistic documentation & all
q Executable filtered Requirements Requirements that the business want to later test
q Development can have the status & • Description captured by Business Analysts; Classification needs consulting input;
Approval of Requirements by the business and programme management
q Interface ownership maintained.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 56
What’s New with Focused Build SP6?
Requirement Management
Requirements Management – new with Focused Build SP06
Performance Improvements
Focused Build