Regular, well-run retrospectives are critical to the ongoing improvement of an Agile team. In theory, scaling this process into an enterprise-wide activity sounds like a great idea. The reality of large scale retrospectives is quite different, however.
Selecting the wrong Agile metrics can actually block improvement — or make matters worse. Keep these five principles in mind when choosing metrics for retrospective improvement and forecasting.
Many Development Teams do not have the communication “muscles” to effectively speak to Stakeholders directly during Sprint Demos. We provide suggestions and a framework to strengthen the Development Team’s ability to make their Sprint Demos awesome.
The software architect has a vital role on the Scrum team. Find out what the architect’s four key areas of responsibility are, and get some top-notch recommendations for further reading.
Sprint Reviews can be dull affairs with little useful output. Instead of focusing solely on the demo, we recommend creating an environment focused on collaboration — and saving some time for celebration.
Remote Program Increment (PI) planning poses unique challenges to SAFe teams accustomed to working together in person. We propose solutions to get your team prepared.
Working from home is a new reality — one that can prove challenging for Scrum teams. ScrumMasters and other facilitators need new tools to make online meetings better.
Developing fully cross functional teams can dramatically reduce waste. In this essay we explore why cross functional teams are difficult to implement, and how to overcome common obstacles.
Scrum leaves a lot of room for teams to experiment, but what are the core elements that should not be changed? And what are the elements that can be tailored for your team?