InfoQ Homepage Continuous Improvement Content on InfoQ
-
/articles/book-review-toyota-kata-agile/en/smallimage/level-up-agile-with-toyota-kata-logo-1568960227176.jpg)
Q&A on the Book Level up Agile with Toyota Kata
In the book Level Up Agile With Toyota Kata, Jesper Boeg explores how to apply Toyota Kata to drive improvement in organizations that are using or striving to use agile ways of working. He shares his experience from combining agile with Toyota Kata to enable organizations to keep improving towards their goals.
-
/articles/scrum-sistema-producao-toyota/en/smallimage/scrum-toyota-production-system-s-1564491117992.jpeg)
Scrum & The Toyota Production System, Build Ultra-Powerful Teams
How to use the Toyota Production System, as a knowledge-building system, to reveal learning topics on which to work to develop outstanding Scrum teams for exceptional results.
-
/articles/metrics-agile-teams/en/smallimage/Meaningful-Agile-metrics-s-1561036346084.jpeg)
The Importance of Metrics to Agile Teams
This article outlines the importance of and proposes meaningful Agile metrics for teams seeking to raise overall performance and whose members seek to continuously self-improve. It emphasizes that team members should democratically agree and manage these metrics. It also advises what to look for in tools that track performance against agreed metrics over time.
-
/articles/continuous-improvement-heartbeat-devops/en/smallimage/continuous-improvement-heartbeat-devops-s-1558624249506.jpeg)
A Different Meaning of CI - Continuous Improvement, the Heartbeat of DevOps
This personal experience report shows that political in-house games and bad corporate culture are not only annoying and a waste of time, but also harm a lot of initiatives for improvement. Whenever we become aware of the blame game, we should address it! DevOps wants to deliver high quality. The willingness to make things better - products, processes, collaboration, and more - is vital.
-
/articles/mitigate-pain-getting-giving-feedback/en/smallimage/mitigate-pain-getting-giving-feedback-s-1558074717961.jpeg)
How to Mitigate the Pain of Getting and Giving Feedback
Companies that encourage open and honest feedback do better than companies that do not. Nonetheless, giving feedback is difficult because social and physical pain share some of the same neural circuitry. Hence, feedback can feel physically painful, as Sarah Hagan discusses in her 2018 QCon San Francisco talk . Hagan uses scientific research to demonstrate how to give feedback properly.
-
/articles/book-review-evidence-based-management/en/smallimage/book-review-evidence-based-management-s-1552675366460.jpeg)
Q&A on the Book Evidence-Based Management
The book Evidence-Based Management by Eric Barends and Denise Rousseau explores how to acquire evidence, appraise the quality of the data, apply it in your management decisions, and assess the impact of your decisions.
-
/articles/great-engineer-needs-liberal-arts/en/smallimage/great-enginners-need-liberal-arts-small-1552323587808.jpg)
A Great Engineer Needs the Liberal Arts
Much of what helps you become a great software engineer, and create outstanding software that people want to use, comes from outside the world of STEM. The ability to effectively analyze a problem, evaluate different options, and engineer a solution requires skills taught in the liberal arts.
-
/articles/observability-driven-development/en/smallimage/observability-driven-development-s-1548787445395.jpeg)
Observability-Driven Development for Tackling the Great Unknown
How does observability-driven development differ from monitoring? As our distributed systems become increasingly more complicated and as our silos break down for DevOps testing, automation, and efficiency, ODD arises as a superset of monitoring to understand your code’s unknown unknowns. Includes insights from Honeycomb Founder Charity Majors.
-
/articles/keys-successful-pre-mortem/en/smallimage/keys-successful-pre-mortem-s-1543276868815.jpeg)
Three Keys to a Successful “Pre-Mortem”
Talking about what might go wrong acknowledges that many things are out of our control, and that we might mess up the things which are within our control. To have this conversation safely involves a structured activity called a pre-mortem. If held with some regularity, and always with creative problem solving time at the end, it can build a safe space for adaptation in the face of adversity.
-
/articles/book-review-code-wisdom-crowd/en/smallimage/code-with-the-wisdom-of-the-crowd-s-1541502857848.jpeg)
Q&A on the Book Code with the Wisdom of the Crowd
The book Code with the Wisdom of the Crowd by Mark Pearl explains how mob programming can be used to collaboratively solve problems. It also provides scenarios to fine-tune and adjust the interaction during mobbing for specific situations and advice for preparing mobbing teams and developing the skills needed for effective mobbing.
-
/articles/service-delivery-review-missing-devops-feedback-loop/en/smallimage/service-delivery-review-missing-devops-feedback-loop-S-1540549719258.jpg)
Service Delivery Review: The Missing DevOps Feedback Loop?
This article introduces the service-delivery review and answers questions like: does the team know what their customer values about their service? How can we regularly assess service fitness?
-
/articles/devops-modern-enterprise-book-review-interview-mirco-hering/en/smallimage/devops-modern-enterprise-1537450690782.jpg)
DevOps for the Modern Enterprise Book Review and Q&A with Mirco Hering
InfoQ reviewed Mirco Hering's "DevOps for the Modern Enterprise" book and reached out to the author for more insights on his experience, learnings and obstacles with transformations at large scale.