My session was in the first slot after the opening keynote on Monday morning, and I got the impression that some of the folks there hadn't fully grasped what the nature of a Discovery Session was, some other presenters found the same, I think. I believe that the origanisers might do more to help attendees understand better what's likely to be expected of them at such sessions for next year: they aren't tutorials. Of course, my session was a re-presentation of an XP Day session, which like Spa sessions (the other sort I'm used to presenting) tend to be exploratory, open-ended and interactive in a way that the typical Agile session seems not to be.
Outputs
As soon as I get unpacked from moving house I'll have the London reuslts here to compare with, but a selection of the Minneapolis results are here.The session was bookended by very quick brainstorm to try an capture any change in the attendees thinking after the discussions and work with the lego.
Before
|
|
- Have an idea of what possibilities your customers may need to explore
- Not for conventional projects, developers know too much business and not only code by success criteria
- provide guide rails for teams to make decisions within
After
|
|
Some conference wiki also bears some comments on the session.
