Lesson 2: Customize the value stream
In this lesson, you will learn to modify the default value stream map.
The value stream that you created in the last lesson contains the default phases and stages. The phases and stages abstractly represent a software development lifecycle. The generic workflow is easy to customize, and, after you modify it to reflect your development process, apply it to future value streams.
When you create a value stream, the first thing to identify is the phases. There are many ways to divide a workflow, of course. One approach is to start with the tools that your team uses. In the default value stream, the Planning phase is used for project management and issue tracking tools, such as Jira. The items created in this phase define the project, both its overall scope and its smallest details.
The Development phase is where work starts on the issues created in the Planning phase. Most work in this phase is associated with version or source control tools, such as Git.
During the Deployment phase, software source code is turned into deliverable artifacts and deployed. Work in this phase is associated with build tools such as IBM® DevOps Build, and Jenkins, and deployment tools, such as IBM DevOps Deploy (Deploy).
The default workflow is shown in Lesson 1.
In the helloWorld workflow, you will use the Planning and Development phases and modify their stages. In other tutorials, you will use the Development phase and manage work items from conception to final deployment.
To modify the tutorial value stream, complete the following steps:
In this lesson, you modified the value stream by downloading and editing the value stream JSON file.


