The document discusses agile inception techniques that can be used at the beginning of a project to align stakeholders, understand user needs, establish relationships, and mitigate risk. It describes common techniques like assumption mapping, vision/product box creation, impact mapping, and user journey mapping. The goal is to give customers permission not to have all the answers at the start, ensure alignment, and provide outputs to safely start the project.

1. Agile Inception
Techniques
@Kev_C_Murray & Tony White

2. • Have you learned the specific inception
techniques?
• Have you learned facilitation techniques?
• Will you use them next week?
• Did you have fun?
WORKSHOP GOALS

3. Gives the customer permission not to know everything at start
Ensures stakeholder alignment and a shared vision of success
Provides an understand user of needs and business goals
Mitigates risk
Creates outputs to safely start a project
WHAT IS THE PURPOSE OF INCEPTION?

4. WHY INCEPTION?
Smaller commitment
Quickly kills unnecessary projects
Demonstrates stand alone value
Who really starts coding on day 1?
Establishes relationships
It works!

5. Assumption
Mapping
Impact
Mapping
Impact
Estimation
Technical Spikes
Vision
Product Box
Sliders
(Competing
Constraints)
Measurable KPIs
Hero Journey
Stakeholder
Mapping
Communications
Plan
Logistics &
Cadence
Introductions
Retrospective /
Futurespective
Prototyping
Hypotheses
Creation User Journey
Mapping
Story Mapping
Release Planning
Guerrilla
Testing
Affinity
Sorting
Sizing
Mood Boards
Inspiration
Boards
Roles and
Responsibilities
plus many more……

6. Assumption
Mapping
Impact
Mapping
Impact
Estimation
Technical Spikes
Vision
Product Box
Sliders
(Competing
Constraints)
Measurable KPIs
Hero Journey
Stakeholder
Mapping
Communications
Plan
Logistics &
Cadence
Introductions
Retrospective /
Futurespective
Prototyping
Hypotheses
Creation User Journey
Mapping
Story Mapping
Release Planning
Guerrilla
Testing
Affinity
Sorting
Sizing
Mood Boards
Inspiration
Boards
Roles and
Responsibilities
plus many more……

7. Assumption
Mapping
VisionProduct Box
Sliders
(Competing
Constraints)

8. Assumption
Mapping
Vision
Product
Box
Sliders
(Competing
Constraints)
Options
Plan
?

9. The ProblemWhen we were small we
all chatted in the pub
We could scale through
pub of pub conversations
Most of our projects are
on our customers sites
As we grow, consultants
feel further from
management
As we grow, management
feel further from
the projects
As a consultant I want to
influence management
decisions
Management
decisions affect
consultants and
their projects
We need a bridge for continuous
lightweight interaction

10. PRODUCT BOX & VISION

11. THE (name of project/service)
FOR (users of the product/service)
WHO WANT (key features/needs of the product/service)
THIS SERVICE(S) WILL (sub key features)
UNLIKE (existing product/service)
THIS SERVICE WILL (key differentiators / advantages of product/service)
VISION

12. The Tool is a Practical / Simple / Vital / Responsive
For Small traders / Sole traders / Construction and maintenance
workers / Vulnerable
Who want to Practical / Easy to understand / Simple / Safety
Information / Guidance
This product Achieves / Inspires / Encourages / Motivates to work more
safely / change in behaviour
Unlike Tabloid newspapers / Current practice / Work advice / Guesses /
HSE guidance / YouTube
This is Accurate / Easy to comprehend / Easy to take advice / Easy to
access / Trusted / Used by my peers / Specific / Relevant
VISION (BAD EXAMPLE)

13. Title
Logo
Strap
line
Key
Feature
Sub Features
PRODUCT BOX

14. Title
Logo
Strap
line
Key
Feature
Sub Features
Front
Back
Title
Logo
Strap line
Key Feature
Sub Feature
Details
PRODUCT BOX

15. THE (name of project/service)
FOR (users of the product/service)
WHO WANT (key features/needs of the product/service)
THIS SERVICE(S) WILL (sub key features)
UNLIKE (existing product/service)
THIS SERVICE WILL (key differentiators / advantages of product/service)
VISION

16. VISION BECOMES THE MISSION

17. ASSUMPTION MAPPING

19. Defer evaluation of non-urgent assumptions
uncertainty
urgency
Reduceuncertaintythroughanalysisoruserengagement

20. Defer evaluation of non-urgent assumptions
uncertainty
urgency
Reduceuncertaintythroughanalysisoruserengagement
Ready for investment
Requires validating
Ready for investment
Requires validating

21. Assumption mapping

22. Assumption mapping

23. Defer evaluation of non-urgent assumptions
uncertainty
urgency
Reduceuncertaintythroughanalysisoruserengagement
Ready for investment
Requires validating

24. 24
Assumptions Hypotheses Test Data Insight
User Needs
Business Goals
Hunches
Assumption Mapping
Research
Qual / Quant
Personas
Questions
Wireframes
Prototypes
Creative
User testing
Guerilla
testing
Lab testing
Affinity
Sorting
LeanUX

25. Assumptions to working software

26. Sliders
SLIDERS

27. SLIDERS
Budget
Duration
Scope (Beta)
Quality
GDS Standards
User Needs
Enablement
Accessibility
Responsiveness
Security
1 110

28. SLIDERS
UX
Re-use
Enablement
Security
Scope
Cost and pace of
change
!
Accessibility
Schedule
User Engagement
Compliance
!
110

29. CREATIVE SLIDERS

30. • Have you learned the specific inception
techniques?
• Have you learned facilitation techniques?
• Will you use them next week?
• Did you have fun?
WORKSHOP GOALS

31. INSPIRATION
Lean UX - Jeff Gothelf
Crossing the Chasm - Geoff Moore
Radical project Management - Rob Thomsett
Bad idea killer - Melissa Perri
Product Box - Innovation Games
Dave Draper - @david_draper
Alastair Brown - @AlBrownCTO
Lydia Livingston - @lydiar
Imran Younis - @ImranYounis
Carolyn Warburton - @affrontedux
Naomi Williams - @teapotdrama
Dave Clark - @DVC752003