Agile user experience design : a practitioner's guide to making it work

cover image

Where to find it

Information & Library Science Library

Call Number
QA76.76.D47 B76 2013
Status
Available

Authors, etc.

Names:

Summary

Being able to fit design into the Agile software development processes is an important skill in today's market. There are many ways for a UX team to succeed (and fail) at being Agile. This book provides you with the tools you need to determine what Agile UX means for you. It includes practical examples and case studies, as well as real-life factors to consider while navigating the Agile UX waters. You'll learn about what contributes to your team's success, and which factors to consider when determining the best path for getting there. After reading this book, you'll have the knowledge to improve your software and product development with Agile processes quickly and easily.

Contents

  • Introduction p. xi
  • Acknowledgment p. xii
  • About the Author p. xiii
  • Chapter 1 Introduction to Agile p. 1
  • Introduction p. 2
  • Agile Values + UX p. 4
  • Agile Principles + UX p. 9
  • Common Methods p. 20
  • Common Terms p. 28
  • Case Study-Jeff Gothelf, TheLadders.com p. 36
  • Summary p. 38
  • Chapter 2 Agile Methods + UX = Agile UX p. 39
  • Introduction p. 39
  • Fitting a UX Peg Into an Agile-Shaped Hole p. 42
  • The UX Work p. 48
  • Case Study-Catherine Robson, Seachange International p. 66
  • Summary p. 68
  • Chapter 3 Case Studies p. 71
  • Introduction p. 72
  • Suzanne O'Kelly, AppNexus p. 72
  • Thyra Rauch, IBM p. 77
  • Archie Miller, Snagaiob.com p. 79
  • Carol Smith, Perficient p. 83
  • Kayla Block, PAR Springer Miller p. 87
  • Anonymous 1, at an Enterprise Software Company p. 92
  • Christina York, ITHAKA p. 94
  • Anonymous 2, a Large Desktop Software Company p. 99
  • Austin Govella, Avanande p. 104
  • Josh O'Connor, National Council for the Blind, Ireland p. 109
  • Adrian Howard, Quietstars p. 110
  • Elisa Miller, Senior User Experience Engineer GE Healthcare p. 112
  • Summary p. 118
  • Chapter 4 Common Success Factors p. 121
  • Introduction p. 121
  • Project Over Process p. 124
  • Team Dynamics p. 127
  • Communication p. 129
  • Define the Big Picture p. 133
  • Training p. 134
  • Adapt and Evolve p. 139
  • Case Study-Sarah Kahn, Adzerk p. 140
  • Case Study-Anonymous 3, a Company Specializing in Direct Marketing Products p. 143
  • Summary p. 146
  • Chapter 5 Frequently Asked Questions p. 147
  • Introduction p. 147
  • Should we Even be Agile? p. 148
  • How Long Should Sprints Be? p. 150
  • What Deliverables Should UX Produce? p. 151
  • How Should the UX Team Fit in With the Development Sprints? p. 153
  • How do you Get Developers to Talk About the Design of One Thing While They are Busy Implementing Another? p. 155
  • What if UX Team Members Have to Support More Than One Project? p. 155
  • How do we Fit User Research Into the Sprint Cycle? p. 156
  • What if the Team Claims to be Agile, but Agile Values are Nowhere to be Seen? p. 157
  • What if the Team is not Colocated? p. 158
  • What do i do When Someone Uses "That's not Agile" As a Reason not to do Something? p. 158
  • How Does the UX Team Plan and Research for the Next Release? p. 159
  • How do you Manage Internal Stakeholders? p. 160
  • Summary p. 160
  • Chapter 6 Using Agile Concepts for UX Teams p. 163
  • Introduction p. 163
  • Creating a User Experience Backlog p. 164
  • Recurring User Testing p. 165
  • Breaking the Work in to Smaller Pieces p. 165
  • Constant Feedback and Iteration p. 166
  • Referring Events and Rituals p. 166
  • No Design Divas or Heroes p. 167
  • Focusing on Communication Over Documentation p. 168
  • Thinking and Communicating in Terms of User Stories p. 169
  • Defining Acceptance Criteria p. 169
  • Using Less Up-Front Design p. 170
  • Summary p. 170
  • Index p. 173

Other details