The Agile Executive

Making Agile Work

Posts Tagged ‘dev/ops

It starts with Agile – The Pragmatic Cloud

leave a comment »

In the podcasts around here and Israel’s posts we often talk about using cloud computing as a tool to deliver better software – indeed, to better the software delivery process. Those two angle on cloud computing are what I tackled in a recent presentation (given as a keynote at the Philly Emerging Technologies for the Enterprise conference last week). As I said in the talk Agile development thinking is a great start for figuring out how to take advantage of cloud computing.

You can see a rehearsal recording of the talk over at my blog (or click play on the above) or hear an audio-only recording of the actual talk over at the Chariot TechNetCast, here’s the slides.

Advertisements

Written by Coté

April 14, 2010 at 9:00 am

Posted in Cloud Computing

Tagged with ,

How to Initiate a DevOps Project

with 4 comments

17th/21st Lancers c. 1922-1929 "THE FIGHTING SPIRIT!" by sunnybrook100 - One Million Views!.

Source: 17th/21st Lancers c. 1922-1929 “THE FIGHTING SPIRIT!”

Agile consultants on a development project often start by helping the team construct a backlog. The task is sufficiently concrete to get all stakeholders (product management, project management, development, test, any others) on a collaborative track through the creation of a key artifact. The backlog establishes a base line for the tasks to be carried out in the project.

For a DevOps project, start by establishing the technical debt of the software to be released to operations. By so doing you build the foundations for collaboration between development and operations through shared data. In the DevOps context, the technical debt data form the basis for the creation and grooming of  a unified backlog which includes various user stories from operations.

Apply the same approach when you are fortunate to be able to include folks from operations in the Agile team from the very beginning. You start with zero technical debt, but you track it on an ongoing basis and include the corresponding “fix-it” stories in the backlog as you accrue the debt. Running technical debt analytics on the source code every two weeks is a good practice to follow.

As the head of development, you might not be comfortable sharing technical debt data. This being the case, you are not ready for DevOps.

dev/ops with John Allspaw – The Agile Executive #08

leave a comment »

Guest co-host Andrew Shafer and Coté talk with John Allspaw (now at etsy) about the dev/ops idea and, more interestingly, cultural and process needs and changes.

To listen to this podcast, download the podcast directly, subscribe to the blog/podcast feed in iTunes (or whatever), or click play below to hear it:

Show Notes

  • Check out the video of the Velocity talk we reference frequently. It has some actual meat when it comes to biting off a dev/ops culture, practices, and process.
  • John opens up by speaking to tools vs/& culture
  • I ask John how his org got over the hump of “we’re a special snow-flake” – resistance to change .
  • Effecting cultural change by speaking to problems solved and benefits of the new culture.
  • What are some major changes in ops and dev process/culture? Continuous deployment (pushing small changes, often).
  • Getting beyond the culture of no – change management tends to be really “no management.”
  • You have to have a good track record to do this (MTTR, MTTD) – don’t crash the car. What’s deployment to incident ratio?
  • The role of metrics (monitoring) becomes important.
  • Physical vs. virtual stuff in operations, EC2 use, etc. People use public cloud stuff for best-of-breed solutions, like SmugMug usage.
  • Taking flickr from 25th most popular web property to the 5th.
  • Coté is glad John’s at Etsy, cause it fuels the best blog du jour, regretsy.

Written by Coté

February 11, 2010 at 3:53 pm

Posted in Podcasts

Tagged with ,