Overview

A Role describes a class of people that interact with a system.  Roles describe functions and responsibilities of members of an Agile Release Train. SAFe outlines many critical ART roles and some speciality team roles. To learn more, visit the Scaled Agile Framework topic Agile Release Train. 

For each Role ‘personas’ are developed. Personas are fictional people who might use a product or solution in a similar way, providing insights into how real users would engage with a solution.  Developing Personas are an important Design Thinking activity which drives product development and several SAFe practices.  To learn more, visit the Scaled Agile Framework topic Design Thinking.

The Role has a corresponding artifact template that can be used when you create a new Role artifact. The template specifies the things you should detail. The template looks like this:

[Role Title]

<Title of the role>

Example: System Administrator

[Name of the Role]

<Description of user role>

Sample Persona

<The purpose of personas is to create reliable and realistic representations of the user role>

Attributes

The Role artifact type defines the following attributes:

• Alternate Spelling - The word which can be used as an  interchange repeatedly and regularly with the role in time.
• Owner - The owner of the artifact
• Status - The status of the artifact (see States below)

States

This 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