- Includes hands on, real-world examples to illustrate the successes and common pitfalls of Agile UX
- Introduces practical techniques that can be used on your next project
- Details how to incorporate user experience design into your company's agile software/product process
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.
UX, HCI, and Interaction Professionals
Agile User Experience Design, 1st Edition
About the Author
Chapter 1. Introduction to Agile
Agile Values + UX
Agile Principles + UX
Chapter 2. Agile Methods + UX = Agile UX
Fitting a UX Peg Into an Agile-Shaped Hole
The UX Work
Chapter 3. Case Studies
Suzanne O’Kelly, AppNexus
Thyra Rauch, IBM
Archie Miller, Snagajob.com
Carol Smith, Perficient
Kayla Block, PAR Springer Miller
Anonymous 1, at an Enterprise Software Company
Christina York, ITHAKA
Anonymous 2, a Large Desktop Software Company
Austin Govella, Avanande
Josh O’Connor, National Council for the Blind, Ireland
Adrian Howard, Quietstars
Elisa Miller, Senior User Experience Engineer GE Healthcare
Chapter 4. Common Success Factors
Project Over Process
Define the Big Picture
Adapt and Evolve
Chapter 5. Frequently Asked Questions
Should we Even be Agile?
How Long Should Sprints Be?
What Deliverables Should UX Produce?
How Should the UX Team Fit in With the Development Sprints?
How do you Get Developers to Talk About the Design of One Thing While They are Busy Implementing Another?
What if UX Team Members have to Support more than one Project?
How do we Fit User Research into the Sprint Cycle?
What if the Team Claims to be Agile, but Agile Values are Nowhere to be Seen?
What if the Team is not Colocated?
What do i do When Someone Uses “That’s not Agile” As a Reason not to do Something?
How Does the UX Team Plan and Research for the Next Release?
How do you Manage Internal Stakeholders?
Chapter 6. Using Agile Concepts for UX Teams
Creating a User Experience Backlog
Recurring User Testing
Breaking the Work in to Smaller Pieces
Constant Feedback and Iteration
Recurring Events and Rituals
No Design Divas or Heroes
Focusing on Communication Over Documentation
Defining Acceptance Criteria
Using Less Up-Front Design