Agile & UX
What Changes And Other C.R.A.P.

        Jon Stahl @jonrstahl
     Michael Norton @docondev
Agenda
•   UX
•   Agile
•   What Changes
•   What We Can Do
•   Agile/UX Practices
UX
The way a person feels about using a product,
system, or service.

Many disciplines contribute, including computer
science, psychology, ergonomics, engineering,
systems thinking, and graphic design.
UX Practices
• User Research      • UI Design
  – Personas           – Hi-Fidelity
• User Modeling          Prototypes
                         •   Contrast
  – Scenarios            •   Repetition
• Task                   •   Alignment
                         •   Proximity
  Analysis/Design
  – Use Cases
UX Appetite
                                                                    Search

                                                E-Mail
Opt In



                                                Client    Social
                                                         Networks


                                      E-Mail
                                     Back-End
Compelled




            Time Entry
                         Insurance
                           Claims



              Internal                          External/Customer Facing
Agile
A collection of software practices focused on
incremental and adaptive development.



Many disciplines contribute, including computer
science, psychology, ergonomics, engineering,
systems thinking, and graphic design.
Agile Practices
• Customer              – Features/Scenarios
  Collaboration       • Simple &
  – Clearly Defined     Evolutionary Design
    Customer            – Low-Fidelity
• Backlog                 Prototypes
  – User Stories        – Iterative
• ATDD / TDD
UX & Agile
UX & Agile : The Shift
What Changes

•   UX teams not staffed for one UX person per team
•   Release Planning sometimes fails to include UX
•   Two week iterations can be too short for UX + Dev
•   Teams encouraged to use light-weight practices and
    focus on reducing waste
What We Can Do

• Move team from SCRUM to kanban to better
  understand flow
• Program/Feature Alignment Room
• Create Classes of Service
  • See UX Appetite Grid
• Feature Mapping to deliver MVP by Persona type
Agile/UX Practices

1. User Story Mapping
2. Lean Startup and Test First Design
3. Flash Builds
User Story Mapping

•   Describe the story using lightweight tools
•   Understand the pain points
•   Focus on Customer Value
•   Converge on solutions
User Story Mapping Steps
1. Capture the basic story & decompose steps
   as necessary
2. Talk about pain points
3. Prioritize
Persona:
Connected Communicated Consumer (CCC)

                      •   Cross Generational
                      •   Smart Phone
                      •   Always connected
                      •   Twitter
                      •   Facebook
                      •   Amazon Reviews
                      •   Froogle
Now, you do it.
• One person               – Describe what
  volunteered to be the      happens next
  CCC                   • Rest of Team
• Scenario                 – Capture the story on
                              post-it notes
  – CCC is at the mall
                            – One key item per note
  – Clothes shopping
                            – No Leading Questions
  – Just walked in the
    door                 • Ten Minutes
Now, you do it.
• Identify pain points (Mr. Yuck)
• Rank them
• 5 minutes
User Story Mapping
•   Describe the story using lightweight tools
•   Understand the pain points
•   Focus on Customer Value
•   Converge on solutions
Lean Startup

                   #2
                   Best
                   Seller

 Lean Startup is a
 disciplined, scientific &
 capital efficient method for
 discovering & building
 products and services that
 people love.
Build, Measure, Learn
• Form a hypothesis
• Implement lightest-weight possible way to get
  feedback
  – Do we even need to build software?
• Measure Results
• Iterate toward a Minimally Viable Product
  – An “iteration” is a single build, measure, learn
    cycle
Test First Design “TFD”
Door is Locked
• Hypothesis: CCC will send a text to open door
• Test?
Test First Design : Door is Locked
Test First Design
Door is Locked
• Text to open door
• Customer Value
   – Easy Access
   – Feel Trusted
• Business Value
   – Allows capture of consumer data
   – Have customer phone number in case of theft
   – Notifications to sales person
Test First Design
Wrong Sizes
• Hypothesis: CCC will scan barcode and request
  correct size
• Test?
Now, you do it.
Wrong Sizes
• Use paper and pencil
• Come up with a hypothesis and a test for it
• 5 minutes
Test First Design : Wrong Size
Test First Design
Wrong Sizes
• Scan barcode and Request Size
• Customer Value
  – Don’t have to leave changing room
  – Personal Service
• Business Value
  – Better service => more sales
  – Not in stock; prompt to order
Agile - VS - Lean Startup
Agile                    Lean Startup
Product Roadmap          Business Model Canvas
Product Vision           Product Market Fit
Release Plan             Minimal Viable Product
Sprint                   Kanban
Sprint Review            Pivot or Persevere Decision
On-Site Customer         “Get Out Of The Building”
User Story               Hypothesis
Backlog                  “To Learn” List
Definition of Done       Validated Learning
Red-Green-Refactor       Learn-Measure-Build
Customer Feedback        Customer Validation
Acceptance Test          Split Test
Velocity                 AARRR
Mock Object              Feature Fake
Continuous Integration   Continuous Deployment
Certified Scrum Master   Customer Success Manager      - Joshua Kerievsky
Flash Builds
• Watch the Nordstrom Innovation Lab: Click this link
  http://www.youtube.com/watch?v=szr0ezLyQHY
Flash Builds
• What did you see that was agile?
• How did design happen?
Review
•   UX
•   Agile
•   What Changes
•   What We Can Do
•   Agile/UX Practices
    – User Story Mapping
    – Lean Startup and Test First Design
    – Flash Builds
