The end of the year if often the time for performance reviews. Should you still do this practice when you have Scrum Agile teams where the global results should be more valued than the individual peformance?
Shifting responsibilities from a “command and control” organization towards self-organized teams is not easy. In her article “Managing Product Teams for Success”, Teresa Torres discusses the challenges that you face when you try manage product teams by outcomes.
The change required by Agile and Scrum isn’t simple. This talk presents the tools provided for six teams and they were enabled to build the foundations for safe continuous learning themselves. Most people in agile and lean are involved in change somehow.
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.