UX meets XP

Overview of core approachesto creating interactive software

Waterfall, iterative design, AgileHybrid methods of evaluation

H&P Chapter 19

H&P Chapter 2, p73-4

© 2013 - Brad Myers 4

Hartson-Pyla steps:parallel track iterations

• Software engineers and UX team both iterate

• Focus on iterating early when cheaper and easier

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“

http://agilemanifesto.org/

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. 19-110© 2013 - Brad Myers

Scrum vs. traditionalsoftware development

11Michael Budwig, http://doi.acm.org/10.1145/1520340.1520434

© 2013 - Brad Myers

© 2013 - 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 ondesign

http://agileproductdesign.com/blog/emerging_best_agile_ux_practice.html

Prototypes aren’t a deliverable; they’re a communication toolhttp://asinthecity.com/2011/07/19/prototypes-arent-a-deliverable-theyre-a-communication-tool/Ben Melbourne

Doing UX in an Agile World: Case Study Findingsby Hoa Loranger on May 26, 2014

http://www.nngroup.com/articles/doing-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. …

• 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. …

• UX Must Work at Least One Step Ahead of the Sprint”

Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 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. 3075-3084. http://doi.acm.org/10.1145/1520340.1520434

• Separate UX team, worked 1 or 2 sprints ahead of developer teams

• Design vision sprint every 3-6 months• Worked well

16

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

UX team

Dev Scrum team

Sprint 0VisionSprint

VisionSprint

© 2013 - Brad Myers

See also Fig. 19-7in textbook

http://www.guindo.com/blog/visiones-sesgadas-de-la-experiencia-de-usuario/

Zen Ex Machina – The blog March 2013http://zenexmachina.wordpress.com/2013/03/28/lean-ux-is-it-really-about-start-ups-or-something-more-profound/

https://twitter.com/jmspool/status/518071262653210624/photo/1

© 2013 - Brad Myers 19