Welcome to Anne Gentle's just write click blog

RSS Subscribe to RSS

Eating our own dog food, or sipping our own champagne

How we strive to achieve BSM at BMC

Eating your own dog food. The phrase comes from the early television advertising genre when people would ask, but will the dog eat the food? Today it’s categorized as a computer jargon phrase, well-documented in a Wikipedia entry, describing how software companies and other industries try out their own products, putting themselves in their customers’ shoes. I assure you that at BMC, our IT group often pops open cans of our dog food, or sips our own champagne, as Thomas Siebel prefers to call it.

My favorite essay on the topic has to be Joel Spolsky’s “What is the work of dogs in this country?” essay from 2001. Read both the Wikipedia link and the essay for all the nuances and pros and cons of eating one’s own dog food. I especially like Joel’s example of how the Juno executive wanted six pop-up ads until he experienced it himself and then backed off to two pop-up ads.

Similarly, I have heard people ask over and over again, this BSM stuff sounds great, but are you really doing it internally, BMC? That type of question is the heart of eating one’s own dog food. “Sounds great, but have you put it into practice? Show me.”

In the spirit of documenting how we eat our own dog food, I recently completed a white paper, “Implementing Resource Management Using Business Service Management Principles.” It’s about how our research and development lab schedules server resources for testing. This scheduling is no small task, especially in an Agile development environment with iterations that might go for 2 weeks or 4 weeks. The products we test also may need to be tested on 14 different platforms. I think the team used a half dozen BMC products and intend to use even more in the future, such as the advanced discovery and provisioning tools we have available. Products consumed so far, with more on the way:

So take a look at the paper - no registration is required - and let us know what you think. This IT group, including talk.bmc’s own Steve Carl, is constantly looking forward to make their processes even more business service centered.


Alterpoint blog gives kudos to our Routes to Value approach to BSM and ITIL

Breaking down best practices by making the parts easily accessible

Alterpoint is located in Austin (where I’m located) and makes network management software that is integrated with our BMC Remedy Action Request System and BMC now resells their product, DeviceAuthority. With just a couple of “follow this idea” clicks, as often happens when I read blogs, I found this blog entry, ” Break it Down: Making Strides with ITIL and Best Practices.” In it they give props to BMC for creating the BSM Routes to Value that make the sometimes daunting task of implementing best practices for IT manageable — by breaking it down into parts that make sense. My favorite lines from this post are these, because it mirrors my own observations lately.

One of the basic points is that these transformational projects have too much at stake to be threatened by internal pride or lack of good internal assessment. To realign around ITIL or other best practices, you often need to adjust, enhance or expel some process and cultural factors that are baked into your operation before you even start talking about technology.

I’ve got a white paper in progress where I offer observations of methods for implementing ITIL best practices, starting with the infrastructure tools you already have in place, and in it I discuss getting started with small projects that can later add up to more. You hear corporate culture stories when you start to talk about ITIL projects, and Gary Holmes has some great observations in his comment on Throw out ITIL, but keep the CMDB?. I look forward to hearing more corporate culture and organizational communication stories as I continue to learn about this IT Infrastructure Library myself.