Review and complete requirements

The purpose of this task is to ensure that your requirements are fully documented and understandable.

Prerequisites:

  • The required adaptions for the system were captured during the fit-to-standard workshops.

Procedure:

  1. Review and validate all required Requirements.
  2. Add any relevant information to the Requirement.

Decide how to follow up on the Requirements, you also might want to change the workstream.

Workstream represents logical grouping of deliverables in the same area of work. They are used as an attribute of a deliverable to indicate in which area of project the work will be done .

Tasks are also assigned to workstreams that provide an alternate working view. The list of workstreams is

WorkstreamDescription
Project ManagementCovers planning, scheduling, governance, controlling and monitoring the execution of the project. Target group of this work stream are project managers.
Application Design & Configuration

Covers the confirmation of scope, fit-to-standard analysis, identification of delta business process requirements, and functional design of the solution. In later phases, it covers the configuration activities, unit testing to fulfil the customer requirements. Items that can be configured include: forms, workflows, user permission/security, screen layout, reports, master data setup, notifications, etc. This work stream also covers the demonstration of the configured/developed solution to the customer project team after each iteration cycle for customer acceptance and identification of adjustments needed for the next iteration. Note. This Work Stream includes RCEFW deliverables in OP deployments. It does not include Integrations, they are covered in separate workstream.

TestingCovers test strategy, test planning, test case development, and execution of Integration Test, Performance Test, System Test, Regression testing, and User Acceptance Test.
IntegrationCovers identification of integration requirements, integration points, integration approach, and integration solution design. The work stream also includes the setup of integration environment and middleware between the solution and any external systems.
Solution AdoptionCovers Value Management, Organization Change Management (OCM), and End-User Training topics of the deployment project.
Customer Team EnablementCovers the enablement of the customer project team to work on the project effectively. This include standard product orientation to prepare the customer for product requirements and design discussion, as well as key user and admin training to prepare the customer for test case development and test execution. The tasks will lead to a full project team enablement.
ExtensibilityCovers the design, development, and deployment of system functionality that cannot be provided by the standard product and needs to be custom developed. Note: Focus is on solution extensibility beyond the RICEFW that are covered in Design & Configuration and Integration.
Data Management

Covers the discovery, planning and execution of moving legacy data to the new system and archiving of legacy data. This work stream also covers cutover planning, preparation, management and execution of activities to cutover the system into production. It also includes the hyper-care support period shortly after cutover.

Technical Architecture & InfrastructureCovers the solution landscape, deployment concept, system architecture, technical system design, environment (development, testing, production, failover) setup, technology operations standards and process.
Operations & Support

Covers the establishment and setting up of the helpdesk process, incident management process, post go-live change management process, & user related operations standards and process.

Analytics

Covers the design, creation, testing of the reporting and analytics inside the implemented solution.

Approve requirements

The purpose of this task is to approve requirements and automatically generate user stories or project tasks. With that you hand a requirement over for realization.

Prerequisites:

  • The requirements captured during the fit-to-standard workshops are reviewed and specified.

Procedure:

  1. Check for properly specified requirements in status "In Specification".
  2. Select the requirement you want to generate one depending user story or project task for.

Approve the requirement and generate a user story or project task automatically simply by triggering the action "Approve & Generate User Story" or "Approve & Generate Project Task".

 

 

Generate User Stories

Creating User Stories and Sub-Tasks in SAP Cloud ALM

What is a User Story

A User story is a user need that needs to be fulfilled in order to provide a business value. It may or may not have an associated Requirement.

Based on the feedback from customers , who want to implement the projects using agile methodology , we introduce a new Task Type called User Story. Now in your task list you will have an additional option.

The user story will have similar attributes as that of a task, there is one additional capability, you can create sub tasks below a user story.

 

You can assign a user story to any timebox but we recommend that you create a sprint schedule and assign user stories to sprints. We advise that you create user stories in such a way that it can be finished in one sprint.

What is a Sub-Task

A Sub-Task is an optional task type that can be created below a user story. You can just click on create sub task option after you create and save your user story.

The attributes of sub task are slightly different from a user story. A user story can have its own timebox but a sub task only inherits the timebox from its parent, which is a user story in this case.

How and when to use User Stories and Sub-Tasks

We know that SAP Cloud ALM comes preloaded with templates from Activate methodology. That content primarily constitutes of methodology tasks that help you understand the order in which tasks should be conducted in a given project phase.

When you conduct Fit-to-Standard workshops and plan your Project into fine level timeboxes as an example sprints, you may want and slice your work much smaller and also ensure its handled differently as compared to the template or project tasks. You may also want to quickly see work planned in an upcoming sprint.

This is where user stories and sub-tasks help you. This also allows better collaboration and parallel work. As an example you may have a user stories that may need input from multiple people as an example a UI expert , a user assistance expert, a database expert etc. You can create multiple sub-tasks assigned to the same user story that helps people collaborate.

Next steps

User story and sub-task creation is one the first steps in ensuring SAP Cloud ALM enables agile methodology. This capability will be extended with more features in upcoming releases