On the topic of retrospectives, I would like to revisit the take a step back. Others already mentioned reviewing what worked and what didn't from a development and process perspective.
My favorite retrospective exercise which some hate and some love is a brainstorm around the theme, kill our company. What market changes could make us irrelevant. If you were a startup or competitor what would you do to make our company or product irrelevant. Two things that always concern me with agile teams, i.e. burnout because of continual release (especially from folks not used to the cadence) and tunnel vision... Hmmm... Free time might be the best practice to ensure overall product quality... Hackathon or 20% time might be the next best thing... -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
