InfoQ Homepage Retrospectives 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/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/agile-reflective-practice/en/smallimage/agile-reflective-practice-logo-1533075201973.jpeg)
Agile: Reflective Practice and Application
We explore how successful software development is based on the following three intertwining thought processes: Systems Thinking, Community Context and Reflective Practices. A majority of unsuccessful transformations result from a failure by members of the team to grasp that they are contributing to a larger system, or an unwillingness to learn how to improve, or that software is a team sport.
-
/articles/state-of-testing-report-2018/en/smallimage/state-of-testing-1530255125661.jpg)
2018 State of Testing Report
The State of Testing 2018 report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. It shares results from this year’s testing survey. InfoQ held an interview with the organizers of the State of Testing survey.
-
/articles/retrospectives-weak-stronger/en/smallimage/teams-1529076869412.jpg)
Retrospectives are Weak - Here is How to Make Them Stronger
This article explains why organisations settle for mediocre results from retrospectives and how a great coach can transform the results by bringing the real issues to the surface and creating an environment where a team can learn to trust each other, deal with conflict and experience extraordinary results.
-
/articles/book-review-improving-agile-retrospectives/en/smallimage/over-agile-1518494485086.jpg)
Q&A on the Book Improving Agile Retrospectives
The book Improving Agile Retrospectives by Marc Loeffler provides practices and approaches for doing agile retrospectives that support continuous improvement. According to Loeffler, agile retrospectives are workshops which need to be prepared and facilitated well in order to be beneficial to teams.
-
/articles/learning-unintended-failures-pattern/en/smallimage/logo-cm-1512460960455.jpeg)
Soft Skill Patterns for Software Developers: The “Learning from Unintended Failures” Pattern
Soft Skill Patterns describe human behaviours that effectively solve recurring problems. The "Learning from Unintended Failures" pattern helps us improve the resilience of a system after a failure. The pattern follows 4 steps: identify a failure, quickly resolve any immediate impact, analyse root cause and system behaviour during the failure, and finally generate and implement improvement ideas.
-
/articles/agile-approach-fits-context/en/smallimage/agil-series-1508534878617.jpeg)
Customize Your Agile Approach: Select Your Agile Approach That Fits Your Context
This is the first in a series of articles that will help you think about how you might want to customize your agile approach for your context. This article explores how to make agile approaches work for you: your work, your team, and your organization. It's about understanding the difference between iteration, flow, and cadence and when you might consider each to customize your agile approach.
-
/articles/book-review-great-scrummaster/en/smallimage/greatscrummaster.jpg)
Q&A on The Great ScrumMaster
In The Great ScrumMaster Zuzana Šochová explores the ScrumMaster role and provides solutions for dealing with everyday and difficult situations. She describes the #ScrumMasterWay, a concept which defines three levels of operation of ScrumMasters.
-
/articles/exercises-building-better-teams/en/smallimage/logo-agile.jpg)
Exercises for Building Better Teams
Have you ever seen a team perform so great that you wanted to join it? If you examine the values of such a team, you may discover a perfect balance of orientation on people and results. If you are trying to discover how far away your own team is from this state, read this article and try the exercises to find your own state of perfection.
-
/articles/agile-principles-over-rituals/en/smallimage/agile-logo.jpg)
A Focus on Agile Principles over Agile Rituals
When scaling agile principles through rituals it's important to constantly evaluate and evolve those rituals. This article provides examples of experiments that focus on the original intent when developing team behaviors. It shows how you can be aware of triggers that mean your team is not finding value in a ritual and what you can do to make things more visible.