Agile Design in Practice

Post on 29-Nov-2014

701 views 2 download

description

Linda Luu - Agile East 2011 New York ThoughtWorks

Transcript of Agile Design in Practice

Linda Luu • Agile East 2011

Photo  from

 Flickr  –  cou

rtesy  of  3oh

eme    

Financial Services + Product Development + Design Sydney → Atlanta → Calgary → Seattle

WHAT IS AGILE DESIGN?

Concept Envisioning Iteration 0 Iteration 1 Release

‘Traditionally” user feedback is late in the delivery process...

…   …  

✘ ✘ ✘ ✘ ✘ ✔ ✔  Customer

Engagement

Delivery Process

Concept Envisioning Iteration 0 Iteration 1 Release

Agile design engages users early and often

…   …  

✔ ✔ ✔ ✔ ✔ ✔ ✔  Customer

Engagement

Delivery Process

And prototyping for fast, rapid feedback with users & stakeholders

How?

Design › Test › Build Design › Test › Build Ideas › Test Ideas › Test Ideas › Test Design › Test

Concept Delivery

A framework

Part 1 Creating the concepts

Part 2 Short iterations of design › test › build

Inception

Part 1: Creating the concepts

Research Ideas Test & evaluate

“If I had asked people what they wanted, they would have said faster horses.”

— Henry Ford, Founder of Ford Motor Company

Case Study

Business Focus Strategy + Design + BA + Tech Lead / Architect

Delivery Focus Business + Design + BA + Tech Lead + Developers

Checkpoint: Project Inception

Design › Test › Build Design › Test › Build Ideas › Test Ideas › Test Ideas › Test Design › Test

Concept Delivery Inception

Are you ready to ramp up your delivery team?

So we’re all agreed then!

Part 2: Short cycles of design, test, build

Business Focus Strategy + Design + BA + Tech Lead / Architect

Delivery Focus Business + Design + BA + Tech Lead + Developers

Design › Test › Build Design › Test › Build Ideas › Test Ideas › Test Design › Test

Concept Delivery Inception

Ideas › Test

10 – tried & tested techniques –

TO GET YOU UNSTUCK

1 Ramp up your dev team when you have a concept

agreed and tested.

2 Design for

everyone and you design for no one

3 People design better

together.

Will customers buy it?

Is it feasible?

4 Is it viable?

Successful solutions live here

5 Keep it visual.

6 Greenhouse. Never sh*!house.

7 Stay ahead, but not too far ahead.

“The developers are chomping on our h!ls again!”

8 Focus on the minimum

viable prototype.

9 The software is

the deliverable.

10 The design

is never finished.

How is this different?

  Just enough of a concept, tested with users, to begin development

 Designers imbedded in project teams

  Short, iterative cycles of design, test, build

 Cross-functional teams (full-time)

  Team collaboration space & wall

  Just enough design (low fidelity)

  Just enough research

  Focus on working software as the deliverable

The benefits

 Ability respond to change

 Customer focused culture

 Avoiding rework of obvious usability issues

  Implementing a design that is true to concept

 Continuous feedback loop

 Clarity of investment at governance level

  Seed funding to further explore concepts outside annual funding process

“Fail early and often, in order to succeed sooner.”

— Tom Kelley, IDEO

I’d love to hear from you! linda.luu@thoughtworks.com