Have presented this Design Sprint comparison on 2015 at the Business Analysis Track at Developer's Conference
http://www.thedevelopersconference.com.br/tdc/2015/portoalegre/trilha-analise-de-negocios
It's based on MVS Model/The Service Startup by Tenny Pinheiro and servicedesignsprint.com and Google Ventures Design Sprint before the publication of the book Design Sprint by Jack Knapp .
Unfortunately I have missed to publish it in 2015 and I haven't updated it since then.
The subject have gained traction last year so will serve more like a back tracking understand about who and how people had been using sprint for design prior the buzz .
18. Design Thinking
Understand Explore Prototype Evaluate
Context
People
Relationships
User Drives
Behavior
Mental Model
Attitudes
User Journey
Pain Points
Desires
Ideas
Ideas
Journeys
Product
User Interaction
experience
Co-creation
Bring
the Usertalk to
user
gather
the team
define a
challenge
observe
connect
findings
figure out
the
user journey
build raw-
and-fast
observe
learn
reframe
learn
see
materialize
product
service
service
Personas
Bring
the User
19. Design Thinking
Understand Explore Prototype Evaluate
Context
People
Relationships
User Drives
Behavior
Mental Model
Attitudes
User Journey
Pain Points
Desires
Ideas
Ideas
Journeys
Product
User Interaction
experience
Co-creation
Bring
the Usertalk to
user
gather
the team
define a
challenge
observe
connect
findings
figure out
the
user journey
build raw-
and-fast
observe
learn
reframe
learn
see
materialize
product
service
service
Personas
Bring
the User
user perspective storytelling
20. Design Thinking
Understand Explore Prototype Evaluate
Context
People
Relationships
User Drives
Behavior
Mental Model
Attitudes
User Journey
Pain Points
Desires
Ideas
Ideas
Journeys
Product
User Interaction
experience
Co-creation
Bring
the Usertalk to
user
gather
the team
define a
challenge
observe
connect
findings
figure out
the
user journey
build raw-
and-fast
observe
learn
reframe
learn
see
materialize
product
service
service
Personas
Bring
the User
user perspective storytelling
Opportunitiesinsights Barriers
21. Design Thinking
Understand Explore Prototype Evaluate
Context
People
Relationships
User Drives
Behavior
Mental Model
Attitudes
User Journey
Pain Points
Desires
Ideas
Ideas
Journeys
Product
User Interaction
experience
Co-creation
Bring
the Usertalk to
user
gather
the team
define a
challenge
observe
connect
findings
figure out
the
user journey
build raw-
and-fast
observe
learn
reframe
learn
see
materialize
product
service
service
Personas
Bring
the User
user perspective storytelling
Opportunitiesinsights Barriers
22. Design Thinking
Understand Explore Prototype Evaluate
Context
People
Relationships
User Drives
Behavior
Mental Model
Attitudes
User Journey
Pain Points
Desires
Ideas
Ideas
Journeys
Product
User Interaction
experience
Co-creation
Bring
the Usertalk to
user
gather
the team
define a
challenge
observe
connect
findings
figure out
the
user journey
build raw-
and-fast
observe
learn
reframe
learn
see
materialize
product
service
service
Personas
Bring
the User
user perspective storytelling
Opportunitiesinsights Barriers
29. Timeboxing
Sprint
essential to driving the right types of behavior from the
participants.
energy economy and social collaboration
It’s not just important in speeding up
30. Timeboxing
Understand Explore Prototype Evaluate
Challenge Solutions
Sprint
essential to driving the right types of behavior from the
participants.
energy economy and social collaboration
It’s not just important in speeding up
31. Timeboxing
Understand Explore Prototype Evaluate
Challenge Solutions
essential to driving the right types of behavior from the
participants.
energy economy and social collaboration
It’s not just important in speeding up
Design Sprint
34. Service Design Sprint
The Minimum Valuable Service
MVS Model
theservicestartup.com
The sprint gives teams a shortcut
to learning without building and
launching.
Google Ventures Sprint
gv.com/sprint
38. Organizing your Sprint
interactions
Day 1
Monday
Day 2
Tuesday
Day 3
Wednesday
Day 4
Thursday
Day 5
Friday
Day 1 Day 2 Day 3 Day 4
week 1 week 2 week 3
Day 1 Day 2 Day 3 Day 4
week 1 week 1
39. Context
Clear your calendars and gather some essential supplies.
Multidisciplinar Team
Service Design Sprint
Google Ventures Sprint
4 day - no sequencial days
5 days - sequencial days
pre Sprint
Plain your sprint interactions
40. Context
Clear your calendars and gather some essential supplies.
Multidisciplinar Team
Service Design Sprint
Google Ventures Sprint
4 day - no sequencial days
5 days - sequencial days
pre Sprint
Plain your sprint interactions
41. Context
Clear your calendars and gather some essential supplies.
Multidisciplinar Team
Service Design Sprint
Google Ventures Sprint
4 day - no sequencial days
5 days - sequencial days
Schedule a user study before you start the sprint
pre Sprint
Plain your sprint interactions
43. Understand
MONDAY: UNPACK
“unpack” everything they know draw insights from the team together
create a simple user story
set the scope for the week
take useful notes as a team
Time Machine (past/present/future) - create perspective around the challenge
Sprint Ethnography - 15 min to talk to people who uses to faces our challenge
Hero Profile: capture extreme attitudes and build attitudinal profile and
mental models
Invoking your Heroes: recruiting real uses that fills up the Hero attitudes
and mental models
Humanize::Projection
Day
1
45. Explore
Ethnography: 50 min interviews with real users that fits the Hero Profile
The Hero Quest: download the interview data and build the journey
challenges (faced by the Hero) and explore how he is solving/overcoming it.
Discuss Opportunities and Barriers for hero desires and pain points
Tuesday: SKETCH
Team will work individually to draw detailed solutions on paper
Everyone works separately to ensure maximum detail and depth
with minimum groupthink.
Breaking it down into four discrete steps (Notes, Mind Map, Crazy 8s, and
Storyboard),
Humanize::Perpectives
After sketching, you’ll use a structured critique and weighted voting to select the
best ideas from the field of possibilities.
Co-criation: bring real plain users and Heroes to co-create ideas among the
groups teams
Day
2
Day
3
47. Prototype
WEDNESDAY: DECIDE
Decide which prototype
Draw a storyboard, which serves
as a blueprint of your
forthcoming prototype
Select research participants and get
to work planning Friday’s interviews
THURSDAY: PROTOTYPE
Build an entire realistic-looking
prototype in just eight hours
Gather a team of experts, assign
roles, and put your plan into
motion
Service Principles
The MVS Journey: prototype the service journey with ideas and
solutions
Hero Pitch: the Hero will pitch(and defend) the team ideas to
other teams and stakeholders
Crystallize::Playground
Day
3
49. Evaluate
Crystallize::Polish-off
FRIDAY: TEST
Show your prototype to real customers in 1-on-1 interviews.
Observe, taking notes as a team and finding patterns in real time
Ideas have all been exposed to oxygen — some will be smash
hits, while others will meet an early end.
Playback: call the users and observe them walking through your
service prototype
Polish-off: refine and polish-off
Backlog: create your Threshold/Performance/WoW/Waste prioritized
backlog
Carving the Pitch: build your MVS selling pitch
Day
4
50. Service Design Sprint
Google Ventures Sprint
4 day - no sequencial days
5 days - sequencial days
Validated High
Definition Prototypes
post Sprint
Learning
by Immersion
in your own
opportunity
Discover your
User Oriented
Business
Principles
Business
Backlog
Learning
by Immersion
in your own
opportunity
52. Service Design Sprint Google Ventures Sprint
some differences
4 day - no sequential days 5 sequential days
53. Service Design Sprint Google Ventures Sprint
some differences
Service Dominant Logic Product Experiences
4 day - no sequential days 5 sequential days
54. Service Design Sprint Google Ventures Sprint
some differences
Service Dominant Logic Product Experiences
4 day - no sequential days 5 sequential days
The Team works with user
since the beginning
The team does not participate in
the user research
The User Research is a input to
the Sprint
55. Service Design Sprint Google Ventures Sprint
some differences
Service Dominant Logic Product Experiences
4 day - no sequential days 5 sequential days
Co-creation does not include
the real user
Co-creation includes the
regular and Hero users
The Team works with user
since the beginning
The team does not participate in
the user research
The User Research is a input to
the Sprint
56. Service Design Sprint Google Ventures Sprint
some differences
Service Dominant Logic Product Experiences
High Definition PrototypesLow Definition Prototypes
4 day - no sequential days 5 sequential days
Co-creation does not include
the real user
Co-creation includes the
regular and Hero users
The Team works with user
since the beginning
The team does not participate in
the user research
The User Research is a input to
the Sprint
57. Service Design Sprint Google Ventures Sprint
some differences
Service Dominant Logic Product Experiences
High Definition PrototypesLow Definition Prototypes
4 day - no sequential days 5 sequential days
Co-creation does not include
the real user
Co-creation includes the
regular and Hero users
Minimum Valuable Service Minimum Viable Product
The Team works with user
since the beginning
The team does not participate in
the user research
The User Research is a input to
the Sprint