InfoQ Homepage Software Craftsmanship Content on InfoQ
-
/articles/transformation-by-imagining-it-had-failed/en/smallimage/KICK-OFF-S-1606304485976.jpg)
Kick-off Your Transformation by Imagining It Had Failed
Large scale change initiatives have a worryingly high failure rate, the chief reason for which is that serious risks are not identified early. One way to create the safety needed for everyone to speak openly about the risks they see is by running a pre-mortem. In a pre-mortem, we assume that the transformation had already failed and walk backward from there to investigate what led to the failure.
-
/articles/book-review-accelerating-software-quality/en/smallimage/accelerating-cover-1604062444647.jpg)
Q&A on the Book Accelerating Software Quality
The book Accelerating Software Quality by Eran Kinsbruner explores how we can combine techniques from artificial intelligence and machine learning with a DevOps approach to increase testing effectiveness and deliver higher quality. It provides examples and recommendations for using AI/ML-based solutions in software development and operations.
-
/articles/search-code-quality/en/smallimage/code-quality-small-1602858727947.jpg)
In the Search of Code Quality
Software development process being a convoluted interplay of technical, business, sociological and psychological forces makes it very hard to understand. This leads to a multitude of myths and hypes. Recent scientific research challenges many commonly held beliefs and intuitions.
-
/articles/testing-boeing-flight-simulators-software/en/smallimage/testing-boeing-flight-simulators-software-s-1602167177160.jpeg)
Learning from Bugs and Testers: Testing Boeing 777 Full Flight Simulators
The aviation industry has developed the habit of scrutinizing every reported event in order to prevent another occurrence, to understand the root causes and suggest changes to design, process, or better training. This article goes over a couple of noticeable accidents and shows you techniques that could be applied to software development.
-
/articles/book-review-learning-to-scale/en/smallimage/learning-to-scale-1591652539968.jpg)
Q&A on the Book Learning to Scale
The book Learning to Scale by Régis Medina explores how to apply lean as an education system to scale companies and help people think about their work and learn together to create value. It provides an enterprise model built on how people learn and grow based on the idea that when people understand what they do and why they do it, they become better in what they do and the company moves faster.
-
/articles/book-review-leading-quality/en/smallimage/leading-feature-1590765165966.jpg)
Q&A on the Book Leading Quality
The book Leading Quality by Ronald Cummings-John and Owais Peer explores how to become a leader of quality, master strategic quality decisions, and lead engineering/QA teams to accelerate company growth. The book is intended for people who lead quality inside their companies, like C-suite executives.
-
/articles/okrs-autonomous-impact-teams/en/smallimage/Using-OKRs-to-Build-Autonomous-Impact-Teams-logo-1580132317346.jpg)
Using OKRs to Build Autonomous Impact Teams
To focus on outcomes rather than outputs, Meilleurs Agents uses the Objective and Key Results framework to align the whole company on what they want to achieve. Christopher Parola and Nicolas Baron gave a presentation at FlowCon France 2019 where they showed how they implemented the OKR method and turned their product and tech teams into impact teams.
-
/articles/candy-crush-QA-AI-saga/en/smallimage/candy-crush-saga-logo-small-1577439341467.jpg)
How King uses AI to test Candy Crush Saga
To be able to improve features in games which are constantly evolving, the challenge will be to scale tests to be on a par with new feature development. Automated tests are vital for King to keep up testing Candy Crush, therefore they are constantly looking for new improved ways to test.
-
/articles/book-review-team-topologies/en/smallimage/Book-Team-Topologies-l-1572527747801.jpg)
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.
-
/articles/unsolved-problems-foreseeable/en/smallimage/Categorise-Unsolved-Problems-in-Agile-Development-Premature-Foreseeable-logo-1571822458014.jpg)
Categorise Unsolved Problems in Agile Development: Premature & Foreseeable
Productivity decline and technical debt, as often seen in agile development, can be prevented by separating unsolved problems into premature and foreseeable. It shifts the discussion about unsolved problems from importance to likelihood. With small but essential adjustments, agile can be kept sustainable. With this insight, developer-architect differences and team psychology gaps can be bridged.
-
/articles/book-review-managing-technical-debt/en/smallimage/Managing-technical-debt-logo-1569408320780.jpg)
Q&A on the Book Managing Technical Debt
The book Managing Technical Debt by Philippe Kruchten, Robert Nord, and Ipek Ozkaya provides principles and practices that help you gain control of technical debt throughout the software development process and life of the software product.
-
/articles/test-automation-prevention-cure/en/smallimage/test-automation-prevention-cure-s-1556139023542.jpeg)
Test Automation: Prevention or Cure?
A lot of teams have the tendency to view test automation as a way of speeding up delivery of software, as this is often the perceived bottleneck within the team, but if they were to take a deeper look at their development practices as a whole, they may get better results.