I’m going to admit something to you as an Agile coach. Clients that I work with make mistakes, and I can’t prevent them all. I don’t even try to.
Here’s another post in the series of how the book Thinking, Fast and Slow has made an impact on me. This time, I’d like to concentrate on the consequences I see for teaching classes. For starters, I’m glad to see that the book compliments the things I learned from Sharon Bowman’s Training from the Back of the Room, as well as from Chip and Dan Heath’s book Made to Stick.
Agile product discovery works in tandem with delivery. The best effect comes when it includes the whole team, is done deliberately and continuously.
The video includes the common roles, artifacts and ceremonies involved in discovery. While this is the first of many iterations to come, I hope you enjoy! What questions do you have, or feedback you would like to provide?
How do you get started with discovery on your Scrum team?
Participants learn how to improve practices like user research and interviews, persona sketching, design studio, prototyping and story mapping by actively using them in a class. At the end of the class, participants see a different way of working. Then the discussion turns to something like- While this is undoubtedly is a better way to work, it’s so different than what we do today. How can we do this stuff where we work? How do you get started?