Over a million developers have joined DZone.

Plan for Murphy

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

It seems strange to plan for Murphy’s Law, but if you don’t plan for risks, they will happen and they will turn into disasters. Some risks you can’t plan for, but many risks you can anticipate.

I plan for some typical risks: I keep a power cord in my office, in my briefcase, in my living room. I never have to move a power cord, and if cord fails, I have easy access to one.

I’ve been working on an agile architecture workshop with Rebecca Wirfs-Brock, and we have had more Murphy moments than any small project deserves. Last week, when we were close to done, but still were under pressure to meet our deadline (think one-week iterations), my power went out. Yes, my town lost power for several hours. In the afternoon, during our joint working time, the power went out. It doesn’t matter how many power cords you have, if you don’t have power to the house!

I texted Rebecca, so she knew that I was unable to save our files, that I had no power, and when the power company told me I might have power. Now she knew what I knew. I read a book—on my Kindle :-).

But my suggestion to plan for Murphy still holds. My Kindle still had power, so I could read for several hours. I even still have paper books—many of them. I have phones with built-in power so I could use them, at least for a while. I could have brought my computer to another town that still had power (something you might not be able to do on a larger project or in a location with a real disaster).

Risk management is project management. If you don’t plan for Murphy, he will come and live on your project forever. Take a few minutes and review your project: anything you need to do to keep Murphy off your project or program today?

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.

Topics:

Published at DZone with permission of Johanna Rothman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}