There are several techniques that can be used to promote communication in a Scrum team, like for instance the Dialogue Sheets that are proposed by Allan Kelly for retrospectives. In this blog post, Alan Dayley discusses how silence is a powerful tool for management and the need for constructive conflict.
Thom Roach shares with us in this blog post the metrics that he includes in iteration summary reports. The three main statistics he uses are Iteration Statistics summary, Iteration Cumulative Flow and Team Velocity Chart.
The Dialogue Sheet is a new technique for team retrospectives in Scrum Projects. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.
Marc Löffler shares in this blog post 11 hints to improve all the Scrum meetings. He discusses daily stand-up meeting where he suggests to show colleagues what your currently working on instead of just talking about it. He also make proposals to improve the sprint planning, sprint reviews and retrospectives.
In this blog post, Marc Löffler shares a checklist of items and best practices that should facilitate the a successful retrospective for a distributed team. Even if virtual retrospectives are fine, he suggests that distributed team should meet personally on a regular basis, if possible every two retrospectives.
This article proposes four “smells” that might indicate that you’re not optimally practicing whole-team approach in your Scrum software development project
Each Scrum Sprint should produce two results: 1) A product or service which is an increment of functionality closer to delivery and 2) a better, happier, more productive team. Peter Stevens explains that the retrospective is the primary opportunity for achieving the second result.
Scrum Expert Copyright © 2009-2024 Martinig & Associates