Questions,              @jonRstahl
Comments?               @DocOnDev




    216.236.4705

jon.stahl@leandog.com
  doc@leandog.com

Agile & UX What changes and other C.R.A.P.

  • 1.
    Agile & UX WhatChanges And Other C.R.A.P. Jon Stahl @jonrstahl Michael Norton @docondev
  • 2.
    Agenda • UX • Agile • What Changes • What We Can Do • Agile/UX Practices
  • 3.
    UX The way aperson feels about using a product, system, or service. Many disciplines contribute, including computer science, psychology, ergonomics, engineering, systems thinking, and graphic design.
  • 4.
    UX Practices • UserResearch • UI Design – Personas – Hi-Fidelity • User Modeling Prototypes • Contrast – Scenarios • Repetition • Task • Alignment • Proximity Analysis/Design – Use Cases
  • 5.
    UX Appetite Search E-Mail Opt In Client Social Networks E-Mail Back-End Compelled Time Entry Insurance Claims Internal External/Customer Facing
  • 6.
    Agile A collection ofsoftware practices focused on incremental and adaptive development. Many disciplines contribute, including computer science, psychology, ergonomics, engineering, systems thinking, and graphic design.
  • 7.
    Agile Practices • Customer – Features/Scenarios Collaboration • Simple & – Clearly Defined Evolutionary Design Customer – Low-Fidelity • Backlog Prototypes – User Stories – Iterative • ATDD / TDD
  • 8.
  • 9.
    UX & Agile: The Shift
  • 10.
    What Changes • UX teams not staffed for one UX person per team • Release Planning sometimes fails to include UX • Two week iterations can be too short for UX + Dev • Teams encouraged to use light-weight practices and focus on reducing waste
  • 11.
    What We CanDo • Move team from SCRUM to kanban to better understand flow • Program/Feature Alignment Room • Create Classes of Service • See UX Appetite Grid • Feature Mapping to deliver MVP by Persona type
  • 12.
    Agile/UX Practices 1. UserStory Mapping 2. Lean Startup and Test First Design 3. Flash Builds
  • 13.
    User Story Mapping • Describe the story using lightweight tools • Understand the pain points • Focus on Customer Value • Converge on solutions
  • 14.
    User Story MappingSteps 1. Capture the basic story & decompose steps as necessary 2. Talk about pain points 3. Prioritize
  • 15.
    Persona: Connected Communicated Consumer(CCC) • Cross Generational • Smart Phone • Always connected • Twitter • Facebook • Amazon Reviews • Froogle
  • 17.
    Now, you doit. • One person – Describe what volunteered to be the happens next CCC • Rest of Team • Scenario – Capture the story on post-it notes – CCC is at the mall – One key item per note – Clothes shopping – No Leading Questions – Just walked in the door • Ten Minutes
  • 19.
    Now, you doit. • Identify pain points (Mr. Yuck) • Rank them • 5 minutes
  • 21.
    User Story Mapping • Describe the story using lightweight tools • Understand the pain points • Focus on Customer Value • Converge on solutions
  • 22.
    Lean Startup #2 Best Seller Lean Startup is a disciplined, scientific & capital efficient method for discovering & building products and services that people love.
  • 23.
    Build, Measure, Learn •Form a hypothesis • Implement lightest-weight possible way to get feedback – Do we even need to build software? • Measure Results • Iterate toward a Minimally Viable Product – An “iteration” is a single build, measure, learn cycle
  • 24.
    Test First Design“TFD” Door is Locked • Hypothesis: CCC will send a text to open door • Test?
  • 25.
    Test First Design: Door is Locked
  • 26.
    Test First Design Dooris Locked • Text to open door • Customer Value – Easy Access – Feel Trusted • Business Value – Allows capture of consumer data – Have customer phone number in case of theft – Notifications to sales person
  • 27.
    Test First Design WrongSizes • Hypothesis: CCC will scan barcode and request correct size • Test?
  • 28.
    Now, you doit. Wrong Sizes • Use paper and pencil • Come up with a hypothesis and a test for it • 5 minutes
  • 29.
    Test First Design: Wrong Size
  • 30.
    Test First Design WrongSizes • Scan barcode and Request Size • Customer Value – Don’t have to leave changing room – Personal Service • Business Value – Better service => more sales – Not in stock; prompt to order
  • 31.
    Agile - VS- Lean Startup Agile Lean Startup Product Roadmap Business Model Canvas Product Vision Product Market Fit Release Plan Minimal Viable Product Sprint Kanban Sprint Review Pivot or Persevere Decision On-Site Customer “Get Out Of The Building” User Story Hypothesis Backlog “To Learn” List Definition of Done Validated Learning Red-Green-Refactor Learn-Measure-Build Customer Feedback Customer Validation Acceptance Test Split Test Velocity AARRR Mock Object Feature Fake Continuous Integration Continuous Deployment Certified Scrum Master Customer Success Manager - Joshua Kerievsky
  • 32.
    Flash Builds • Watchthe Nordstrom Innovation Lab: Click this link http://www.youtube.com/watch?v=szr0ezLyQHY
  • 33.
    Flash Builds • Whatdid you see that was agile? • How did design happen?
  • 34.
    Review • UX • Agile • What Changes • What We Can Do • Agile/UX Practices – User Story Mapping – Lean Startup and Test First Design – Flash Builds
  • 35.
    Questions, @jonRstahl Comments? @DocOnDev 216.236.4705 jon.stahl@leandog.com doc@leandog.com

Editor's Notes