SAP Cloud ALM - Break Fix for Productive Processes?

[brad_saxon]

We have an SAP Cloud ALM customer who is working in multiple releases and have been setting Processes to Production once they have gone-live. See below.

The question they have now, is when it comes time for Break-Fix (after Go-Live), should they be removing these processes from the earlier scope? They ask, because when logging Requirements, Test Cases, User Stories, Tasks, etc. if they are logged against the Processes under a specific Scope, they will appear under the previous Scope (1.1 for example). They would prefer they be logged as "Break-Fix" and not part of a previous Scope.

After Go-Live, do other customers create a Scope specifically for Break-Fix and include the same Processes? Or is there another way to handle processes which are Productive so as to include Requirements, Test Cases, etc. as NOT being tied to the previous Scopes? 

Thank you for the feedback!

[Sinje]

Hi Brad,

thanks for your valid question. One remark before giving my recommendation: think of "scope" as something that can last longer than a phase or even project in the long run. Scope could combine all processes of e.g. central finance and the releases and timeboxes are used to show what is implemented when as part of the project.

Regarding your customer situation: switch the status of the solution processes to "Maintenance", but keep them in the same scope. now you can assign new requirements, user stories, tasks, documents and test cases to the process. The new requirements and tasks can be assigned to new timeboxes (or releases if you use them for feature release) to manage them. for test cases you can bundle them in test plans and ad them as well to the relevant timebox. 

I hope this helps you. 

Best Regards,

Sinje