The Internet belongs to everyone. Let’s keep it that way.

Protect Net Neutrality
Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Agile Experience Design

No description
by

Hoby Van Hoose

on 13 October 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Experience Design

Agile UX Practices
Barriers
Without benefits there is no reason to do Agile.
Do it right or you won't see benefits.

What are your "secrets to success"? Do any of them conflict with Agile practices? Map them to principles or be forever resistant.

Direct vs document communication
Favoring process vs people
Transparency vs big reveals
Two timeline
Summary
Quality
Quality to dev team
Quality to executives
Quality to end users

The right quality at the right time

Continuous improvement
Pairing
Same-practice

Cross-functional

Working sessions

Live Design
Testing
Documents
Open

Version controlled

Trailing

Pattern libraries

Light weight
Coverage
Barriers
Benefits
At first it feels weird and wrong. That's okay, it's natural.

Justifying individual hours vs team hours.

Improved quality not always apparent.

It DOES require more effort.
Full transcript