Change is the only constant in our world and “business agility” is demanded. Our old maps for running organisations are no longer valid; we need new ones based on systemic thinking. This second article from a series on Leading Self-Organising Teams discusses why we need self-organising teams.
We all want to have confidence in the software we create. We know that testing plays an important role. Assuming we've overcome the hurdle of learning the various ways to test, what's still missing that inhibits us from having confidence in what we do? How do we go about leading a culture of effective testing?
Recently, there has been more and more interest in Kanban as a simple and effective method for managing software development. But how does Kanban work? This article digs into details to try to understand the dynamics of Kanban in the light of queuing theory. It analyses three case studies to reveal some basic and insightful ideas about how Kanban works.
Nadja Macht, Flow Manager and Coach at Jimdo, talks about balancing flow and slack time in teams, doing visual management with Kanban boards and deploying retrospectives for continuous improvement.
The book Becoming a Catalyst by Len Lagestee aims to help Scrum Masters, Agile coaches, and project managers to accelerate the culture change that is needed when an organization is adopting agile.
A story about implementing Lean Software Development in a software vendor house with seven major changes that have helped the R&D department to remove waste from their software development process. 4
This first article from a series of on Leading Self-Organising Teams explores what self-organising teams are. 3
This is a story about four cross-functional scrum/DevOps/feature teams delivering and managing a business-critical 24/7 system used by vessel-traffic services operators and many other users.
This article presents an agile approach to the production of different types of documentation, in different phases of an application lifecycle, and adapted to the different target audiences.
There are ways to obtain sustainable pace beyond scrum that can help stem the increasing number of failing scrum projects, with a backlog-item-oriented workflow treating sprints as iterations.
Rally Software and Carnegie Mellon's Software Engineering Institute (SEI) are researching the impact of agile software development practices. An interview wit Larry Maccherone and Jim McCurley. 1
Ahmad presents a set of techniques that can be applied in strategic workshops or an initial product backlog session. He tells the story of a workshop where these techniques were used in Egypt.