Inspired by NASA astronaut training for solving complex, evolving problems on the fly, the Chaos Lottery is one approach to testing the resilience of a Scrum team. This is a story about knowing what you should do, and finding you are still not quite doing it.
The Product Owner is a key component of Scrum teams as the role a major influence on software development projects. It is however not always possible for the Agile team to get access to a full-time qualified Product Owner. This is why Marcelo Leonetti discusses in this article some situations where a Product Owner proxy could help Scrum teams solve some problems.
Agile and Scrum team formation is a natural human response to certain conditions. Once they exist, the formation process begins. This session looks at those conditions, and then looks at what other conditions need to be reached to progress through the different stages defined by Bruce Tuckman: Forming, Storming, Norming, and Performing.
As Agile has become a mainstream approach in software development, there are many books and discussions about its concepts and how to implement them. The book “Environment for Agile Teams” by Andy Brandt provides a different, and very interesting, perspective as it discusses the practical details of the everyday life of a Scrum team.
In small Scrum teams, it’s common for people to share roles such as Scrum Master / Tester / Dev but in a lot of cases there are conflicting interests. How can a Tester adequately test when as a Scrum Master the highest priority is assisting the team to deliver?
As an Agile Coach or Scrum Master do you want to add energy to your team that looks not enthusiastic or resists change? Is it possible to cause harm to your team even with proper Agile coaching? Yes, if you are working with tired, exhausted or even burned-out teams, they do need special treatment, usually counterintuitive to the coaches.
Agile approaches like Scrum recommend a “just enough” attitude in software development and this is also the case when you discuss tools. Ideally, you would work with a small team that is collocated, but this is not always possible and you might be running your project in a virtual mode with a distributed Scrum team scattered around the world.