If IT has become disconnected from the business, it may be time to rethink your org chart. Draper's CIO shares how his team forged a tighter business relationship using a new IT role.
How do CIOs deal with agile and DevOps?
An interview with Aaron Stibel, Executive Vice President, Technology of Dun & Bradstreet Credibility Corp about Agile and DevOps.
The Enterprisers Project (TEP): The shift from traditional waterfall software development to agile seems to be in full force. Are you noticing it in your travels?
TEP: You’ve been using DevOps in your organization to drive faster delivery for at least a year. What has it been like to live through that transition?
STIBEL: We had to redeploy our entire organization. In the first two years, we went crazy fast and did something incredible. Since then we’ve been able to implement true agile and move to rolling releases and then partly to continuous integration. The moves we’ve made from multi-version releases to rolling releases then continuous integration have created massive advantages. When we were just doing multi-version releases it was so painful. We’d wait for the selling day to end at 7 PM. We’d do the release. We’d get dinner for everyone. We’d be here until 3 in the morning at times. God forbid it didn’t work by 3 in the morning; we’d have to roll back and start over another day. It was horrible. Work-life balance was a mess. The efficiency of the team was a mess. We decided we couldn’t kick the can down the road anymore, so our head of engineering and his team came up with a killer rolling release plan and organized a really strong DevOps team. One of our most senior engineers/architects is no longer on projects; now he heads up DevOps.
TEP: How do you look at measuring the other impacts of a DevOps group and Agile development?
STIBEL: We track stats very closely for each story, epic, and ticket in each release. Engineering and PMO have their KPIs, but the one I focus on for DevOps is the ratio of revenue producing or product tickets versus non-revenue tickets in each release. A high ratio means our productivity is visible to the rest of the organization and helps the top line. A low ratio means, even while being very productive, the productivity is targeting technical debt and bugs. The amount of products and product enhancements we have rolled out has probably gone up by 20, 30, or 40 percent in the latter half of the year. More importantly to me, the happiness of the team has improved materially. There is no calling your wife or your husband saying, “Hey, I’m not coming home today.” We don’t have that anymore. When releases don’t go well, they don’t go well at 2 p.m., and we can figure out how to deal with it during the workday. None of this is brain surgery. It’s just hard to switch. You have to build a lot of technology on your platform and you have to build an organization for it. We made the investment this year and it has paid off in spades.
Aaron Stibel serves as Executive Vice President, Technology of Dun & Bradstreet Credibility Corp. Prior to Dun & Bradstreet Credibility Corp., Aaron spent nine years with software company Revenue Solutions Inc. where he co-created DiscoverTax and led technology efforts for multi-billion dollar enterprise data warehousing implementations for government agencies. He additionally led consulting and sales engagements for large-scale enterprise technology implementations ranging from $500K to $250M. Previously, Stibel was a senior technology consultant at Granitar, helping financial services clients develop eCommerce and data strategies, including implementations for Thompson Financial, MindBranch.com, Law.com, Boston.com, and NYT Companies. Stibel began his career at business consulting firm PriceWaterhouseCoopers in the Strategic Change Business Unit. He holds a BS in Computer Science from The Johns Hopkins University.