We run a sprint a month ago, 5 apocalyptic days where you would think all is going wrong. By Friday, we had a half-fake half-real web app running and realised 95% of it was crap after 5 testers. We made a product out of the other 5% and built it in 3 weeks :D
Epic book!
I just bought it from a store in Prague, Czech Republic. I am still reading it, but I like it so much. I would choose another title, tho, because "Sprint" for me, in the Agile World means slightly different thing :) Kudos!
We love this book! Adapted the method for the production of our interactive multimedia stories at oolipo and it works great. Besides that, we'll also use quick sprints for team processes. Highly recommended!
Report
We've been using Design Sprints in a large Malaysian telco, from 2016 to 2018, to rapidly test and validate new ideas to solving problems. Several issues come into play when adopting this in large traditional corporations:
a) resistance to trying new things
b) "sketching", "storyboarding" and other "new" exercises can often be seen as superfluous; some participants we've managed have looked at these parts as a waste of time
If your team is thinking of doing this for your organization, some tips include:
1. Do a mock run yourselves first, before facilitating others
2. Have the book handy as a reference, and refer to it often -- even when you've been doing these sprints for a long time
3. Be flexible with the sprint timing and agenda -- stakeholders in large corporations often don't have enough time to commit
4. Be ready to chop and change the daily agenda around, especially when stakeholders, deciders and experts change their schedule at the last minute
Pros:
Good framework to develop and test ideas. Book has lots of real-world examples of the Sprint in motion. Checklists are invaluable.
Cons:
Hard to get a design sprint right the first time. For practitioners, there's a tendency to skip some parts that may seem 'unimportant'.
Replies
Bend
Driveway
Sharechat
Threat Modeling e-book
oolipo
We've been using Design Sprints in a large Malaysian telco, from 2016 to 2018, to rapidly test and validate new ideas to solving problems. Several issues come into play when adopting this in large traditional corporations:
a) resistance to trying new things
b) "sketching", "storyboarding" and other "new" exercises can often be seen as superfluous; some participants we've managed have looked at these parts as a waste of time
If your team is thinking of doing this for your organization, some tips include:
1. Do a mock run yourselves first, before facilitating others
2. Have the book handy as a reference, and refer to it often -- even when you've been doing these sprints for a long time
3. Be flexible with the sprint timing and agenda -- stakeholders in large corporations often don't have enough time to commit
4. Be ready to chop and change the daily agenda around, especially when stakeholders, deciders and experts change their schedule at the last minute
Pros:Good framework to develop and test ideas. Book has lots of real-world examples of the Sprint in motion. Checklists are invaluable.
Cons:Hard to get a design sprint right the first time. For practitioners, there's a tendency to skip some parts that may seem 'unimportant'.