"Because of the short timeline, it’s tempting to jump into prototyping as soon as you’ve selected your winning ideas. But if you start prototyping without a plan, you’ll get bogged down by small, unanswered questions. Pieces won’t fit together, and your prototype could fall apart." (Jake Knapp et al, "Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days", 2016)
"But perhaps the biggest problem is that the longer you spend
working on something - whether it’s a prototype or a real product - the more
attached you’ll become, and the less likely you’ll be to take negative test
results to heart. After one day, you’re receptive to feedback. After three
months, you’re committed."
"No problem is too large for a sprint. Yes, this statement sounds absurd, but there are two big reasons why it’s true. First, the sprint forces your team to focus on the most pressing questions. Second, the sprint allows you to learn from just the surface of a finished product." (Jake Knapp et al, "Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days", 2016)
"Sometimes, the best way to broaden your search is to look
inside your own organization. Great solutions often come along at the wrong
time, and the sprint can be a perfect opportunity to rejuvenate them. Also look
for ideas that are in progress but unfinished - and even old ideas that have
been abandoned."
"Sometimes when people work together in groups, they start to
worry about consensus and try to make decisions that everybody will approve - mostly
out of good nature and a desire for group cohesion, and perhaps in part because
democracy feels good. Well, democracy is a fine system for governing nations, but
it has no place in your sprint."
"Sometimes you can’t fit everything in. Remember that the
sprint is great for testing risky solutions that might have a huge payoff. So
you’ll have to reverse the way you would normally prioritize. If a small fix is
so good and low-risk that you’re already planning to build it next week, then
seeing it in a prototype won’t teach you much. Skip those easy wins in favor of
big, bold bets."
"The prototype is meant to answer questions, so keep it
focused. You don’t need a fully functional product - you just need a
real-looking façade to which customers can react."
"There are only six working hours in the typical sprint day.
Longer hours don’t equal better results. By getting the right people together,
structuring the activities, and eliminating distraction, we’ve found that it’s
possible to make rapid progress while working a reasonable schedule."
"When a big problem comes along, like the challenge you
selected for your sprint, it’s natural to want to solve it right away. The
clock is ticking, the team is amped up, and solutions start popping into
everyone’s mind. But if you don’t first slow down, share what you know, and
prioritize, you could end up wasting time and effort on the wrong part of the
problem."
"You can prototype anything. Prototypes are disposable. Build just enough to learn, but not more. The prototype must appear real." (Jake Knapp et al, "Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days", 2016)
No comments:
Post a Comment