Copyright © 2006-13 The FatDUX, Cologne, Germany

AGILE FOR ALLUXcamp Europe 2013

Senior UX Designervs Product Owner

Stefan Böhland @spy23

LET YOUR CLIENTS BENEFIT FROM AGILE DEVELOPMENT METHODS AND KNOW HOW TO DO THE UX IN SUCH A PROJECT

Why we went agile

Fix launch date

+ Fix budget

+ Flexible scope

--------------------------

= SCRUM project

HOW IS IT TO BE A PRODUCT OWNER?

Product Owner vs. UX Designer

Product Owner

UXDesign

Content responsibility

IdeationProject controlling

Team coordination

Reports and presentations

Market- andcompetitor analysis

UX METHODS YOU CAN USE AS A PRODUCT OWNER

Sprint 0

Product backlog development

Scenarios Personas Customer Journeys

Epics & Stories Priorisation

Scenarios

Tool: wufoo.com

Personas

Customer Journey

Epics & Stories

Epics & Stories

Epics & Stories

Epics & Stories

Story prioritization

Business value with MoSCoW method

Customer preference with Kano model

Kampagnen

Story prioritization

Business value with MoSCoW method

Customer preference with Kano model

Kampagnen

Optiker Suche

Prioritized Product Backlog

SCRUM SPRINTS

Sprint 1 – Basics and news

Sprint 2 – Knowledge template

Sprint 3 – Campaigns

Sprint 4 – Profiles

Sprint 5 – Search

BENEFITS THE SPONSOR GETS

Velocity

We have developed a new portal in just 14 weeks

With Scrum you can be as fast as twice the speed of waterfall projects

Launch date guarantee, but no scope guarantee ;)

Flexibility

Change the scope without change requests

Dependencies to 3rd party service providers are easier to manage

Quality

The Scrum team feels responsible

Quality remains a team factor from start until the project ends

Transparency

Due to the restrict time boxing Scrum behalves like a good project plan

Sprint Review Meetings with product demos are like milestones

Your client is able to speak to the team during each product demo

The client can talk to the product owner at any time

WHAT WE HAVE LEARNEDTake-away

UX and Scrum

Be creative but do as much as possible in sprint 0

Three options for UX during Scrum sprits

Integrated UX sprint

Shifted UX sprint

Hybrid UX sprint

UX and Scrum

Integrated UX sprint

UX sprint nUX

DEV

Sprint n Sprint n+1

DEV sprint n

UX sprint n+1

DEV sprint n+1

The integrated UX sprint is hard. It puts UX under pressure at the beginning of each sprint and DEV at the end.

UX and Scrum

Shifted UX sprint

UX sprint n+1UX

DEV

Sprint n Sprint n+1

DEV sprint n

UX sprint n+2

DEV sprint n+1

UX runs ahead of DEV by the length of one sprint. This looks and feels like a small waterfall. More design artifacts may be created than necessary but the PO gets a chance to get approvals from stakeholders before DEV starts. The team is working on different stories at the same time which is not optimum for finding the best solution together.

UX and Scrum

Hybrid UX sprint

UX sprint n+1UX

DEV

Sprint n Sprint n+1

DEV sprint n

UX sprint n+2

DEV sprint n+1

We suggest you to try hybrid UX sprints. During the first half of each sprint UX and DEV are working together on the same stories. During the second half of the sprint the PO and UX prepare concepts for the planning meeting of the next sprint, do user tests and so on.

UX sprint n UX sprint n+1

Team room

Even if the Scrum project is not the only project the team members are working for

Reduces setup times and context switches

Boosts team communication

Experienced team members

Junior teams may have problems to handle their degree of freedom

The product vision needs to be clear

Hard acceptance criteria for each story are helpful

What’s not written in the story doesn’t belong to the story. Thus it doesn’t need to be done ;)

More small stories

A story shouldn’t be larger than the team velocity.

Your backlog is your backlog

In our customer journey workshop we have collected more than 100 stories. During the project we have finished a quarter of them.

Thank you!

Stefan Böhland

@spy23slideshare.net/spy23