Design Sprint

There's a lot of evidence to suggest the book wasn't even proofed before it was published. There are spelling mistakes all over it and even an entire paragraph repeated on pages 158 and 162. 

It's a short book padded out with irrelevant or uselessly vague anecdotes and photos that don't relate to the topic under discussion. 
For example page 168 discusses how to use a 2x2 matrix. The text says ‘draw a Cartesian coordinate “+” on a board. A what? How big? Frustratingly there's a large image on the opposite page... But it's not a 2x2 matrix. I don't know what it is, it seems to be random scribbling. It has nothing to do with the text and anyone who has never seen a 2x2 matrix or knows what a Cartesian coordinate + is, will not be enlightened. Opportunity missed. 

It could have been much better - ‘show don't tell' is one of the key lessons we get drummed into us at school and if the authors had followed that advice this would have been a fantastic book. As it is it's frustrating. The ideas are good. The suggested agendas are useful. The execution is poor. 

A particular issue is that the book is clearly focused on digital design. But that clarity is only apparent when you start reading it. This makes it even more frustrating for anyone designing communications, services or other things - there's a lot of translation needed to make it useful. 
I want to recommend this book as it's potentially beneficial. But it's a good example of what's missing in the literature on design sprints than a long-lasting contribution to it. 

Comparé au livre fondateur de la méthodologie Sprint, [b:Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days 25814544 Sprint How to Solve Big Problems and Test New Ideas in Just Five Days Jake Knapp https://images.gr-assets.com/books/1457284924s/25814544.jpg 45671240], ce livre n'apporte au final pas grand chose à part une litanie de manières de réduire la méthodologie Sprint en charpie pour satisfaire à des exigences de grandes entreprises. La force du Sprint étant de compresser un process en un très petit nombre de jour comparé aux gros projet, ce livre déforce à mes yeux l'ensemble du process. La profusion d'ateliers peut sembler intéressante au premier abord, mais la majorité n'apportent pas grand chose. Bref, à passer.