Needs versus wants
It wasn't until the second proof-of-concept for these tools that the teams started to get more attention from the business leadership. The CDO was curious to see what the DevOps team was doing, especially if there were measurable effects of the recent DevOps initiatives. The DevOps team was able to share what requirements had been gathered, what tools were being evaluated, and so on. For some, the speed at which these steps were accomplished were extremely fast. But the CDO was not as impressed with the timeline.
The initial directive and timeline, which was the main driver for all of the work the DevOps team had done, was now being altered. The CDO needed the teams to have a beta version of the application deploying to Kubernetes within a month.
The DevOps team immediately went into panic mode. Although the developers would be able to get the artifacts ready in time, the delivery pipeline would not be. The amount of time available meant that the DevOps...
