Capture developmental value stream data
The license package Lean Portfolio Management is required to work with developmental value streams. The use case Agile Implementation must be activated.
A development value steam is the sequence of activities required to design, build, test, and deliver the systems or solutions that enable an organization’s operational value streams. It represents how teams create and evolve the capabilities the business relies on.
Users with the user profiles Portfolio Manager, and Portfolio Admin can add and edit developmental value streams in Alfabet. Click for an overview of permission concepts.
In the navigation panel, click Agile Architecture > Development Value Streams. Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench or you can navigate to a developmental value stream's content area and define it in more detail there. Click to learn about how to use data workbenches.
Create a new developmental value stream from scratch. Go to Agile Architecture > Developmental Value Streams and click New > Developmental Value Streams. Specify the developmental value stream's attributes as well as the relationships that the developmental value stream has to other assets in the repository. All mandatory fields must be defined to create the developmental value stream and save it.
Edit the attributes and relationships for an developmental value stream. Click the Navigate
button next to an developmental value stream to open its content area. Specify the developmental value stream's attributes as well as the relationships that the developmental value stream has to other assets in the repository.
Try to capture as much information as possible about the developmental value stream because complete data considerably improves the results of business questions and other analytics.
Once a developmental value stream is in the repository, you can define more details about it in the Epics data workbench.
Per default, the data workbench displays a limited set of basic attributes. You can add more columns via the Structure column to capture other attributes directly in the data workbench.
Or specify and analyze the developmental value stream in detail in its content area . In the data workbench, click the Navigate button for a developmental value stream to open its content area > Overview page.
Define the developmental value stream's basic data. All mandatory fields must be defined to create the developmental value stream and save it.
- Name: (Mandatory) Enter a unique name for the developmental value stream. The name should help others easily understand the purpose of the developmental value stream.
- Description: Enter a meaningful description that will clarify the purpose of the developmental value stream.
- Authorized Access tab: The user who creates the developmental value stream is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the developmental value stream. All users in the authorized user group can edit the developmental value stream.
Specify the solutions that provide the developmental value stream. In this context, a solution refers to the applications or components in the repository that enable the developmental value stream. Ideally the solutions are consistent for the value stream steps across the developmental value stream.
Go the Developmental Value Streams data workbench, click the Navigate
button next to a developmental value stream to open its content area. In the Solutions field, select the applications and components that enable the developmental value stream.
A role represents a functional responsibility that a user or organization has for the developmental value stream. Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets?.
Responsibilities are based on preconfigured role types. Your company may also configure custom role types via the Portfolio Admin user profile. Depending on the role type, a specified user and/or a specified organization may fulfill the responsibility for the developmental value stream. A user assigned responsibility via a role has read-only permissions to the developmental value streams. To change data about the developmental value stream, they must also be specified as an authorized user or member of an authorized user group.
Roles can be assigned to a developmental value stream in the Developmental Value Streams data workbench or the developmental value stream content area via Overview > Responsibilities. A person can have one of the following roles or a custom role added by your company:
- Business Owner: A person who is the responsible owner of the developmental value stream.
- Stakeholder: A person or organization that has an interest in the developmental value stream and therefore requires read-only access permissions.
To specify responsibilities for the developmental value stream:
- Click in the relevant role field to open the selector.
- Expand the ORGANIZATION or USER sections in the selector and select the person or organization fulfilling the role.
- Click OK to save the role definition and close the selector.
Go to the developmental value stream's content area > Investment Context > Epic Kanban.
The Epic Kanban view shows a Kanban-like matrix displaying epics that impact the developmental value stream. The epics colored by their epic type and positioned in lanes according to their status. Drag an epic and move it to a different lane as needed. The lanes represent the following statuses:
- Funnel: New epic under initial consideration.
- Reviewing: Epic being evaluated to determine if it is aligned with business goals.
- Analyzing: Deeper assessment of epic for feasibility and impact.
- Backlog: Epic is waiting to be prioritized and allocated resources.
- MVP: A minimal version with one or more features is created to test assumptions and gather feedback.
- Persevere: Based on feedback, the epic continues, pivots, or stops.
- Done: Epic is complete, tested, and ready for release.
Developmental value streams are assigned to the architecture scope of an epic in the Affected Architecture view in the epic's content area.