Author(s): Jake KnappDownload
Publish: Published March 8th 2016 by Simon Schuster
ISBN: ISBN13 9781501121746
From three design partners at Google Ventures, a unique five-day process for solving tough problems using design, prototyping, and testing ideas with customers.
The startups that Google Ventures invest in face big questions every day: Where’s the most important place to focus your effort, and how do you start? What will your ideas look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution to a problem? Business owners and investors want their companies and the people who lead them to be equipped to answer these questions—and quickly. And now there’s a sure-fire way to solve their problems and test solutions: the sprint.
While working at Google, designer Jake Knapp created a unique problem-solving method that he coined a “design sprint”—a five-day process to help companies answer crucial questions. His ‘sprints’ were used on everything from Google Search to Chrome to Google X. When he moved to Google Ventures, he joined Braden Kowitz and John Zeratsky, both designers and partners there who worked on products like YouTube and Gmail. Together Knapp, Zeratsky, and Kowitz have run over 100 sprints with their portfolio companies. They’ve seen firsthand how sprints can overcome challenges in all kinds of companies: healthcare, fitness, finance, retailers, and more.
A practical guide to answering business questions, Sprint is a book for groups of any size, from small startups to Fortune 100s, from teachers to non-profits. It’s for anyone with a big opportunity, problem, or idea who needs to get answers today.
Some Reviews: 7,978 ratings 681 reviews in Goodreads.com
As a UXer working in Agile for more than 10 years, I initially turned up my nose at this book: After all, what new information could it really contain? Besides, there’s no way this methodology could work in a massive enterprise like my current employer.You see where this is headed, right? A colleague and I decided to give it a try, and we followed the book’s directions faithfully to run a sprint on a project that had been struggling to gain traction. At the end of the week, we had a tired but happy sprint team as well as a prototype concept, tested with actual users. Even better, when our leadership saw a concrete concept with positive user feedback, they gave our project a green light.
I’m officially a convert and recommend this methodology to anyone who wants to quickly move a project forward.
I have to say that I’m probably not the right audience for this book. The question which I usually have to answer have different character. I come to a connection with some product when it should be clear that it is a good idea to implement and it is me who have to decide how to implement it. Whether the implementation way is correct is usually verified by a prototype (as in this book) but with a different focus and with a different test audience. That said I cannot immediately verify described ideas that they are truly working. All suggested approaches sounds reasonable and when I will be involved in some product decision I would definitely tried it. I liked that you can take some components from the whole process and apply just them. I have couple candidates which could make my future meetings more efficient.
Everyone in IT knows that a sprint is a process to make things faster. But how the greatest products in the world solved their problems through a process, their mistakes, etc. are covered in this book.Taking a group from mythology, I started reading this book to again get back to professional track. The Sprint Book is for everyone who wants to solve the problems in their work life, projects.
Though this book is for working where this teaches how to make proper decisions, making a product track which should not loose its goal, it also showcases real startups problems that were fixed by this process.
There are many processes in this sprint process as a whole stressing on taking at least of 5 days from your regular work to make a decision which will save lot of future work.
Ever been in the situation where you are working on a project and you have all the time and resource in the world but the output isn’t to your satisfaction. Or where you are in the situation that you don’t have enough time, or resource but the outcome is excellent? Sprint is a methodology to enable you to build and test ideas fast. Born out of Google, Sprint is a framework enables accelerate project outcomes. The book provides you with all the roles and responsibilities, deliverables and hints and tips from it being used many times within Google and the startup world! If you are in a start-up or want to test an idea for both success and failure this is worth a read. It might save you some time!
This is good book which forces you to think and push you to challenge your limits of thinking of solution, facilitation, stakeholder commitment, prototyping and feedback gathering within shortest possible time which is 5 days in this context but i think this more depends on the culture as well as mindset which is different across geographies. example if we go to western countries where management is ready to take risk they give this chance to new comers without having experience in those areas in which they are looking for solution, but if you come to Asian countries still management is looking for people with higher experience in the same field without thinking that our professionals always comes with a baggage of old mindset