InfoQ Homepage Agile Content on InfoQ
-
Product Goals, not Sprint Goals
There is a myth that Sprint Goals are a way to focus Scrum teams towards a common purpose, and without Sprint Goals, teams would end up building a disparate list of Product Backlog Items, every Sprint. This is in fact not only untrue, the reality is the exact opposite, that Sprint Goals are in fact a distraction and would only deliver parts of Product Goals.
-
How SwissLife France’s Enterprise Architects Used Lean to Raise Their Level of Influence
This article shows how Lean has been successfully applied to its own activities by an Enterprise Architecture team. Making the flow visible, loving problems and having fun solving them, and welcoming voice of the customer feedback were some of the practices that helped the team navigate the flow. Lean allowed them to better live to their purpose, both individually and as a team.
-
How Structure, Process, and Rules Make People Free
There is a widespread belief that rules, structure and processes inhibit freedom and that organizations that want to build a culture of autonomy and performance need to avoid them like the plague. In this article, we want to debunk that myth. Nurturing a culture of freedom and responsibility at scale is an organizational design problem
-
InfoQ Editors' Recommended Talks from 2019
As part of the 2019 end-of-year-summary content, this article collects together a list of recommended presentation recordings from the InfoQ editorial team.
-
Author Q&A: The 4 Stages of Psychological Safety
Dr Timothy Clark has published the book The 4 Stages of Psychological Safety in which he explores how psychological safety is enabled in groups and how they progress through the four stages of inclusion safety, learner safety, contributor safety and challenger safety and why achieving challenger safety is so important for creativity and innovation
-
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.
-
On Uncertainty, Prediction, and Planning
This article describes the software industry’s dismal history with predictions and planning in the face of uncertainty. It details some of the reasons why we fail to learn from our repeated mistakes. It suggests alternative approaches that are based on learning and include the strategy of hypothesis testing (Hypothesis-Driven Development) for deciding which features to deliver.
-
Did You Forget the Ops in DevOps?
Kris Buytaert, a DevOps pioneer, takes us through his journey in the last 10 years of helping organizations go through the adoption hype cycle and sorting out misunderstandings in their transformations.
-
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 Mastering Professional Scrum
The book Mastering Professional Scrum explores how using the Scrum values and focusing on continuous improvement can increase the value that Scrum Teams deliver. Stephanie Ockerman and Simon Reindl explain how professional Scrum teams can be focused and committed to delivering a Product Increment every Sprint, and how they leverage empiricism to improve themselves.
-
13 Practices for Better Code Reviews
When done incorrectly, code review can be irritating, excessively time consuming, and have little or no impact on code quality. However, if done well, it can improve the quality of code and reduce the overall time spent delivering features. This article provides several good practices regarding both technical and cultural aspects of code review.
-
Book Review: A Leader's Guide to Cybersecurity
A Leader's Guide to Cybersecurity educates readers about how to prevent a crisis and/or take leadership when one occurs. With a focus on clear communication, the book provides details, examples, and guidance of mapping security against what a business actually does. The book describes ways to align security with the motivation of others who may be security-agnostic against their own goals.