Overview

The Solution Intent provides the basic understanding of the current and evolving requirements, design and "intent" -- or larger purpose -- of the solution. This artifact would logically be created during the Analysis phase of the Kanban for Epics and typically would reflect the overall goals for delivery of a solution, including the usage model(s) supported and how they will be validated. The Solution Intent may have an associated Solution Context.

Learn more about Solution Intent as described by SAFe.

Artifact Template

The Solution Intent has a corresponding artifact template that can be used when you create a new Solution Intent artifact. The template reminds you about the things you should consider when articulating the context for a given solution. The template looks like this:

[Solution Intent Title]

<Derived from the Value Stream Epic for the solution being described.>

Vision

<What is the vision for this specific solution?>

Specifications

<Describe specifications, link to Solution Context for details.>

Compliance

<Describe the considerations for Compliance, citing specific regulations that are fixed as well as those that are variable in nature.>

Architecture

<Describe the critical architectural elements of the solution, if applicable.>

Design

<Describe the use cases and other design elements relevant at this level. Also describe any solution trade-offs that should be vetted with stakeholders and customers.>

Tests

<List the set of tests that must be performed in order to meet the Criteria for Success (provided by the associated Value Stream Epic for this Solution).>

Attributes

The Solution Intent artifact type defines the following custom attributes:

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

States

The Solution Intent 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 it 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