Artifact: Scenario Act

Overview

The Scenario Act is a child of the Lifecycle Scenario artifact and elaborates a Use Case that is part of the end-to-end scenario. There may be multiple Acts in a Lifecycle Scenario, and Acts are logically implemented by Capabilities or Features. Acts are defined during Solution elaboration at the Portfolio or Large Solution level as part of the analysis activity.

The kind of systems thinking involved in developing a Lifecycle Scenario with Acts is a key aspect of the solution elaboration process prescribed by SAFe.

While SAFe does not specifically define artifacts like the Scenario Act, it is included to help you formalize the usage models that are critical aspects to modeling any solution.

Artifact Template

The Scenario Act has a corresponding artifact template that can be used when you create a new Scenario Act artifact. The template reminds you about the things you should consider when articulating an activity that is part of a scenario. The template looks like this:

[Scenario Act Title]

<Title of the activity>

Example: Align & Balance Program Backlogs

Description

<High-level description.>

Example: In this Act, the Portfolio and Program Teams collaborate to align the Program work for the next few Program Increments with the Portfolio priorities. As this happens, the Portfolio will be watching for any risks or impediments so that mitigation happens in near real time. This Act involves both Portfolio and Program project areas, so roles change for the Program Leads depending on which project area is used.

Roles

<List the roles involved in the scenario act.>

Input

<Describe any inputs into this activity.>

Output

<Describe any outputs as a result of performing this activity.>

Scenes

<Link and embed the Scenario Scenes (as children).>

Attributes

The Scenario Act artifact type defines the following custom attributes:

  • Owner - The owner of the artifact
  • Status - The status of the artifact (see States below)

States

The Scenario Act artifact type has this workflow:

  • Draft - Initial state of the artifact
  • Under Review - Indicates that the artifact is being reviewed by the Portfolio team
  • In Playback - Indicates that the artifact is being reviewed with stakeholders and customers for feedback
  • Approved - Indicates that the artifact is approved by the Portfolio team as well as stakeholders/customers
  • Rejected - Indicates that the artifact is rejected and no further work will be done
  • Deprecated - Indicates that the artifact has been deprecated and there may possibly be a newer version of it

Traceability

 

Relationships