| |
|
 |
119 pages PDF format
Download your copy of the report instantly (from eSellerate)
$148 for a single report,
$298 for the report with a site license and the right to make copies within your organization and place on your intranet.
(No shipping/handling fees will be added: it's an immediate download directly from the server.)
|
|
|
Summary
|
|
Rapid Application Development (RAD) processes such as Agile, Scrum, and the like, simultaneously pose an opportunity and a threat to achieving a quality user experience. It all depends on how it's handled.
The standard methodologies as described in books don't work in practice, if you care about the usability of your products. But small modifications work wonders, as we found when studying how Agile works on real projects.
The report contains detailed analyses of five trends we saw in most successful organizations:
- UX people are bridges: embedded with the team but also involved in high level/early planning
- UX work is early, flexible: done up-front to storyboard level with good expectation setting that changes will happen
- Low-fi prototype is the ongoing spec: owned by UX, agreed by stakeholders
- UX work happens in a parallel track: pair complex back-end sprints with UX intensive work
- Guerilla style UX validation: fast, discount methods run frequently and regularly on early code
The report is based on case studies from 16 organizations that have embraced Agile while also caring about user experience. Further adding to the empirical evidence in the report are the findings from surveying 174 professionals.
> Jakob Nielsen's Alertbox summarizing the report
|
|
Table of Contents
|
|
119-page report.
- Executive Summary
- The promise of Agile methods
- The threat of Agile methods
- Making Agile and usability work
- Introduction
- Agile — theory and history
- What is Agile/Rapid Application Development?
- The main elements of Agile
- Differences from other development processes
- Agile benefits for UX practitioners
- Agile in practice
- Partial Agile implementations
- Being the only Agile kid on the block
- The effects of poor Agile implementations
- Just do it!
- Agile in practice: Case study
- Challenges for UX practitioners
- Little up-front design time
- It's hard to talk about users when they are poorly defined
- Agile is developer-centric
- There is little time to test
- Agile is not conducive to a centralized UX team
- We have to do Agile by the book, and UX isn't in that book.
- Challenges: Case study
- Integrating UX into Agile teams
- User Experience people are bridges
- UX work is early, flexible
- Low-fidelity prototypes as specification document
- User Experience work happens in parallel
- Guerilla-style UX validation
- Integrating into teams: Case study
- Guerilla usability: quick-and-dirty techniques
- Early work
- Sprint-specific work
- Decoupled (holistic) work
- Post-sprint work
- Making it happen
- UX people have to embrace Agile too!
- Showing user needs to a fast-moving team
- Showing your value
- Essential techniques for short-staffed teams
- Special challenges for large and distributed teams
- Making it happen: Case Study
- Always room to grow
|
|
What You Get
|
|
- Information about what actually worked (and didn't work) in 16 companies that moved to Agile and still cared about user experience.
- Additional experience from the 174 professionals we surveyed.
- Many best practices you can follow when adapting Agile as described in books to actual development practices such that you won't suffer a loss of usability.
|
|
Comparing the Editions
|
|
If you already own the 1st edition of this report, should you buy the 2nd edition? Probably not, because the main conclusions in the first edition were confirmed in Study Two (though some were refined or extended in the new edition).
Comparison of the editions:
| |
1st edition |
2nd edition |
| Case Studies |
12 |
16 |
| Professionals Surveyed |
105 |
174 |
| Page count |
95 |
119 |
| Report file size |
1 MB |
2 MB |
|
|
Who Should Read This Report?
|
|
This report has important information for:
- Usability specialists, interaction designers, and other user experience professionals in organizations that have moved (or are thinking of moving) to an Agile development methodology.
- Anybody in charge of an organization's development methodology, if they don't want to see drastically reduced user experience quality after moving to Agile.
Please help us continue to publish low-price reports by buying a site license if you have colleagues who will read the report. If you only need it for yourself, then that's what the single-user license is for. If somebody "gives" you a copy, then please buy a download anyway to keep prices down in the future.
 |
Download Report (from eSellerate)
$148 for the PDF file (119 pages)
$298 for site license to make copies
|
|
|
| |
|
|
|
|
Alternative Payments |
If you do not want to buy online, we accept other forms of payment:
- Check
- Bank transfer
- Purchase orders
- Faxed or mailed credit cards
We can also send you a paper invoice if your company requires that.
|
|
File Format Used |
The report is a standard PDF file, formatted to print on both 8.5x11 and A4 paper. Any recent version of the Acrobat Reader will suffice to read or print the file. No special software is needed. The file is not copy-protected: we trust you to buy a site license if you are going to have multiple people read the report.
|
|
|