Better Performing IT Results in Better Business Value


IT performance and well-know DevOps practices, such as those that enable continuous delivery, are predictive of organisational and business performance.

DevOps

How IT performance is measured? the most used criteria is measured in terms of throughput and stability. The individual measures that make up IT performance are:

  1. Deployment frequency
  2. Lead time for changes
  3. Mean time to recover from failure

Bear in mind DevOps has always been about culture, not just about tools and processes. Healthy cultural practices and norms that characterise high-trust organisations are required for the successful implementation of agile methodologies, these are: good information flow, cross-functional collaboration, shared responsibilities, learning from failures and encouragement of new ideas.

Practices Leading to Increased Deployment Frequency

  1. Continuous delivery ensures that your software is always in a releasable state that can be performed on demand.
  2. Capability for easily recreate environments for testing and troubleshooting.

Practices Leading to Reduced Lead Time for Changes

  1. Version control as the ability to get changes into production repeatedly in a reliable, low risk way.
  2. Reliable and comprehensive set of automated tests, so code is releasable without lengthy integration and manual regression testing cycles.

Practices Better Mean Time to Recover

  1. Version control, when an error is identified in production, devs can quickly either redeploy the last good state or fix the problem and roll forward.
  2. Monitoring system and application health so is easy to detect failures and identify the events that contributed to them.

Implementing continuous delivery means creating multiple feedback loops to ensure that high-quality software gets delivered to users more quickly. Continuous delivery requires that developers, testers, designers and UX, product and operations people collaborate effectively throughout the delivery process.

Continuous integration is a development practice whereby developers routinely merge their code into build servers with version control systems. Each change triggers a set of quick tests to discover serious regression, which developers must fix immediately.

Six Recommendations to Apply when working with DevOps:

  1. work with other teams and build empathy, build bridges, understand challenges and put yourself in the shoes of the others
  2. build trust between teams, trust is built on kept promises, open communication, and behaving predictably even in stressful situations
  3. actively seek, encourage and reward work that facilitates collaboration, make sure success is reproducible
  4. learn by sharing knowledge & create opportunities and spaces to share information
  5. create a training budget, and advocate for it internally
  6. make it safe to fail

Read more: Puppet Labs. “2014 State of DevOps Report“. PDF report.

Stop Planing and Start Acting


Being creative and innovative is not enough, you still need to act.

Many people get stuck between wanting to act and taking action. Professors Bob Sutton and Jeffrey Pfeffer call this the “knowing-doing gap”: the space between what we know we should do and what we actually do. This cal lead the company to have a paralysis by analysis, this is when talk becomes a substitute for action.

Yoya, Do or do not there is no try

A corporate example of paralysis by analysis is Eastman Kodak company, in mid 1990’s the leadership team had a deep expertise and intellectually understood that the future of photography was digital, Kodak had actually invented the digital camera in 1975 and later they pioneered the world’s first megapixel sensor. So why all this knowledge and technology was not marketed by Kodak, why they didn’t take action?

Kodak had basically owned the consumer and professional photography market for at least 100 years, with in some segments having a market share as high as 90%. Facing strong global competitors in the digital market like Cannon, Sony, Nikon, Kodak knew that it will struggle and the management team had fear of failure.

What happened to Kodak is not due to lack of information or leadership expertise; its failure was to not being able to turn insight into action, as a result one of the most important corporations lost its way.

To achieve goals, to overcome obstacles in your way, you have to be focused on getting it done now. As Yoda (from Stars Wars) put it to Luke Skywalker “Do or do not. There is no try”.

8 tips to turn insight into action:

  1. Start with the end goal in mind
  2. Fight procrastination by adopting “do it now!” as your mantra
  3. Don’t plan out everything you need to do to finish a project, just focus on the very next thing you need to do to move it forward
  4. Assign a set amount of time per day to work on a task or project
  5. Un-clutter, be able to access what you need, when you need it, without breaking the flow of your work to find it
  6. Break down large goals into smaller steps to make the journey to completion more doable
  7. Prioritise, certain tasks will always hold more priority than others
  8. Stop chasing perfection, getting things done shouldn’t involve mastering perfection

* Image credit hitwallpaper.com