DevOps is the seamless union of developers and operations working as one to facilitate high speed-to-market. It can be considered the approach of applying Lean or Agile to principles to infrastructure and operations. It breaks down silos within organisations and enables teams to move at a much greater pace to deliver software at scale.
“[DevOps is] a cross-disciplinary community of practice dedicated to the study of building, evolving and operating rapidly-changing resilient systems at scale.” — Jez Humble
In many organisations, DevOps is still massively misunderstood with dedicated departments clinging onto those silos under the gise of DevOps. …
As businesses fight to become more agile and stay relevant, technology has evolved to support it. Forget Docker, JAMstack is the next evolution in modern web development.
Technologies such as Docker will continue to play a huge part of our digital future but should become increasingly transparent to the majority of businesses and used behind the scenes. …
One challenge to successful product development is to do less work. To put this in context, it’s about removing wasted effort and becoming Lean. This isn’t a new concept, but it’s harder than it sounds.
“Simplicity — the art of maximizing the amount of work not done — is essential” — Agile Principle
The idea of not doing work to avoid waste is an Agile principle, but it’s also the foundation of the Lean philosophy.
Waste is unnecessary work that either adds no value or produces too much work at the wrong time. …
But how many people can say they have referred to the Agile manifesto before their first Agile project?
This article looks at the wider view of what Agile is, and why it can fail.
Back to basics. Agile is about delivering customer value and putting customer satisfaction first. It’s founded on 12 principles which support the manifesto.
In corporations, the term “enterprise” often instills a sense of importance, complexity, cost and scale. Likewise high-budget, high-profile projects often result in tech departments responding with enterprise-ready software solutions and infrastructure.
What this means is extensive planning, evaluation, procurement, and timeframes often of several years to “get it right”. The cost of building an enterprise-level solution in this manner is usually in the millions. The risk from failure is extreme.
Of course, enterprise-level solutions shouldn’t mean high-cost, high-risk and long timeframes. Often this is the result of a traditional mindset and organisational structure. …
Consultant, architect and thought leader. Over 20 years of industry experience, remaining hands-on with modern development practices and Cloud architecture.