UX meets XP

Overview of core approaches to creating interactive software Waterfall, iterative design, Agile Hybrid methods of evaluation H&P Chapter 19

H&P Chapter 2, p73-4

Hartson-Pyla steps: parallel track iterations Software engineers and UX team both iterate Focus on iterating early when cheaper and easier © Brad Myers4 Fig 2-11

Agile Manifesto “Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan “

Principles behind the Agile Manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Principles behind the Agile Manifesto Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile elements User stories Acceptance tests Engineering tasks Unit tests Implementation Code testing Acceptance testing and deployment

Agile forms XP – eXtreme Programming SCRUM

Waterfall, Iterative, XP Fig © Brad Myers

Scrum vs. traditional software development 11 Michael Budwig, © Brad Myers

Issues with Agile UX Created by programmers, not designers UI might be patchwork of non-integrated pieces Reducing documentation  not capturing design rationale No mention of iteration on design

Prototypes aren’t a deliverable; they’re a communication tool communication-tool/ Ben Melbourne

Doing UX in an Agile World: Case Study Findings by Hoa Loranger on May 26, 2014Hoa Loranger ing-ux-agile-world/

“Unfortunately, most teams don’t conduct user research on a consistent basis, if at all. … However, discount usability methods can accommodate short timelines as needed. …discount usability methods Skipping user research is extremely risky. … The good news is Lean UX techniques such as sketching, wireframing, and paper prototyping have gained support. Designers are encouraged to create low-fidelity prototypes as a way to demonstrate ideas and reduce heavy documentation. The downside is that many organizations are not testing them with target users. …paper prototyping UX Must Work at Least One Step Ahead of the Sprint”

Sprint 0Sprint 1Sprint 2Sprint 3Sprint 4Sprint 5Sprint 6 Report from PayPal Courtesy: Michael Budwig, User Experience Manager, Customer Experience and Merchant Solutions, PayPal, “When user experience met agile: a case study”, SIGCHI’2009, pp Separate UX team, worked 1 or 2 sprints ahead of developer teams Design vision sprint every 3-6 months Worked well 16 Sprint 1Sprint 2Sprint 3Sprint 4Sprint 5Sprint 6 UX team Dev Scrum team Sprint 0 Vision Sprint © Brad Myers See also Fig in textbook

usuario/

Zen Ex Machina – The blog Zen Ex Machina – The blog March about-start-ups-or-something-more-profound/

© Brad Myers19

Write user stories around privacy We spend a lot of time designing features—features that users experience. But things that happen in the background of an experience can still constitute bad UX. One way to bring privacy into the conversation early on is to write user stories around a privacy epic. Here are some examples based on an online store: As an online shopper, I want to know why the store requires my phone number because I feel uncomfortable giving it out, and it seems irrelevant to making a purchase. As an online shopper, I want to have a choice over whether and how the store uses my search history so that I have control over my data. As an online shopper, I want to have the option for my purchase history to inform recommendations the store makes so that I can shop more efficiently. As an online shopper, I want to know how the store uses my data so that I can make an informed decision about whether I want to shop there. As an online shopper, I want my purchase history to remain under the purview of the relevant business so that I do not receive unsolicited marketing. As an online shopper, I want my purchase history to default to private until I tell the store they may use it. Turn privacy into a feature Prioritizing privacy can also lead to clearer product designs, as in Microsoft’s recent expansion of its privacy policy: