InfoQ Homepage Agile Techniques Content on InfoQ
-
2020 State of Testing Report
The 2020 State of Testing report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. It shares results from the 2020 testing survey organized by Joel Montvelisky from PractiTest, and Lalit Bhamare from Tea-Time with Testers.
-
Article Series: Data-Driven Decision Making
The Data-Driven Decision Making Series provides an overview of how the three main activities in the software delivery - Product Management, Development and Operations - can be supported by data-driven decision making.
-
Q&A on the Book Compass for Agility
The book Compass for Agility by Leila Rao describes an approach to create change in complex organizations and realize business agility. The compass consists of five phases: Ideation, identification, intake, in action, and introspection. Iterating with this five-step approach can develop internal capability for adaptability and reinvention.
-
Data-Driven Decision Making – Product Development with Continuous Delivery Indicators
The Data-Driven Decision Making Series provides an overview of how the three main activities in the software delivery - Product Management, Development and Operations - can be supported by data-driven decision making. In Development, Continuous Delivery Indicators can be used to steer the efficiency of the development process.
-
Q&A on the Book Agile Machine Learning
The book Agile Machine Learning by Eric Carter and Matthew Hurst describes how the guiding principles of the Agile Manifesto have been used by machine learning teams in data projects. It explores how to apply agile practices for dealing with the unknowns of data and inferencing systems, using metrics as the customer.
-
Three Key Success Factors for Improving Test Automation Outcomes
Test automation is crucial in the DevOps world and vitally important even if not taking a DevOps approach, and good test automation requires careful thought and design from the architecture onward. Tests need to be fully automated, and that automation needs to be stable; no test cases should fail for reasons other than issues in the system(s) under test.
-
The Evolution of Lean Thinking - Transitioning from Lean Thinking to FLOW Thinking
The Flow System provides a re-imagined system for organizations to understand complexity, embrace teamwork, and autonomous team-based leadership structures. It is a holistic FLOW-based approach to delivering Customer 1st Value. It is built on a foundation of TPS and LEAN, plus a new triple helix structure known as the DNA of Organizations.
-
Using Kanban with Overbård to Manage Development of Red Hat JBoss EAP
As planning the work for Red Hat JBoss EAP became harder and harder, Red Hat decided to adopt Kanban to make their development process more manageable, while maintaining a very high level of quality. They introduced Kanban in their distributed team and developed their own Jira add-on for visualizing the work, and added parallel tasks to their Kanban cards to simplify the workflow.
-
Q&A on the Book Team Topologies
The book Team Topologies by Matthew Skelton and Manuel Pais shows how to arrange teams within an organization to enable effective software delivery. It describes four fundamental team types and three team interaction patterns, and dives into the responsibility boundaries of teams and how teams can communicate or interact with other teams.
-
Testing Microservices: Six Case Studies with a Combination of Testing Techniques - Part 3
This article presents six real world use cases of testing microservice-based applications, and demonstrates how a combination of testing techniques can be evaluated, chosen, and implemented.
-
Velocity and Better Metrics: Q&A with Doc Norton
Velocity is not good for predictions or diagnostics, argued Doc Norton at Experience Agile 2019. It's a lagging indicator of a complex system which is too volatile to know what our future performance will be; it isn’t stable enough to be used reliably. We can use Monte Carlo simulation for forecasting, and cumulative flow diagrams to track work, see changes in scope, and spot bottlenecks.
-
Q&A on the Book Continuous Delivery in Java
The book Continuous Delivery in Java by Daniel Bryant and Abraham Marin-Perez was released nearly ten years after the original Continuous Delivery book by Dave Farley and Jez Humble, and more than 20 years after Java’s first release. Q&A with the authors to better understand from their experience why a book on Continuous Delivery specifically for Java and the JVM ecosystem was needed.