InfoQ Homepage Software Craftsmanship Content on InfoQ
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Simplicity, Please - A Manifesto for Software Development
An unrelenting and breathless rush to market is quietly driving your company to the brink of extinction. Maybe it’s time to rethink how you design and write code. Investment in simplicity is investment in speed. Simplicity is also the mother lode of intellectual property — and a competitive advantage almost impossible to regain once lost.
-
Who is in Charge of Quality in Software Development
As silos break down, the whole team is responsible for quality in software development. As process more and more defines people and processes, how can you strive for better quality of releases?
-
Test Automation in the World of AI & ML
An in-depth look at the criteria & requirements for Functional Test Automation in the agile world, and the capabilities you should build in your custom framework, or should exist the tools you choose. Anand Bagmar explores aspects like readability, reuse, debugging / rca, CI, Test Data, Parallel Execution, integration with other tools & libraries, free Vs open-source and support.
-
Q&A on the Book Refactoring - Second Edition
The book Refactoring - Second Edition by Martin Fowler explores how you can improve the design and quality of your code in small steps, without changing external behavior. It consists of around seventy detailed descriptions of refactorings, including a motivation for doing them, the mechanics, and an example.