Agile User Experience
Design......Page 1
Chapter-1-Introduction-to-Agile_2013_Agile-User-Experience-Design.pdf......Page 0
Copyright......Page 2
About the Author......Page 3
Dedication......Page 4
Introduction......Page 5
Acknowledgment
......Page 6
D......Page 175
P......Page 176
U......Page 177
Y......Page 178
INTRODUCTION
......Page 166
CREATING A USER EXPERIENCE BACKLOG
......Page 167
BREAKING THE WORK IN TO SMALLER PIECES
......Page 168
RECURRING EVENTS AND RITUALS
......Page 169
NO DESIGN DIVAS OR HEROES
......Page 170
FOCUSING ON COMMUNICATION OVER
DOCUMENTATION
......Page 171
DEFINING ACCEPTANCE CRITERIA
......Page 172
SUMMARY......Page 173
INTRODUCTION
......Page 151
SHOULD WE EVEN BE AGILE?
......Page 152
HOW LONG SHOULD SPRINTS BE?
......Page 154
WHAT DELIVERABLES SHOULD UX PRODUCE?......Page 155
HOW SHOULD THE UX TEAM FIT IN
WITH THE DEVELOPMENT SPRINTS?......Page 157
HOW DO WE FIT USER RESEARCH INTO
THE SPRINT CYCLE?......Page 159
WHAT IF THE TEAM CLAIMS TO BE AGILE,
BUT AGILE VALUES ARE NOWHERE TO BE SEEN?......Page 160
WHAT IF THE TEAM IS NOT COLOCATED?......Page 161
HOW DOES THE UX TEAM PLAN AND RESEARCH
FOR THE NEXT RELEASE?......Page 162
HOW DO YOU MANAGE INTERNAL
STAKEHOLDERS?......Page 163
SUMMARY
......Page 164
Reference......Page 165
INTRODUCTION......Page 125
PROJECT OVER PROCESS......Page 128
TEAM DYNAMICS......Page 131
COMMUNICATION......Page 133
DEFINE THE BIG PICTURE......Page 137
TRAINING......Page 138
Book......Page 139
Online resources......Page 140
ADAPT AND EVOLVE......Page 143
References......Page 150
3 Case Studies
......Page 76
SUZANNE O’KELLY, APPNEXUS......Page 77
Key points......Page 81
THYRA RAUCH, IBM......Page 82
ARCHIE MILLER, SNAGAJOB.COM......Page 84
CAROL SMITH, PERFICIENT......Page 88
KAYLA BLOCK, PAR SPRINGER MILLER......Page 92
Key points......Page 96
ANONYMOUS 1, AT AN ENTERPRISE SOFTWARE
COMPANY......Page 97
CHRISTINA YORK, ITHAKA......Page 99
ANONYMOUS 2, A LARGE DESKTOP SOFTWARE
COMPANY......Page 104
AUSTIN GOVELLA, AVANANDE......Page 109
Key points......Page 113
JOSH O’CONNOR, NATIONAL COUNCIL FOR THE
BLIND, IRELAND......Page 114
ADRIAN HOWARD, QUIETSTARS......Page 115
ELISA MILLER, SENIOR USER EXPERIENCE
ENGINEER GE HEALTHCARE......Page 117
Key points......Page 122
References......Page 123
INTRODUCTION......Page 45
FITTING A UX PEG INTO AN AGILE-SHAPED HOLE......Page 48
Individuals and interactions over processes and tools
......Page 54
Specifications......Page 57
Tactics......Page 60
User research......Page 61
Tactics......Page 66
Usability testing reports......Page 67
Tactics......Page 69
Design activities......Page 70
Tactics......Page 71
SUMMARY......Page 74
References......Page 75
1
Introduction to Agile......Page 7
INTRODUCTION
......Page 8
AGILE VALUES + UX
......Page 10
Working software over comprehensive documentation
......Page 12
Customer collaboration over contract negotiation
......Page 13
Responding to change over following a plan
......Page 14
AGILE PRINCIPLES + UX
......Page 15
Principle 1 - Our highest priority is to satisfy the customerthrough early and continuous delivery of valuablesoftware......Page 16
Principle 3 - Deliver working software frequently, froma couple of weeks to a couple of months, with a preferenceto the shorter timescale......Page 17
Principle 4 - Business people and developers must worktogether daily throughout the project......Page 18
Principle 5 - Build projects around motivated individuals.Give them the environment and support they need, andtrust them to get the job done......Page 19
Principle 6 - The most efficient and effective method ofconveying information to and within a development teamis face-to-face conversation......Page 20
Principle 7 - Working software is the primary measureof progress......Page 21
Principle 8 - Agile processes promote sustainabledevelopment. The sponsors, developers, and users shouldbe able to maintain a constant pace indefinitely......Page 22
Principle 9 - Continuous attention to technical excellenceand good design enhances agility......Page 23
Principle 10 - Simplicitydthe art of maximizing theamount of work not donedis essential......Page 24
Principle 12 - At regular intervals, the team reflects onhow to become more effective, then tunes and adjustsits behavior accordingly......Page 25
Extreme Programming (XP)......Page 26
Scrum......Page 27
Hybrid agile, or custom agile......Page 29
Kanban......Page 31
Scrumban......Page 32
Lean UX......Page 33
Product owner......Page 34
Scrum master......Page 35
Product backlog......Page 36
User stories......Page 37
Story-point estimation......Page 38
Burn-down chart......Page 40
AgileFall......Page 41
Jeff Patton......Page 42
References......Page 44