Another busy day started with a breakfast briefing at 7 am and wrapping up about 7 pm. Here are the highlights from February 17th:
Breakfast Briefing – What’s for Breakfast session with Kirk Weisler – personal growth and development is one of the top three needs. As part of our own personal growth, Kirk suggested some books. His short list included: Switch, How to Change Things When Change is Hard, 7 Habits of Highly Effective People, The Oz Principle, The Power of Habit , Visual Teams, Now Discover Your Strengths, Tribal Leadership. In addition, Kirk mentioned that the Zappos headquarters is located here in Las Vegas and we can tour their office and learn a bit about their culture. I’m hoping to get that opportunity after the end of the conference.
Daniel Burrus – Flash Foresight – Daniel talked about technology trends and a little bit about how the biggest trends are changing the world. He believes the competency many companies are missing is execution and the ability to anticipate the future. He suggested we start with certainty; the future is all about relationships and relationships are built on trust. Understand the difference between hard trends and soft trends. Think about how our kid’s gaming experience with current gaming technology and think about how they must feel like they’re taking a giant step backwards each day when they go to school. Evidence Daniel shared about predicting the future included his sharing of a list of hard trends that he shared back in 1985. The list included networking, virtualization and mobility. His point – the list hasn’t changed at all and every item is still relevant.
His recommendations for us: “Direct your future or someone else will.” He suggested that we all spend one hour a week unplugging from the present and thinking about the future.
The Continuing Journey To Become A Strategic Advantage – This session was conducted by Anthony (Tony) Krasinski, Director of IT Service Management for Erie Insurance Group. Tony shared that the issue at Erie was not a process problem but rather a leadership problem. The goal of their journey was to move from being considered a weakness to a strategic advantage in three years. They spent the first year of their journey focusing on the people with three key activities: leadership breakthrough training, limiting what they delivered until they got it right and enforcing their processes (compliance). Their critical success factors are operational stability and delivering on their commitments. In year two, they accelerated delivery, implemented ‘right size, right mix’ and the ‘how’ of leadership. With the ‘right size, right mix’ effort, they tackled an issue with too many job descriptions and job levels. As an example, they had 55 position descriptions for analysts in IT. The problem – they were too specialized. They resolved the issue by creating job families. They eliminated negativity with their people about these updates when they announced that no one would have any financial changes based on the mapping and no one would lose vacation time based on their mapping. As part of the organizational effectiveness program (right size, right mix), they:
- organized better to be more effective
- eliminated specialization
- Decentralized functions
- Established a team of project managers in operations focused only on operations
- Redesigned operations
- They separated engineering, administration and support
- Coupled architecture and engineers
- Set the expectation – the engineering and ops teams must collaborate
The result – they delivered more than they were asked for in 2014 and their relationship with the business is better than ever.
Moving from Problem Administrators to Problem Managers – this session was conducted by Joe Gallagher, Global Head of Problem Management for Bank of New York Mellon. This was an excellent session with so much practical advice, there is simply too much to put here. Some key take-aways:
- Their key pain point was stability. After three years with problem administrators, they had seen no true improvement in stability.
- The process was cumbersome and not effective. They needed to leverage automation as much as possible and make it an easy, sustainable process.
- The existing process was too slow with an average of 28 days to complete root cause analysis. After the implementation of problem managers, they reduced the number down to 8 days!!
- The backlog of items was large and they needed to trim it down.
- Accountability for RCA was decentralized in the existing process but was moved to a centralized team as part of the movement. This proved to be much more effective.
- They set their goal to reduce major incidents by 20% and amazingly achieved a 38% improvement with the movement.
IT Transformation at Prudential Group Insurance: The ITSM & DevOps Mashup – this session was conducted by Chris Flanagan, VP of ITSM & Operations. Chris talked about how their team’s operated essentially as ‘islands’. They were not good at addressing end-of-life issues and even worse, they had no plans to address the issues. Their engagement model was essentially a ‘friends and family’ model so if you knew the right person, you could get your effort going but if you didn’t, tough luck. Their operational model was not good either. As part of their improvement initiative, they choose a plan/build/test/run approach. They started addressing the ‘silo’ issue between dev and ops by having the teams share what the value proposition of each of their teams was. The goal was to ‘find a way to go fast with quality.’ Chris shared their story and suggested that we pick which devOps capabilities make sense for our own organizations. At Prudential, they chose continuous integration and continuous delivery. Some take-aways Chris shared as ’10 things we wish we had known when we started’:
- Principles matter
- Get a trail guide
- Small teams speed things up
- Develop a framework
- Pick one application to start with (preferably a web-based one)
- Tools are less important than results
- Software configuration management is hard
- Elastic provisioning is a nice to have, not a need to have
- It’s all about testing
- DevOps is a culture, not a technology
I’ll be blogging about the final day of the conference soon. Stay tuned.