Project Tasks - Multiple Releases and Phases?

[brad_saxon]

Customer is planning an S/4HANA project with multiple releases across different geographies. See below. Question came up on how they should handle Roadmap activities vs. Project Tasks which are specific to each Release?

For example, there are Roadmap Tasks which will need to be only completed once (set up CTMS, provision systems, etc.), but there are other Release specific Tasks which they know will need to complete as part of each Release (update Architecture Diagrams, training materials, onboarding, etc.). Currently, they are copying the Activate Roadmap Tasks and then uploading them for each Release. This essentially duplicates ALL of the Roadmap Tasks for each Release as Project Tasks. This approach is less than ideal because the Project Tasks do not allow linked Accelerators.

How have other Cloud ALM customers handled the need to duplicate some of the Roadmap Tasks? Do they wait for the Release to define only those Tasks which are necessary? Or are they copying them in advance? Or, are they setting up different Cloud ALM Projects for each Release?

Normally, I see each geography rollout defined as a Scope. However, defining the individual rollouts as a Scope does not address the Tasks question. How to handle Tasks across both Roadmap and Phases when there will be multiple releases?

[DoloresCorrea · Accepted solution]

Hi Brad, 

I think this question is not relevant anymore.

Let  me close it. 

If yes let me know,

Dolores