Modern software-based services are implemented as distributed systems with complex behavior and failure modes. Many large tech organizations are using experimentation to verify such systems' reliability. Netflix engineers call this approach chaos engineering. They've determined several principles underlying it and have used it to run experiments. This article is part of a theme issue on DevOps.
Fujitsu UK is using a large number of processes and methods which have developed over the period of many years. Looking for a way of combining agile and traditional methods, they became aware of SEMAT and the Essence Kernel. This article explores how they applied SEMAT and Essence to systems engineering, and used it to look at the whole programme of work across all disciplines.
This article is intended for newbies and agile sceptics who want to challenge their take on agile. It provides 10 ways to successfully fail your agility, implying that by replacing these practices with ones that do the opposite, you will increase agility and improve the odds of being successful.
In the book The Lean IT Field Guide Mike Orzen and Tom Paider explain how to initiate, execute, and sustain a Lean IT transformation.
The Art of Scalability, by Martin L. Abbott and Michael T. Fisher, is a book on scaling organisations to adapt to web scale growth of their products and services.
The book Devops in Practice: Reliable and automated software delivery by Danilo Sato provides a hands-on approach for implementing continuous delivery and DevOps practices.
An interview with Craig Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility.
Experiments and lessons from the engineering organization of King Digital Entertainment showing how continuous improvement of HR-related processes and topics fosters a creative and innovative culture. 4
Common System and Software Testing Pitfalls provides 92 pitfalls that make testing less efficient and effective. It aims to help you to avoid falling into pitfalls or dealing with the consequences.
In this article, authors discuss the Reflective Agile Learning Model (REALM) that embeds reflective practice into the iterative and agile software engineering development cycle.
This article is the first article in a series on managing remote teams, which shares experiences in developing a process for remote collaboration.
This article explains why it is inherently wrong to set up software metrics to try and 'improve' the software development process, and offers some alternatives. 3