Successful Agile/UX

115
Successful Agile/UX Jeremy Kriegel UX Manager, CIDC

description

 

Transcript of Successful Agile/UX

Page 1: Successful Agile/UX

SuccessfulAgile/UXJeremy Kriegel

UX Manager, CIDC

Page 2: Successful Agile/UX

UXAgile

Page 3: Successful Agile/UX

Culture is not about what is absolute, real, or true. it’s about what a group of people get together and agree to believe.

Culture can be healthy or toxic, nurturing or murderous. Culture is made of stories...

—Thom Hartmann, author

Page 4: Successful Agile/UX
Page 5: Successful Agile/UX
Page 6: Successful Agile/UX
Page 7: Successful Agile/UX

Agenda

• Agile & Scrum Basics• Project Initiation• Design in Sprints

Page 8: Successful Agile/UX

Your Goals

• workflow in relation to web design/visual design• a list (or "toolbox") of UX design methods adjusted for Agile, that can be

used based on specific project needs (e.g., RITE testing, paired design/development, Design Studio, Story Mapping, etc.)

• More detail on Design Studio (a la Jim Ungar) and Story Mapping (a la Jeff Patton), and when they should take place?

• I attended the Bentley Usability Bootcamp in 2006. How out of date am I in my UCD approach?

• How can Agile work with 3 types of projects: Design from scratch, open source and implement commercial, off-the-shelf products?

• staggering design and code tasks• architecture and design done piecemeal• adding to a legacy application• design controls artifacts for the fda and agile

Page 9: Successful Agile/UX
Page 10: Successful Agile/UX
Page 11: Successful Agile/UX
Page 12: Successful Agile/UX
Page 13: Successful Agile/UX

18 minutes

Page 14: Successful Agile/UX

Any Questions?

Page 15: Successful Agile/UX
Page 16: Successful Agile/UX

Marshmallow Challenge Lessons

Page 17: Successful Agile/UX

Who does well?

Page 18: Successful Agile/UX

Who does well?

Page 19: Successful Agile/UX
Page 20: Successful Agile/UX
Page 21: Successful Agile/UX

Learn more marshmallowchallenge.com

Page 22: Successful Agile/UX
Page 23: Successful Agile/UX

http

://w

ww

.ena

gilit

y.co

m/

Page 24: Successful Agile/UX

Agile 101

Page 25: Successful Agile/UX

Agile is coming!

Page 26: Successful Agile/UX
Page 27: Successful Agile/UX
Page 28: Successful Agile/UX
Page 29: Successful Agile/UX
Page 30: Successful Agile/UX

A minute to learn, a lifetime to master

Page 31: Successful Agile/UX
Page 32: Successful Agile/UX

Why agile?• Faster value to market• More responsive to change• More collaboration• More control

Page 33: Successful Agile/UX
Page 34: Successful Agile/UX
Page 35: Successful Agile/UX

Discover Define

DesignDevelop

Deliver

Deploy

Decide

Defen

d

Page 36: Successful Agile/UX
Page 37: Successful Agile/UX
Page 38: Successful Agile/UX

Agile gives you the

to define a process that exactly meets your

needs

FREEDOM

Page 39: Successful Agile/UX

Agile gives you the

to define a process that exactly meets your

needs

RESPONSIBILITY

Page 40: Successful Agile/UX

Origin of Agile

Extreme

ProgrammingSCRUM

DSDM

Adaptive

Software

Development

Crystal

Feature-

Driven

DevelopmentPragmatic

Programming

Page 41: Successful Agile/UX

Agile Manifesto

4 Values

12 Principles

Page 42: Successful Agile/UX

Agile ManifestoWe are uncovering better ways of developing software by doing it

and helping others do it.

Through this work we have come to value:

Individuals & interactions

Working software

Customer collaboration

Responding to change

That is, while there is value in the items on the right, we value the items on the left more.

Processes & tools

Comprehensive doc

Contract negotiation

Following a plano

ver

Page 43: Successful Agile/UX

Agile Manifesto

4 Values

12 Principles

Page 44: Successful Agile/UX

Principles Behind Agile

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.

Page 45: Successful Agile/UX

Principles Behind Agile

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.

Page 46: Successful Agile/UX

Principles Behind Agile

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.

Page 47: Successful Agile/UX

Principles Behind Agile

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.

Page 48: Successful Agile/UX

Principles Behind Agile

Continuous attention to technical excellence and good design enhances agility.

Simplicity--the art of maximizing the amount of work not done--is essential.

Page 49: Successful Agile/UX

Principles Behind Agile

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.

Page 50: Successful Agile/UX

agilemanifesto.org

Page 51: Successful Agile/UX

Agile

Page 52: Successful Agile/UX

Why

