Most enterprises still develop applications in large chunks and release them infrequently by throwing them over the wall to operations. The mega software either works or it doesn’t – there’s often no middle ground. These projects are historically associated with long timelines and traditional waterfall methods which don’t allow for rapid iteration and feedback. The infrastructure team then receives the commensurate requests for more servers, triggering a large capital expenditure request to the CIO, who isn’t always aware of what it’s for. In these situations, there’s often a divide between the Apps, Infrastructure and Ops teams, and these types of scenarios don’t help the situation.
Scaled DevOps
