Re: [scrumdevelopment] Re: Retrospective instructions?
- Hello, George. On Tuesday, September 2, 2008, at 6:08:11 PM, you
> dalermatthews wrote:An example would come in handy right about now.
>> The Agile Retrospectives book has lots of useful ideas on how to get
>> the information you want from retrospectives. Essentially it is just
>> the 3 questions though. What went well? What didn't go well? What can
>> we do better next time?
> I beg to differ. I think those three questions barely scratch the
> surface of successful retrospectives. And I've seen many situations
> where those three questions were totally inadequate to generate any real
I don't do force. People should do what they want, and experience
How are productivity and personal preference balanced?
You get to decide.
- --- In firstname.lastname@example.org, Ron Jeffries
> Yes. I have some dear friends who used SAMOLO and loved it. I wasIt seems to me this has less to do with clever mnemonics or
> not as impressed as they were. For reasons such as you're referring
> to, and others, it seemed to me that important things just couldn't
> be brought up.
retrospective techniques (which are certainly useful tools) and more
to do with the fact that retrospection is not equivalent to
introspection either individually or collectively. A tendency towards
superficial examination of past history without a requisite amount of
serious introspection cannot have a significant impact on future
development. As with all things Scrum related, teams will get out of a
retrospective whatever they put in. The trick for the ScrumMaster or
coach is to inspire them to be more introspective individually and as
a group. I don't think there is a mnemonic or prescriptive technique
that provides that.