Managing Requirements

Objective

After completing this lesson, you will be able to illustrate the creation, approval, and refinement of requirements.

Management of Requirements

The magic ring of requirements management. It consists of three major parts: the requirement, the user story, and features.

Requirements management in SAP Cloud ALM deals with the entity requirements, user story, and feature.

Details about the figure:

1. Requirement
  • Business-focused functionality: Describes required functionality from a business point of view.
  • Multi-sprint implementation: Functionality can be implemented over multiple sprints.
2. User Story
  • Small, actionable functionality chunks: Describes a smaller part of the required functionality that can be completed in a few days or less.
  • User stories for step-by-step planning: Requirements are broken down into user stories to plan step-by-step implementation.
  • Daily dev tasks (optional): Optional task, functionality to be realized by one dev member daily.
3. Feature
  • Sprint-sized, business-value features: Represents functionality that delivers business value to a target system and is sized to be delivered in a single sprint.
  • Deployed together as a unit: Functionality that is represented by a feature must be deployed to a target system together.
Visualization of the process of managing requirements. based on a process, the requirement is created. The requirement itself creates user stories, additionally, test cases are assigned and features are created based on the requirement.

Description of the requirements driven process:

  1. Requirement created from solution process→approval process→refined in multiple user stories (and optional in tasks).
  2. Feature created from requirement with manually assigned user stories.
  3. Created test cases can be assigned to the requirement and/or to user stories.
  4. Feature creates/assigns transports.

Other possibilities to work with SAP Cloud ALM (can be discussed):

  1. Requirement without refinement in user stories→approval process→feature created from requirement (creates/assigns transports)→test cases assigned to requirement.
  2. User stories created without requirement (no approval process)→feature created without requirement→feature creates/assigns user stories and creates/assigns transports→test cases created and assigned to user stories.

Exercises in the Unit: Managing Requirements

Flowchart of all steps of the exercises, the steps, which are processed in the next exercise, are highlighted.

The figure illustrates all steps, performed in the exercises of this training.

In the exercises of this Unit, you will perform the following steps:

  • Create Requirement:
    • Create new requirement from solution process.
    • Add mandatory information.
    • Add necessary additional information.
  • Approve Requirement:
    • Select requirement from Requirement Traceability.
    • Approve requirement to break it down into user stories.
    • Set requirement to In Realization.
  • Refine Requirement:
    • Refine requirement by creation of new user story.
    • Add mandatory information.
    • Add necessary additional information.
    • Create second user story.

Create a Requirement

Business Scenario

As a member of the Fit-to-Standard workshop team, you are asked to create Requirements to define the scope of the implementation project.

Task Flow

In this exercise, you will perform the following steps:

  • Use added solution processes.
  • Create a new Requirement.
  • Add necessary additional information.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Approve a Requirement

Business Scenario

As a project lead, you are asked to approve Requirements to task the project team with their implementation.

Task Flow

In this exercise, you will perform the following steps:

  • Use Requirement Traceability.
  • Select the created Requirement.
  • Approve the requirement.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Note

All text input fields can be confirmed by choosing the Tab or Enter key or by leaving the text box.

Create a User Story

Business Scenario

As a configuration expert, you are asked to break down requirements into user stories to plan the implementation steps.

Task Flow

In this exercise, you will perform the following steps:

  • Select created Requirement to refine it.
  • Create new User Story.
  • Add necessary additional information.
  • Create a second user story.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Note

All text input fields can be confirmed by choosing the Tab or Enter key or by leaving the text box.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn