Week 2: Explore Phase (Process Expert/Analyst)

Unit 5: Managing Requirements Backlog

Managing Requirements Backlog
Release planning – Roles and responsibilities

Create requirement
based on business
1. Define product process
Business Analyst
Responsibility

backlog
Business

Use value points High-Level

and priority to rank Release Plan
2. Prioritize product Approve/
backlog postpone Based on Project
5. What would you like requirements
in the release?

3. Analysis of
Responsibility

dependencies
Architect

Use effort to Detailed

estimate
IT

Create work Release Plan

4. Estimate product
backlog packages Based on Wave
6. Scope release:
Build logical and technical
packages

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

Managing Requirements Backlog
Requirements Management process flow

= manual status setting

Requirements = automated status setting

Send for Approval To Be Approve

Draft Approved In Realization Realized Completed
Approved
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

Withdraw

Recover
Postponed Set
by
WP

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Managing Requirements Backlog
Find requirements

Use the Requirements app to filter, sort, and

maybe export the list of all requirements.

You can maintain further attributes like Value

Points or Effort Points to prioritize your backlog.

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Managing Requirements Backlog
Prioritize the backlog
How to establish clear priorities

▪ In Agile projects the process owner must prioritize and

force-rank list of all requirements in project backlog
▪ No two items should end up being ‘equal’ on the list (for
example, have the same priority and ranking)
▪ Main reason for this is to prevent everything being rated
as a “very high”.
▪ The MSCW prioritization (Must-Have, Should-Have,
Could-Have, Would-Have) is mapped with priorities very
high, high, medium, and low in SAP Solution Manager
▪ Secondary step is to rank items within the same priority
group with value points

Use columns “Priority” and “Value Points” in the

requirement in SSM to prioritize and sequence the
product backlog.

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

Managing Requirements Backlog
Approve requirements via Mass Change Operations app

You can use the Mass Change Operations app from SAP Solution Manager launchpad to approve requirements in
batch.

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

Managing Requirements Backlog
Monitor all requirements using the Solution Readiness Dashboard

Tile: Requirements
Gives an overview of all requirements assigned to your project.
Each bar of the tile is clickable and offers a filtered list of requirements.

Unassigned Requirements
The Unassigned Requirements bar displays all requirements
that still need work packages creating for them.

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

Managing Requirements Backlog
Demo

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

Thank you.
Contact information:

[email protected]
Follow all of SAP

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company 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
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.