InfoQ Homepage Stories & Case Studies Content on InfoQ
-
Adding Security to Testing to Enable Continuous Security Testing
Teams can be trained by security experts to become able to identify areas to add security testing in the test process and add security checks as part of functional test automation. This can lead to continuous security testing where security defects can be spotted at an early stage with higher security testing coverage in every release.
-
Shifting Quality Left with the Test Pyramid
Shifting quality left means building in quality much earlier in the software development cycle, rather than testing for quality after completion of development. Using the test pyramid model, a project was able to move testing towards earlier stages, thereby finding defects that caused integration issues earlier in development.
-
Experiences from Testing Stochastic Data Science Models
A data science model is a statistical black box; testing it requires an understanding of mathematical techniques like algorithms, randomness, and statistics. To validate data science models you can use thresholds to handle output variance.
-
Migrating a Monolith towards Microservices with the Strangler Fig Pattern
ScholarPack has migrated away from its monolith backend using a Strangler Fig pattern. They applied incremental development and continuous delivery to target customers’ needs, in the meanwhile strangling their monolith.
-
Using Agile with a Data Science Team
Agile helped a data science team to better collaborate with their stakeholders and increase their productivity. As priorities became clear, the team was able to focus and deliver. Buy-in of the data science team by taking them through a journey of agile was crucial to making it work.
-
Applying a Zero-Bug Policy at Redgate
A zero-bug policy is a simple yet effective bug management system that can help you avoid being buried deep in months or sometimes even years-old bugs. Any bugs you agree are serious enough for you to fix, you fix right away, and any other bug will not be fixed and closed. Tom Walsh spoke about how Redgate Software applied the zero-bug policy at Lean Agile Exchange 2020.
-
Experiences from Using a Disciplined Approach to Change
When a company embraces the agile path, the first question is: “Where do I want to go?” and not “What is the right framework to do agile?” A disciplined approach to change can help you to choose from possible practices such as a “design pattern book” for agile transformation, and to identify when a practice is promising and when the current context is not the most favorable for it.
-
Learnings from a Project That Went from Heaven to Hell
Maja Selmer Megard, project leader and department manager at Kantega, shares her experience from a project that at first sight seemed to be a perfect fit in all regards, but ended up as the most exhausting, conflict-ridden project she has been in.
-
Cloudflare’s 27 Minutes Outage Explained
Cloudflare recently suffered a partial outage, which lasted for 27 minutes. This outage caused 50% of traffic drop across the network.
-
Building a Banking Infrastructure with Microservices: QCon London Q&A
In a few years, the number of microservices has grown from 100 to 1600 at Monzo, and it continues to grow. Microservices are split when responsibilities grow, or merged when services are tightly coupled. Engineers can generate, deploy, scale and monitor their own services using code generation.
-
Making Distributed Organizations More Effective
An autonomous team model with teams organized around geographical or time-zone proximity can make a distributed organization more effective. With the Reverse Conway Maneuver you can deliberately add or remove bottlenecks to better support the designs you are trying to build.
-
Volkswagen’s Journey towards a Software-Driven Company
Volkswagen is changing their working methods for software development, where they focus on regaining their own development skills and developing new products based on new technologies and methods. The technologies used are decided on by the teams independently.
-
How N26 Scales Technology through Hypergrowth
As N26 grew fast, they had to scale their technology to keep up. This meant scaling not only their infrastructure, but also their teams; for instance, they had to decide how to distribute work over teams and what technology to use or not use. Folger Fonseca, software engineer and Tech Lead at N26, shared his experience from scaling technology at N26 at QCon London 2020.
-
Involving Engineers in Incident Management: QCon London Q&A
Learning from past incidents can increase engineers' confidence in handling live incidents and convincing them to join the on-call team. Samuel Parkinson spoke about how we can benefit from past incidents and encourage engineers to get involved in incident management at Qcon London 2020.
-
Trust in High Performing Teams: QCon London Q&A
High-performing teams flourish in a culture of trust and safety. It’s important that trust come both from within and outside of the team, in order to avoid isolating teams from their stakeholders. Stephen Janaway shared his experience with trust in high performing teams at Qcon London 2020.