Value Stream Mapping the DevOps Void

In this article, learn about value stream mapping and also see some of the benefits.

Ever wonder why your releases take so long?

After all, your company just invested a “zillion” dollars on a whole bunch of great ‘agile’ tools and a cloud framework. Tools that allow you to automatically provision your infrastructure, applications, data, and ensure that all your security obligations are met.

Hey! With this new” DevOps toolchain”, we should be moving our releases, from request to delivery, in a matter of minutes. You know … full push-button automation! … environments on demand! … And all that stuff!

Yeah! Right! But no! That’s not how it typically plays out.

In fact, a more realistic example might follow a storyline as follows:

  • Project manager raises a request for a Test Environment
  • Request sits in its service management queue for a few days
  • Gets approved and assigned by Test Environment Manager and distributed to engineering teams
  • Sits in the team ITSM queues for another few days
  • Apps team build the package in 5 minutes but can’t deploy as infra not ready
  • Infra team provisions
  • Test team can’t start testing as data not ready
  • Data team ensures Data secure and Compliant
  • Data team provisions
  • Sorry, testing now too busy with another test cycle
  • Test teams spot a defect with the build
  • Higher priority project comes along and acquires environment
  • Go back to go

#devops #value stream mapping #devops void

Value Stream Mapping the DevOps Void