1

Agile + UXBuilding the right way + Building the right thing

Agile UX Success!

2

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Agile PrinciplesUX works with Dev

Minimum Lovable Product

UX is user advocate

UX is data driven change

3

Guerilla UX Research + agile + lean

4

Validating learning loop

5

“The difference between learning and failure is how much money you spend to do it.”

—David Hussman

6

PM/PO collaborates with UX to deliver one or two sprints ahead of development

Timing of Tactical UX Activities

Developers, UX, etc.

Scrum Master

Product Owner

Scrum Team

R1S1 R1S2 R1S3 R1S4 R1S5 R1S6 R1S7 R1S8Development Workstream

UX Design & architectureWorkstream

7

Developers work with UX to decide which functionality/user stories to work on

Collaboration: Tactical UX Activities

Developers, UX, etc.

Scrum Master

Product Owner

Scrum Team

R1S1 R1S2 R1S3 R1S4 R1S5 R1S6 R1S7 R1S8Development Workstream

UX Design & architectureWorkstream

8

During sprint, UX produces: User research about the usability, usefulness, desirability

of the application or solution

Interaction design guidance

UI design guidance

Non-functional requirements (standards, principles, etc.)

Tactical UX Deliverables

9

PM/PO collaborates with UX to deliver early in the product planning process.

The goal is to deliver data and knowledge to drive the product design so we are building the right thing

Then there is STRATEGIC UX

10

-- assumptions about our product, our design, our users

Testing our assumptions

11

Constant, daily interaction

Working together

12

acts as user advocate

answers questions, clarifies requirements

may be tasked with research

UX at Standups

13

UX continually available for collaboration outside of scrums

Collaboration

14

Definition of done: all UI devs must work with UX before it can be called done

A guideline

15

Always dedicate some holdback to meeting UX standards and non-functional requirements

When planning sprints

16

• UX works one sprint ahead

• Agile = build it the right way

• UX = build the right thing

Otherwise, rework is costly!!

UX isn’t a bottleneck

17

Participation in Community of Practice

Key to success

18

Forum for exchange

Focus on intersection of development, user experience, and graphical user interfaces

Reinforces consistency across applications

Venue for communicating changes to UX guidelines, standards, ng-Components

A place for suggestions and questions/answers around the topic

What is a Community of Practice?

19

Who Promoted by Joao Ribeiro (UX) and Michal Margiel (Portal 8).

All dev teams should attend and contribute

Where Meetings held via WebEx

Email kelley.howell@redacted.com to be added

When TBA for US location

Mondays 11h30 CET for Europe/India

Who, where, when is the CoP?

20

Non-functional requirements

21

Any questions? Comments?

Thank you!

UX TeamKelley Howell, UX Architect