Sep 16, 2009


Scrum recommends periodic retrospectives for continuous improvement (inspect and adapt).

I recently facilitated a release retrospective for a large project team*. In the next few posts, I will share my experience and learnings.

* This was no doubt a large project... ~ 20 team members distributed across New York, San Francisco, Atlanta, Bangalore, Mumbai, Dusseldorf, Paris that have worked together for ~ 2 years with multiple 3-month releases.

No comments:

Post a Comment