Slide 1
Slide 1 text
How to make a blended agile
approach work for you
#AdaptingAgile
@suzehaworth
Slide 2
Slide 2 text
+
A bit about me…
+
@suzehaworth
Slide 3
Slide 3 text
+ +
2005…
@suzehaworth
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
THINGS
CHANGE
Slide 6
Slide 6 text
Waterfall vs Agile
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
FORGET
THE
SNOBBERY
Slide 9
Slide 9 text
As long as your process is right
for your project, your client,
your team, your organisation, it
doesn’t matter what it’s called
Slide 10
Slide 10 text
YOUR CUSTOMERS
ABOUT YOUR PROCESS
DON’T GIVE A SHIT
Slide 11
Slide 11 text
So today I want you to get
comfortable…
Slide 12
Slide 12 text
…with not following a strict process
Slide 13
Slide 13 text
FOR TODAY
OUTCOMES
1
Slide 14
Slide 14 text
Assumptions
Slide 15
Slide 15 text
1. We are all different
2. We all have different experiencees
3. We all work at different places
Slide 16
Slide 16 text
Out of scope
Slide 17
Slide 17 text
1. There’s so much to cover!
2. Let’s chat more…
Slide 18
Slide 18 text
#AdaptingAgile
@suzehaworth
Slide 19
Slide 19 text
THERE IS NO
SILVER BULLET
Slide 20
Slide 20 text
THINK LESS PROJECT
MORE PRODUCT
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
THINK LESS PROJECT
MORE PRODUCT
Slide 23
Slide 23 text
HOW TO
ADAPT AGILE
Slide 24
Slide 24 text
OUTCOMES
FOR TODAY
1 2 3 4
CORE
PRINCIPLES
PRODUCT
DISCOVERY
HOW TO
ADAPT AGILE
Slide 25
Slide 25 text
OUTCOMES
FOR TODAY
1 2 3 4
CORE
PRINCIPLES
PRODUCT
DISCOVERY
HOW TO
ADAPT AGILE
ACTIVITIES!
Slide 26
Slide 26 text
Exercise 1:
Mapping your
process
Slide 27
Slide 27 text
1. Use post-its to map your process
on your current project out, thinking
about the stages you go through
2. If time, add in any tools, techniques
and practices against each stage
BRIEF:
OUTCOME: You will have mapped out your
current process, plus ways of
working
Slide 28
Slide 28 text
REQUIRE-
MENTS
DEFINE UX DESIGN LAUNCH
DEV QA
Slide 29
Slide 29 text
REQUIRE-
MENTS
DEFINE UX DESIGN LAUNCH
WIRE
FRAMES
KICK OFF
MEETING
DEV
DAILY
STAND UPS
QA
BUSINESS
NEEDS
USER
NEEDS
BACKLOG
STATIC
DESIGNS
CLIENT
DEMOS
SPRINTS
TDD
RETRO-
SPECTIVES
Slide 30
Slide 30 text
WHAT ARE THE
PRINCIPLES
2
OF GOOD PRODUCT DELIVERY?
Slide 31
Slide 31 text
FORGET
AGILE…
Slide 32
Slide 32 text
FOR NOW!
FORGET
AGILE…
Slide 33
Slide 33 text
#1
CUSTOMER FIRST
Slide 34
Slide 34 text
CUSTOMER FIRST
Prioritise the customer and the outcomes they will
value
Value getting working designs, prototypes or software
to the customer over defining requirements upfront
Feedback and iterate
Slide 35
Slide 35 text
FREQUENT DELIVERY
#2
Slide 36
Slide 36 text
Deliver a working product quickly to the
customer
Team and customers working together to
make adjustments
Iterative development
FREQUENT DELIVERY
Slide 37
Slide 37 text
TEAM COLLABORATION
#3
Slide 38
Slide 38 text
Key to making your project work and building a
better product
Don’t rely on documentation to define
requirements and share knowledge
Face to face communication and shared decisions
The team is your client too!
TEAM COLLABORATION
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
1. Individuals and
interactions over processes
and tools
2. Working software over
comprehensive documentation
3. Customer collaboration over
contract negotiation
4. Responding to change over
following a plan
TEAM
COLLABORATION
CUSTOMER
FIRST
FREQUENT
DELIVERY
Slide 41
Slide 41 text
1. Focus on customers
2. Optimise the whole
3. Elimate waste
4. Learn first
5. Deliver fast
6. Keep getting better
7. Energise workers
TEAM
COLLABORATION
CUSTOMER
FIRST
FREQUENT
DELIVERY
Slide 42
Slide 42 text
So what are the challenges with
adopting one rigid methodology?
Slide 43
Slide 43 text
You’re not responding to change
It’s harder to inspect and adapt
You’re not allowing for the mix of
needs on your projects
Slide 44
Slide 44 text
THERE’S NO
ONE SIZE FITS ALL
Slide 45
Slide 45 text
“You have your way. I have my way. As for
the right way, the correct way, and the only
way, it does not exist.”
Nietzsche, 1891
Slide 46
Slide 46 text
Exercise 2:
Identifying the pain
points
Slide 47
Slide 47 text
1. Looking at your process and the 3
principles, think about any
problems you are having on current
projects.
2. Fill in the first column of the canvas.
BRIEF:
OUTCOME: You will identify pain points in your
projects against the 3 core
principles.
Slide 48
Slide 48 text
REQUIRE-
MENTS
DEFINE UX DESIGN LAUNCH
WIRE
FRAMES
KICK OFF
MEETING
DEV
DAILY
STAND UPS
QA
BUSINESS
NEEDS
USER
NEEDS
BACKLOG
STATIC
DESIGNS
CLIENT
DEMOS
SPRINTS
TDD
RETRO-
SPECTIVES
LACK OF
DESIGN
TIME
NO USER
TESTING
NOT
WHOLE
TEAM
NO SPRINT
RELEASES
Slide 49
Slide 49 text
Pain points
(Principles)
Opportunities
(Processes)
Actions
(Practices)
Customer first:
• No user testing until we’ve
launched the product
• Lack of design time means
we’re focusing on tech defining
the product
Frequent delivery:
• Despite working in Sprints, we
aren’t releasing frequently
Team collaboration:
• We don’t have the entire team
involved from the start of the
project
#AdaptingAgile
@suzehaworth
Slide 50
Slide 50 text
WHY WE SHOULD
PRODUCT
3
THINK MORE
Slide 51
Slide 51 text
All core principles come back to
one thing:
Building the best product possible
Slide 52
Slide 52 text
“We have come to realise that bespoke
software delivery is far more akin to
product design and development than it
is to project delivery.”
John Yorke, 2017
Slide 53
Slide 53 text
DISCOVERY?
WHAT IS
PRODUCT
Slide 54
Slide 54 text
Discover and test that what
you are building is what the
customer needs
Slide 55
Slide 55 text
Deliver what your customer
needs… rather than what
you (or they!) think they want
Slide 56
Slide 56 text
E X I S T I N G
D A T A &
R E S E A R C H
I N S I G H T S
A S S U M P T I O N S
F U R T H E R
R E S E A R C H
H Y P O T H E S E S
STAGE 1
I D E N T I F Y
P A I N P O I N T S
I D E N T I F Y
O P P O R T U N I T I E S
Slide 57
Slide 57 text
U X / D E S I G N P R O T O T Y P E T E S T I N S I G H T S
STAGE 2
I T E R A T E
Slide 58
Slide 58 text
Gather requirements Review data & research
Think in terms of deliverables Identify customer pain points
Develop features
Develop assumptions &
hypotheses
Build & launch Design & prototype
Test after dev Test & learn before dev
Product
Project
Slide 59
Slide 59 text
3. A better backlog
1. Validated learning
2. Build things customers need
4. Business value
Slide 60
Slide 60 text
DELIVERY
FREQUENT
DON’T FORGET
Slide 61
Slide 61 text
Keep discovery lean and fast
Feed into delivery quickly
Involve your dev team in the discovery process
We don’t need to pick sides!
Slide 62
Slide 62 text
Exercise 3:
Identifying
opportunities
Slide 63
Slide 63 text
1. Thinking about product over project
process, where are the opportunities
to improve in your projects?
2. Fill in the second column of the
canvas with a couple of hypotheses
BRIEF:
OUTCOME: You will identify what the
opportunities in your project
process are
Slide 64
Slide 64 text
I believe that [creating this experience]
For [this persona]
Will achieve [this outcome]
Slide 65
Slide 65 text
Pain points
(Principles)
Opportunities
(Processes)
Actions
(Practices)
Customer first:
• No user testing until we’ve
launched the product
• Lack of design time means
we’re focusing on tech defining
the product
Frequent delivery:
• Despite working in Sprints, we
aren’t releasing frequently
Team collaboration:
• We don’t have the entire team
involved from the start of the
project
Customer first:
• I believe that testing designs on
customers
• For my whole team
• Will help us define the correct
solution before we start build
and help eliminate waste
Frequent delivery:
• I believe that reviewing the
release process and uncovering
blockers
• For my developers
• Will help us to release more
frequently
#AdaptingAgile
@suzehaworth
Slide 66
Slide 66 text
HOW DO YOU
ADAPT AGILE?
4
Slide 67
Slide 67 text
No content
Slide 68
Slide 68 text
The problem
Slide 69
Slide 69 text
APPROACH
DUAL TRACK
THE
Slide 70
Slide 70 text
John Ciecholewski
Slide 71
Slide 71 text
John Ciecholewski
Slide 72
Slide 72 text
John Ciecholewski
Slide 73
Slide 73 text
PROTOTYPING
CUSTOMER FIRST
PURPOSEFUL
Slide 74
Slide 74 text
Static
Gauge reactions to
concepts/propositions
Test short journeys and
simple goals
e.g. Invision
Low fidelity
Slide 75
Slide 75 text
Medium fidelity
Interactive
Get input on experience /
mechanics of a journey
Test new products/features,
look & feel & motion principles
e.g Principle
Slide 76
Slide 76 text
High fidelity
Live
Gauge reactions to true
functionality of full scenarios
Test look & feel & complex
interactions
e.g HTML prototype
Slide 77
Slide 77 text
USER & USABILITY
TESTING
CUSTOMER FIRST
Slide 78
Slide 78 text
Face to face interviews
Guerrilla testing
Online testing
Surveys
Slide 79
Slide 79 text
DEFINING AN
MVP
FREQUENT DELIVERY
Slide 80
Slide 80 text
SUSTAINABLE
PACE
FREQUENT DELIVERY
Slide 81
Slide 81 text
It’s actually more of a
marathon, than a sprint!
Slide 82
Slide 82 text
It’s actually more of a
marathon, than a sprint!
Slide 83
Slide 83 text
VISUALISE
WORKFLOW
FREQUENT DELIVERY
Slide 84
Slide 84 text
Camilla Chakiri
Slide 85
Slide 85 text
LIMIT
WIP
FREQUENT DELIVERY
Slide 86
Slide 86 text
Camilla Chakiri
Limit: 4
Limit: 6
Slide 87
Slide 87 text
TEAM
COLLABORATION
Slide 88
Slide 88 text
1. Balanced team
Slide 89
Slide 89 text
“We are one team”
Aaron, 2018
Slide 90
Slide 90 text
1. Balanced team
2. Understand team needs
Slide 91
Slide 91 text
“Learn about what makes them tick”
Aaron, 2018
Slide 92
Slide 92 text
3. Communication that’s just enough
1. Balanced team
2. Understand team needs
Slide 93
Slide 93 text
“How can I help you to have
a better project experience?”
Yvette, 2018
Slide 94
Slide 94 text
3. Communication that’s just enough
1. Balanced team
2. Understand team needs
4. Retrospectives
Slide 95
Slide 95 text
HOW TO
IMPLEMENT
Slide 96
Slide 96 text
3. Involve the full team
1. Small increments
2. Test and learn—and trash
4. Understand and sell the value
Slide 97
Slide 97 text
Be confident—don’t let
the process own you,
own the process
Slide 98
Slide 98 text
Adapting agile is about trying
to work with more agility using
the core principles
Slide 99
Slide 99 text
Exercise 4:
Your actions!
Slide 100
Slide 100 text
1. Think about any of the techniques
I’ve gone through (and any others!)
and what you can takeaway to your
projects.
2. Fill in the third column of the canvas.
BRIEF:
OUTCOME: You will identify actions to apply
within your projects, against the 3
core principles
Slide 101
Slide 101 text
OUTCOMES
FOR TODAY
1 2 3 4
CORE
PRINCIPLES
PRODUCT
DISCOVERY
HOW TO
ADAPT AGILE
Slide 102
Slide 102 text
T
HANK YOU!
@suzehaworth