InfoQ Homepage Business Content on InfoQ
-
Book Review: Site Reliability Engineering - How Google Runs Production Systems
"Site Reliability Engineering - How Google Runs Production Systems" is an open window into Google's experience and expertise on running some of the largest IT systems in the world. The book describes the principles that underpin the Site Reliability Engineering discipline. It also details the key practices that allow Google to grow at breakneck speed without sacrificing performance or reliability.
-
Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!
Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.
-
Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
-
Virtual Panel on Bimodal IT
Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.
-
Respect Your Organisational Monoliths
There is a lot of information about DevOps, the technology, the culture, the behaviour. There is not a lot of information about tackling DevOps in large enterprises and there is certainly very little about tackling DevOps in large financial organisations. This article presents lessons learnt rolling out DevOps in a large insurance organisation.
-
WTF requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
Waterfall Requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
Author Q&A: Decoding Silicon Valley
Jon Baer and Michelle Messina have written a book exploring the secrets to success in Silicon Valley - what it takes for a startup to succeed. They look at the culture, history and stories which show how and why the Valley works, and provide guidance for prospective entrepreneurs who are considering setting up in the Valley, or elsewhere. They spoke to InfoQ about the book and their ideas.
-
Stop Measuring Turn Around Time
Are you patting yourself on the back for remarkable turn around times while simultaneously neglecting your customers? It's tempting to think that timeliness matters when in fact it rarely does. Stop measuring turn around time and start learning what matters to customers.
-
How to Deal with COTS Products in a DevOps World
Mirco Hering explains why we shouldn't leave COTS products (and the people working on them) left behind in a DevOps world. With creative solutions we can apply good practices from custom software. This leads to a significant effort reduction in the long term.
-
Don't Break Your Silos - Push Out the Silo Mentality
Organizational silos are a serious hurdle for many companies out there. They may cause a wide variety of problems if not dealt with accordingly. Silos may not need to be broken if you manage to push out the mentality that comes with them by creating ventilators. The first step towards dealing with the silos is to learn more about them and familiarize yourself with the best practices against them.
-
A Letter to the Manager: Release the Power of Your Agile Teams
Agile is both simple and hard – and success depends on managers creating a suitable environment for their teams. Here a coach’s experiences from several agile transformations are made into concrete recommendations for strengthening agile teams. To create and sustain high-performing agile teams, these points are fundamental.