What exactly do we have to do to capitalise on self-organisation? How can we best support our teams? What special kind of leadership is needed? The third article from a series on Leading Self-Organising Teams covers what it means to lead a self-organising team.
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.
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. InfoQ interviewed Len about supporting people in adopting agile practices, what it takes to become a catalyst, and how catalysts can start and energize change initiatives.
A well managed backlog should contain a manageable set of Product Backlog Items (PBIs) that are of value to the customers & users of the resultant product. Keeping this list useful takes skill. 6
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.
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.
Brian Rabon wrote the book Scrum for the rest of us which describes Scrum without using information technology jargon aimed at all kinds of teams that want to use Scrum for managing projects.
InfoQ interviewed Tommy Norman about his introduction training on Scrum, roles, artifacts and events, User Stories and collaboration in teams, and on-line resources for learning more about agile.
An interview covering what Software Engineering Method and Theory (SEMAT) initiative adds to agile and how SEMAT can be used when organizations adopt agile.
An interview with Tim Ottinger and Ruud Wijnands about the way that organizations adopt agile, services provided by the industry, and the importance of technical practices and craftsmanship in agile.