Under the legacy approach to software development, developers write code, which is then frozen, tested by another group, released and ultimately supported by yet another team again. Under this highly structured approach, large enterprise software applications are typically updated every 6 to 12 months, and up to several years can pass between major operating system releases. In enterprises, risk appetite and the desire for stability typically drive these intervals. This “silo” approach to software development practices is clearly out of synch with today’s real-time-focused business world.
Loading ...
Bridging the Great Dev/Ops Divide
Posted by: James Turnbull June 30, 2011 05:00 AMUnder the legacy approach to software development, developers write code, which is then frozen, tested by another group, released and ultimately supported by yet another team again. Under this highly structured approach, large enterprise software applications are typically updated every 6 to 12 months, and up to several years can pass between major operating system releases. In enterprises, risk appetite and the desire for stability typically drive these intervals. This “silo” approach to software development practices is clearly out of synch with today’s real-time-focused business world.