Scrum Agile Project Management

Giving Scrum Retrospectives Their Due Diligence

June 8, 2012 0

Scrum Retrospectives are not easy and this meeting is often the first one that will be canceled when there is some pressure to deliver a product. In this blog post, Mitch Lacey explains why retrospectives are so important in Scrum. He presents also some key components of an effective retrospective in a Scrum / Agile project and how to organize a retrospective meeting.

The Silence as a ScrumMaster Tool

May 23, 2012 0

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.

Metrics for Iteration Summary Reports

December 15, 2011 0

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.

A New Tool for Retrospectives

October 10, 2011 0

 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.

Improve Your Scrum Meetings

September 20, 2011 0

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.

A Checklist for a Distributed Retrospective

September 6, 2011 0

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.

Are You a Whole Team?

July 18, 2011 4

This article proposes four “smells” that might indicate that you’re not optimally practicing whole-team approach in your Scrum software development project

1 5 6 7 8