Reports and Insights

We produce reports and whitepapers based on our industry experience and research. We regularly attend industry events (conferences, meetups, panel discussions) and these events inform our research and reports.

We have produced research reports for some of the largest organisations in the world, helping them to assess market conditions, IT/delivery strategy, and organisation design.

Collaborate with us on content


report tools cover

How to choose tools for DevOps and Continuous Delivery

Optimizing software tool selection for learning, collaboration, automation, and team dynamics

Modern approaches to software tool selection go way beyond the simple checklists of yesteryear.

When choosing tools for DevOps and Continuous Delivery (CD), high-performing organisations know to take into account the social dynamics of the organisation and the trajectory of the rapidly-evolving public cloud vendors.

Learn how to:

  • Choose tools in a way that enables collaboration
  • Favour tools with APIs for automation
  • Understand the learning challenges for staff
  • Avoid special tools that exist only in one environment
  • Making use of Conway’s Law for tool choices

In this report, we help you to choose tools in a way that emphasises collaboration, automation, learning, reproducibility, and the relationship between teams and software (Conway’s Law).

Publication date: December 2017

Download the report


whitepaper cloud cover

Whitepaper: changes to technology & teams needed for modern software systems

‘Cloud’ changes everything for organisations building and operating their own internet-connected software systems. However, many organisations are unaware of the scale and nature of the changes in technology and teams needed to take advantage of cloud in order to remain current and competitive.

Learn how:

  • Faster delivery comes at a price worth paying
  • Operability should be a first-class concern
  • Team structures dictate systems architecture

Techniques and practices such as Continuous Delivery and DevOps work well precisely because ‘hand-over’ between teams is avoided in favour of in-team responsibility for both innovation and improvements based on feedback from the software in operation. Such approaches may not be cheaper in terms of head count, training, or salaries, but the resulting approach – seeing IT as ‘value-add’ – can be much more effective than one that sees IT purely as a cost centre, as recent studies by Gartner, Forrester, and others have shown.

Publication date: January 2015

Download the whitepaper


DevOps perspectives II

Report: DevOps Perspectives II – Ideas, insight and direction from DevOps leaders

in collaboration with CA, Inc (and other contributors)
[The] need to grasp the DevOps opportunity is an immediate imperative for all technologists if we accept that we are in the middle of what we now call the application economy – a place where customers are far more likely to experience your brand and interact with your enterprise through a software application than a living person.

Learn:

  • Six habits of the effective DevOps practitioner
  • ITIL: help or hindrance
  • Practical steps for joining up Agile + ITIL

Ensure that the right kind of collaboration is set up between Dev and Ops teams, and shared tools are used effectively in order to reduce Continual Service Improvement feedback loops timings to minutes or hours, rather than days or weeks. How do you reward failure in the right way? — Matthew Skelton

Publication date: February 2015

Download the report