DevOps Zone is brought to you in partnership with:

Steve Smith is an Agile consultant and Continuous Delivery specialist at Always Agile Consulting Ltd. An XP / Lean developer with 10+ years of experience in enterprise software development in Britain and New Zealand, Steve favours practices such as Pair Programming and Test-Driven Development to build quality into software products. As an early adopter of Continuous Delivery he has overseen transformation programmes in multiple organisations to reduce lead times and increase product revenues. Steve is a co-author of the Continuous Delivery and DevOps book "Build Quality In", a co-organiser of the monthly London Continuous Delivery meetup group, a co-organiser of the annual PIPELINE conference, and a regular speaker at conferences such as Agile On The Beach and QCon New York. Steve blogs at Always Agile Consulting and is on Twitter at @AgileSteveSmith. Steve is a DZone MVB and is not an employee of DZone and has posted 28 posts at DZone. You can read more from them at their website. View Full User Profile

Continuous Delivery != Service Management

10.23.2013
| 5052 views |
  • submit to reddit

Continuous Delivery is homogeneous, Service Management is heterogeneous

In the seminal Continuous Delivery book Dave Farley and Jez Humble describe how Continuous Delivery and Service Management methodologies such as ITIL share an overriding focus on delivering increased value to customers“, and advocate a Repeatable Reliable Process for releasing software as follows:

  1. Select version
  2. Prepare environment
  3. Deploy binary
  4. Configure binary
  5. Stop running version
  6. Migrate data
  7. Start new version
  8. Run smoke tests
  9. Perform exploratory testing
  10. Approve or reject binary

Each of the above actions provide an operational capability that is potentially of value to Service Management as well as Continuous Delivery, such as the ability to remotely start/stop an application. However, Continuous Delivery and Service Management fundamentally differ in terms of both action frequency and ordering – while a Continuous Delivery pipeline will offer a single workflow encapsulating the same actions in the same order, the Service Management domain requires multiple workflows and adhoc actions in order to respond to operational issues.

Continuous Delivery is homogeneous, Service Management is heterogeneous

Conflating the homogeneity of Continuous Delivery and the heterogeneity of Service Management capabilities into a single tool artificially couples different business concerns and consequently makes it more difficult for an organization to respond to change.



Published at DZone with permission of Steve Smith, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)