This document discusses the differences between technology natives and immigrants and how this affects user experience (UX) design. It notes that natives have never known life without being connected and expect good UX, unlike immigrants. This shift requires UX design to go beyond superficial design and necessitates specialized skills in areas like information architecture and interaction design. The document also discusses how agile development methods like Scrum and Kanban can be merged to support both design and development work, with Kanban feeding stories to the Scrum team.

1. VERACITY AGILE UX
2013
Building great teams, great products, great companies ™

2. Changing User Experience
Technology Natives versus Technology Immigrants
Immigrants
Remember edlin, DOS, batch files, and thought ASCII art was cool
Adapted as technology changed
Remember life without the internet
Are more willing to accept bad UX Design
Natives
Have NEVER known life without being connected
Have never used low resolution displays
EXPECT all applications to have good UX
This shift has changed the level of skill needed for UX
UX is no longer the same as “Making it pretty with curved corners”

3. Design in the 80’s

4. Design in the 90’s

5. Design in 2000’s

6. Design in 2010

7. Adapting to the new Expectations
Most developers can no longer do design!
They simply don’t have the skills they need
Designers need specialized skills
Information Architecture
Interaction Design
Visual Design
User Interface Development
Design must focus on the needs of the end user, not the
developer

10. Veracity Agile Project Management
INCEPTION
ELABORATION
CONSTRUCTION
SPRINT 1
BUSINESS
MODELING
DISCOVERY
& VALIDATION
PROJECT
PLANNING
USER EXPERIENCE
DESIGN
ARCHITECTURE
IMPLEMENTATION
TESTING
DEPLOYMENT
ENVIRONMENT
SPRINT 2
SPRINT 3
[TRANSITION]
...
SPRINT N

11. Merging Design and Development
Scrum is GREAT for Development
Scrum forces designers to:
Estimate creative tasks that aren’t well defined
Do all of their work in short periods of time
Swarm on stories
What would Mona Lisa look like if 5 artists painted it at the same time?
Clearly, Scrum doesn’t work so well for Designers
How do we merge them?
Veracity has spent years trying to understand what works best
Kanban feeding the Scrum team has worked best so far

12. What is KanBan
Based on Lean Manufacturing
Quite simple
Uses Swim Lanes and Cards to show story progress
Measures in terms of Throughput, not Velocity
Doesn’t require up front estimation of tasks

13. KanBan Visually
Product Backlog
Story
Story
Story
Story
Swim Lanes
Working (Many
Lanes)
Ready for
Scrum
Story
Story
Story
Story
Story
Sprint Backlog
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Low Priority on Bottom

15. Workstreams for Kanban
Business
Alignment
Market and
User
Research
Personas
Design and
Prototyping
Development
and Platform
Understand
Business
Vision
3rd Party
Investigation
Persona
Profiles
Flow
Mapping
Flow-State
Charting
Identify
Feature Sets
& Solutions
On-Site
Visits
Scenarios
Prototyping
Story
Creation &
Review
Product
Roadmap
Internal /
External
Research
Review
Proof Of
Concept
Proof Of
Concept
Review,
Test,
Pivot
Review,
Test,
Pivot
Visuals
Ready To Run
Inform
Design, Implementation, Test, Validate

17. Q&A