Value Stream Analytics
Values Streams are all the rage these days. In many ways, applying values streams to software development is no different than mapping out your software development workflow or lifecycle, but some folks would argue that it's important that you go a bit broader, especially earlier, to include the business ideas and planning aspects. Sounds a lot like our idea to production flow. Of course, that's already included in our DevOps lifecycle; and our DevOps lifecycle goes beyond, to include monitoring after deployment to production. At any rate, we have Cycle Analytics which is kind of similar, but perhaps we could deliver something specific for value stream.
- Rename Cycle Analytics to Value Stream Analytics
- Let people define their own value stream
Now, one way to do this might be to use Issue Boards. Imagine that I define my value stream as columns in an Issue Board, and then as I move issues between columns, I keep track of those transitions and use them to calculate time spent in each stage of the value stream (https://gitlab.com/gitlab-org/gitlab-ee/issues/5783).
Now imagine that we automated some, or all, of that movement. e.g. When an issue's merge request is deployed to staging, move the issue to Staging. In this way, using labels would let people track manual things if necessary, but automate as much as possible. It would have a really great byproduct of making issue boards more valuable.