A few months ago I started talking about “Agile Operations”, which is my adaptation of Incident Command to technology development and operations. Blaine Cook brought it up during the Web2.0 Expo Program Committee Meeting, and I realized that I hadn’t mentioned it here before.

I’m in the process of writing an introduction and some case-studies. I’m considering putting together a course.

(from wikipedia)
The Incident Command System (ICS) is a standardized, on-scene, all-hazard incident management concept. It is a management protocol originally designed for emergency management agencies and later federalized. ICS is based upon a flexible, scalable response organization providing a common framework within which people can work together effectively. These people may be drawn from multiple agencies that do not routinely work together, and ICS is designed to give standard response and operation procedures to reduce the problems and potential for miscommunication on such incidents.

ICS has been summarized as a “first-on-scene” structure, where the first responder on a scene has charge of the scene until the incident is resolved or the initial responder transitions incident command to an arriving, more-qualified individual.

Overview

ICS consists of procedures for controlling personnel, facilities, equipment, and communications. It is a system designed to be used or applied from the time an incident occurs until the requirement for management and operations no longer exist. ICS is interdisciplinary and organizationally flexible to meet the following management challenges:

• Meet the needs of incidents of any kind or size.
• Allow personnel from a variety of agencies to meld rapidly into a common management structure.
• Provide logistical and administrative support to operational staff.
• Be cost effective by avoiding duplication of efforts.

Technorati Tags: ICS, incidentcommand, emergencymanagement, agile, operations, agile operations, agileoperations, disastercamp

I am at FooCamp getting to hang out with a few friends and talking about technology, emergency management, and finance. I’ve pimped Swivel, BarCampBankSeattle, and Black Rock Federal where it’s been appropriate, gave a “FooCamp Survival Guide” lightning talk, and am giving a talk tomorrow on Designing for Disaster & DisasterCamp

Designing for Disaster & DisasterCamp

Date: Sunday, June 24

Time: 11:00 - 12:00
Location: jackal (tent)
Track:“Another F***ing Growth Opportunity”

The first part of this talk will cover a few (painful/entertaining/instructive) lessons I’ve learned from emergency management and humanitarian aid. We’ll then talk about how these apply to you and the technologies you design.

Then we’ll talk about DisasterCamp, a project to provide training and operational experience under realistic conditions… (AKA: “hazing the n00bs”).

I leave here tomorrow and fly out to meet the Swivel Team in Turkey for the OECD World Economic Forum.

BarCampBank

• BarCampBankSeattle announced (original post)
• Currently selecting date and location

Black Rock Federal

• Revised Field of Membership revised to be IgnitionNW
• Met with Credit Union executives, discussing possible partnerships
• Waiting on charter details from NCUA

DisasterCamp (New Project)

• Initiated new project which I’ll be talking about more about soon!

LimberMedia

• See Allegra’s Updates on the blog

Other stuff

• Will be helping Brady with Ignite @ Where2.0
• Considering entering GreaseBallRally 2008 with an ambulance or fire engine.



Powered by Gregarious (21)

Share This

I’m giving a talk at the Web2.0Expo on Wednesday called “Failures, Disasters, & Resilient Design“. I’ll be using some of the lessons-learned from our deployment and how they apply to managing technology.

Failures, Disasters, & Resilient Design
(Click here for ExpoCal!)

Jesse Robbins, ex-Amazon, OpenAid

Track: Web Operations
Date: Wednesday, April 18
Time: 4:30pm - 5:20pm
Location: 2008

This talk reviews real world examples of complex systems failure and how they relate to Web 2.0. Drawing on his work as the “Master of Disaster” at Amazon and using examples from Nuclear Power to his own experiences after Hurricane Katrina, Jesse will provide:

• A methodology for managing risk with Web 2.0 technologies.
• Best practices for building Resilient Systems with Web Services & Web Scale Computing
• Stories and pictures of things blowing up!

Here’s the full-version of one of my slides: