agile & ux: how to make it work

11
Discussion Anders Ramsay & Claudia Oster UXcamp Europe 2011 AGILE & UX: HOW TO MAKE IT WORK

Upload: claudia-oster

Post on 27-Jan-2015

109 views

Category:

Documents


2 download

DESCRIPTION

Summary of the discussion/workshop about Agile & UX hosted by Anders Ramsay & Claudia Oster at the UXcamp Europe 2011 in Berlin.

TRANSCRIPT

Page 1: Agile & UX: How to make it work

Discussion

Anders Ramsay & Claudia Oster

UXcamp Europe 2011

AGILE & UX: HOW TO MAKE IT

WORK

Page 2: Agile & UX: How to make it work

Anders Ramsay www.andersramsay.com @andersramsay

Claudia Oster usabilitytalks.blogspot.com @usabilitytalks

ANDERS & CLAUDIA

Page 3: Agile & UX: How to make it work

OUR EXPERIENCES

Page 4: Agile & UX: How to make it work

CARD STORMING & CLUSTERING

„WHAT ARE THE CHALLENGES YOU ARE FACING?“

Page 5: Agile & UX: How to make it work

No experience with agileDesign befor development startsHalf-baked UXScrum vs. UX

CHALLENGES - 1

Page 6: Agile & UX: How to make it work

Roles Involving Devs in UXWaterfall vs. AgileTransitions into Agile

CHALLENGES - 2

Page 7: Agile & UX: How to make it work

Dev-CentricNot enough time for user testingAgile Philosophy

CHALLENGES - 3

Page 8: Agile & UX: How to make it work

DISCUSSION

Page 9: Agile & UX: How to make it work

Sprint 0: 3 weeks - Developers are doing research on the technology and the Designers are doing the upfront analysis and design.

UX design is involved in creating the product vision: Actively engage the Developers in the design process (Collaborative Sketching, ... ) Devs have solutions that the UX designer wouldn't think of. This also can relate to a close relationship

Spreading competency of UXteam to Devs and vice versa should be part of the process

TOPIC 1DESIGN BEFORE DEVELOPMENT STARTS

Page 10: Agile & UX: How to make it work

Problem of proper planning: Product Manager need to take ownership and needs to share the goal of what should be the result at the end of the sprint/project.

Each team member should have a broader view of what problems they are solving. The product manager should communicate it. Instruments:a) Send all the material to everybody in the project.b) Requirement gathering session with the whole team to get

the inputc) Write down user stories and make the pland) Present again to the team and get feedback

TOPIC 1DESIGN BEFORE DEVELOPMENT STARTS

Page 11: Agile & UX: How to make it work

Each team member should explain in the standup exactly what they are doing and what problem they are solving and not using the daily standup as a high-level meeting. > Better understanding, communication in the team and commitment.

The team need to have the trust in what they are doing and what they should deliver.

Inside the team you need to get rid of the feeling of "guilt" and "failure„. The team need to be confi dent about the problem and the possibilities of improving.

The Scrum Master should take care of the tranisition and he should have knowledge of how to do that.

TOPIC 2TRANSITIONING INTO AGILE(UX COMING LATE IN THE PROJECT/PROCESS)