Task Content sources & types

The standard task content provided in SAP Cloud ALM for implementation comes from SAP Activate methodology in the form of roadmaps. 

The implementation roadmaps provide end to end procedural guidance to help new and existing SAP Customers navigate through an SAP software implementation. 

The roadmaps are organized by phases, deliverables and tasks with accompanying linked accelerator assets that provide the right information at the point in time that it is needed in the project. The content is continually updated and provides the detailed guidance behind the SAP Activate methodology.

There are multiple roadmaps available to choose from and you can find the one matching to your use case.

Selection of an Activate Template triggers task generation in the Project.In addition to the generated tasks, you can also create your own task content by manually creating tasks or uploading task content using an upload template.

What is the Roadmap Viewer

The Roadmap Viewer is another tool to access the SAP Activate methodology implementation roadmaps.

 You can access the roadmap viewer here.

SAP Activate team maintains Task Repository and the same task content is distributed to both to SAP Cloud ALM and Roadmap viewer. SAP Cloud ALM has a subset of roadmaps which are available in Roadmap viewer.

Please note SAP Cloud ALM supports a lot of Process content and Test management content which is not available in Roadmap viewer.

Anything that you need to take an action on or a track in SAP Cloud ALM is a task. Since different tasks have different behaviors (e.g can this be edited or not) and attributes (can I assign story points or not), you need to understand Task Types.

Task Types in SAP Cloud ALM

Template Task

A Task which is delivered by SAP. It's content cannot be updated by a user and is called a Template Task. An example would be tasks delivered by SAP Activate methodology which are generated when the user selects a Project template during a project set up.

Project Task

Tasks created by users manually as required in the Project. This includes tasks uploaded via excel import.

User Story

Task that describes user expectations as part of the Requirement to Deploy process. A requirement can be broken down into one or multiple user stories if the requirement includes different functionality which is required.

Sub-Task

A breakdown of a user story into smaller under-stable segments of work.

Differences in Task Types

The table below helps understand the subtle differences in Task Types.

Task Sources

You need to understand from where did the task land in your task list. That is explained by Task sources. Currently the following sources are supported.

SAP Cloud ALM setup

These are also called Foundation tasks. These tasks exist in system even before an Activate template is selected. They help the user understand how to use SAP Cloud ALM and get started.

SAP Activate Methodology

Tasks that are generated when SAP Activate template is selected

Manually created

Tasks created manually by the user.

Requirement

Tasks generated when Requirement is approved for Realization.

Scoping

These are also called scope specific tasks. Each scope creation causes generation of these tasks guiding the user deal with created Scope.