Design Implications of DevOps

A session at DevOps and Continuous Delivery: Successful Adoption, 18 September 2014, Chicago

  • Stephany Bellomo, Software Engineering Institute (Carnegie Mellon University)

The Agile movement began as a reaction to frustration over slow delivery of software that often didn’t sufficiently meet user needs. Agile improved software delivery and DevOps and Continuous Delivery extend what Agile began. Software development velocity may improves only to run into deployment-related delays due to issues such as inability to integrate frequently, challenges completing automated testing within an increment/build cycle and uncertainty about whether a build is stable and/or secure enough for external release. To avoid problems such as these, we suggest that design decisions need to align with deployment goals early and continuously such as reducing deployment pipeline cycle time. In addition, the application design should enable continuous delivery practices such as continuous integration, automated testing, synchronizing environments, etc. If not addressed, misaligned design decisions can become a form of technical debt - a heavy burden slowing down the release cycle that the project carries forward release to release. SEI is exploring what design decisions projects may want to consider early to enable deployability. In this talk, we summarize the challenges in this space and provide empirical examples of deployment-driven design tactics derived from real world projects striving toward continuous delivery.

About the speaker

This person is speaking at this event.
Stephany Bellomo, Software Engineering Institute (Carnegie Mellon University)

Sign in to add slides, notes or videos to this session

Tell your friends!


Date Thu 18th September 2014

Short URL


Official event site


View the schedule


See something wrong?

Report an issue with this session