GV sprint
Petr Hyna
November 20, 2017
Five-day process for answering critical business
questions through design, prototyping, and
testing ideas with customers
Use cases
• Start of new project
• Not enough time
• Just plain stuck
Problem
understood
Solution
defined MVP Version 1.0
Our situation
Why did we
use SPRINT in
Kentico?
Set the stage
• Choose big challenge
• Get a Decider (or two)
• Recruit a sprint team
• Schedule extra experts
• Pick a Facilitator
• Block five full days
Team
CEO DEV
UX PM
Facilitator
Deciders
Monday - long term goal
• Why are we doing this project?
• Where do we want to be in six months, a year, or even five years
from now?
„Make the web development faster and more affordable for
marketers and developers”
Monday - sprint questions
• To meet our long-term goal, what has to be true?
• Imagine we travel into the future and our project failed. What
might have caused that?
Monday - map
HMWs concept
Problem/Challenge HMW question
Users are not able to find the content that they are
interested in.
Users are frustrated by the unintuitive navigation in
our system.
The product is difficult to integrate with other
platforms.
“How might we help our users to find content they’re
interested in?”
“How might we make the navigation fun and intuitive
for our users?”
“How might we make it easier to integrate
the product with other platforms?”
Tuesday – lightning demos
• Short demos
• Capture big ideas
Group brainstorming does not work
Tuesday - sketches
• Notes
• Collecting inspiration
• Ideas
• Rough ideas
• Crazy 8s
• Alternative ideas
• Solution sketches
Wednesday – sticky decision
• Art museum
• Heat map
• Speed critique
• Straw poll
• Supervote
After Straw poll
Prototype decision
Wednesday - storyboard
• Opening scene
• Fill out the storyboard
Realistic façade is all
you need to learn from the customers
Thursday
• Prototype mindset
• You can prototype anything
• Prototypes are disposable
• Build just enough to learn, but not more
• The prototype must appear real
• Goldilocks quality
• Create a prototype with just enough
quality to evoke honest reactions
Thursday
• Prototype
• Pick the right tools
• Keynote, PowerPoint, Axure, Indigo Studio, 3D print, Word, modify the existing
space
• Divide and conquer
• Makers, Stitcher, Writer, Asset Collector, Interviewer
• Stitch it together
• Do a trial run
Demo time
Interview & Learn
Interview script
• Friendly welcome
• Context questions
• Introduction to the prototype
• Tasks
• Quick debrief
Interview script – preparation
• Print
• This script
• Questions cheatsheet
• Problem interview
• Find out what’s weather like :-)
• Open prototype
• Prepare
• Empty sheet of paper and pen
• Jabra speaker
• Glass of water
• Learn interviewee’s name and company
• Make sure you have started recording in GoToMeeting
Friday - Interviews
Friday – Wrap up
At the End of the Day
• Look for patterns
• Wrap up
• Review your long-term goal
• Compare with the patterns
• Decide how to follow-up
Lessons learned
• Deciders need to be available when taking decisions
• Prototype syncs help the team to stay on track
• Prepare enough whiteboards to write on (at least 3)
• Lightning demos homework saves the time on Tuesday
• Keep the HMWs visible for Tuesday not to loose
additional inspiration for sketching
Shortened Sprint
Manage item elements
w/o switching to
another screen
Improve modular
content usability and
way of working
Shortened Sprint
• One day
• Goal – get storyboard
Shortened Sprint - experience
• Crazy 8s – wow effect
• Focus on one problem only
• Design sprint was incomplete
• 4 hours schedule (with 2 breaks) was tough
Discussion
Thanks
Feel free to contact me at:
petrh@kentico.com