How to Deal with Results from an Agile Retrospective? -
Have you ever heard a team complaining about results of a retrospective not being realized? I have. And it’s important to change something immediately after hearing it.
Agile Team Retrospective Activities: Starfish & Team Radar -
Variety in retrospective activities are definitely necessary. The more retrospectives I do, the more I’m getting tired of using the same method over and over again. And hey, this will most probably bore the teams I work with as well. Therefore it’s good to challenge the team AND you with new retrospective techniques. In the last weeks I tried out Starfish and Team Radar in retrospectives.
Lean Thinking is what I’m trying to learn and adopt at the moment.
This post moved to http://proessler.wordpress.com/2011/08/18/soft-agile-transition-slowly-from-nowhere-to-scrum/
It’s great to witness how a company changes from somewhat “old school-ish” to something agile-like: Last week we finally started with a Scrum of Scrum and it turns out to be working pretty well only after a few days.
This post moved to http://proessler.wordpress.com/2011/08/01/scrum-of-scrum-introduced-yes/
One of the principles behind the Agile Manifesto is maximizing the amount of work NOT done! If you really manage to do it, it is very liberating. It actually sounds very easy but is really hard to get it started and keep it going.
This post moved to http://proessler.wordpress.com/2011/07/25/not-done/