What

Page 53: Successful Agile/UX

SCRUM

Page 54: Successful Agile/UX
Page 55: Successful Agile/UX
Page 56: Successful Agile/UX
Page 57: Successful Agile/UX

SCRUM

3 Roles

4 Rituals

3 Artifacts

Page 58: Successful Agile/UX

Roles

• Product Owner• Team• Scrum Master• Stakeholder

Page 59: Successful Agile/UX

Pigs & Chickens

Page 60: Successful Agile/UX

Product Backlog

Value

Outcome

Feature

Work

Bug

Page 61: Successful Agile/UX

Iteration Planning

Product Backlog Iteration Backlog

Page 62: Successful Agile/UX

WARNINGNO SCOPE CHANGES

except…

Page 63: Successful Agile/UX

Daily Scrum

Page 64: Successful Agile/UX

The 3 Questions

• What have you done since the last meeting?

• What will you be working on until the next meeting?

• Are you blocked?

Page 65: Successful Agile/UX

Burndown

Page 66: Successful Agile/UX

Demo

Page 67: Successful Agile/UX

Retrospective

Page 68: Successful Agile/UX

Insanity

Page 69: Successful Agile/UX

Iteration PlanningProduct Backlog

New Iteration Backlog

Undone Work

Page 70: Successful Agile/UX

Overview

Product Backlog

Iteration Backlog

Iteration

Scrum

Working Software

IterationPlanning

Demo & Retro

Page 71: Successful Agile/UX

Snowman

Release

Iteration

Scrum

Page 72: Successful Agile/UX

Caveats

Page 73: Successful Agile/UX

J CurveProductivity

Time

Page 74: Successful Agile/UX

Any cooks?

Page 75: Successful Agile/UX
Page 76: Successful Agile/UX
Page 77: Successful Agile/UX

Other negatives

• Rework• Missed edge cases• Overemphasis on deadlines &

engineering

Page 78: Successful Agile/UX

A lot of potential• Real feedback faster• Closer ties to stakeholders and

developers• Faster, less effort on low importance

features• Pervasive understanding of UX• Real User focus• Less waste, decide as late as

responsible

Page 79: Successful Agile/UX
Page 80: Successful Agile/UX

Process design is what we do

Page 81: Successful Agile/UX

The Project

Page 82: Successful Agile/UX

Patients Dr. & Staff Pharmacists

Page 83: Successful Agile/UX

Getting Started

Page 84: Successful Agile/UX

Sprint 0

Page 85: Successful Agile/UX

Sample Goals• Define problem/benefit• Prioritized and measurable

goals• Contractual obligations• Target users and their goals• Key assumptions that need to

be validated by research

• Relationship of users to business goals

• User tasks or scenarios• Refined, estimated, and

prioritized stories• Release roadmap

Page 86: Successful Agile/UX

Done?

Page 87: Successful Agile/UX

Specific

Measurable

Achievable

Relevant

Timelyhttp://www.projectsmart.co.uk/smart-goals.html

Page 88: Successful Agile/UX

Who?

Page 89: Successful Agile/UX

User Stories

Page 90: Successful Agile/UX

User Stories

As a (persona) ,

I would like to (action) ,

so that (value) .

Page 91: Successful Agile/UX
Page 92: Successful Agile/UX

Photo by David Paul Ohmerhttp://www.flickr.com/photos/the-o/

Page 93: Successful Agile/UX
Page 94: Successful Agile/UX

example

As a gardener, I want a shovel so that I can dig a hole

As a gardener, I want to dig a hole so that I can plant a tree

As a gardener, I want to plant a tree so I can have some shade.

Page 95: Successful Agile/UX
Page 96: Successful Agile/UX

Images via ifixit.com

Page 97: Successful Agile/UX
Page 98: Successful Agile/UX

INVEST in Stories

Independent

Negotiable

Valuable

Estimable

Small

Testable

Page 99: Successful Agile/UX

Write Stories

Page 100: Successful Agile/UX

Story Map

Page 101: Successful Agile/UX
Page 102: Successful Agile/UX
Page 103: Successful Agile/UX

Demo

Page 104: Successful Agile/UX

Retro

Page 105: Successful Agile/UX

Planning

Page 106: Successful Agile/UX

Go!

Page 107: Successful Agile/UX

Demo

Page 108: Successful Agile/UX

Retro

Page 109: Successful Agile/UX

Planning

Page 110: Successful Agile/UX

Go!

Page 111: Successful Agile/UX

Demo

Page 112: Successful Agile/UX

Retro

Page 113: Successful Agile/UX

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

Vision

Page 114: Successful Agile/UX

Final thoughts

Page 115: Successful Agile/UX

One last thinghttp://speakerrate.com/jkriegel