Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

57
IMPACT DRIVEN SCRUM DELIVERY HOW TO DELIVER DESIRABLE PRODUCTS #impactmapping #impactmanagement #UX @ingriddomingues @HeedTheNeed

Transcript of Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Page 1: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT DRIVEN SCRUM DELIVERY

HOW TO DELIVER DESIRABLE PRODUCTS

#impactmapping #impactmanagement #UX @ingriddomingues @HeedTheNeed

Page 2: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

INGRID DOMINGUES

@ingriddomingues

STOCKHOLM GÖTEBORG MALMÖ

SARA LERÉN

@HeedTheNeed

Page 3: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHAT IS THIS ”IMPACT DRIVEN DELIVERY”

THING

HOW CAN IT HELP YOU?

AND

Page 4: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT

MAPPING MAP

MANAGEMENT Framework

Task

Model

Page 5: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT

MAPPING MAP

MANAGEMENT Framework

Task

Model

Page 6: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT MAP

Page 7: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT MAP EFFEKTKARTA ®

Page 8: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY

IMPACT MAP EFFEKTKARTA ®

Page 9: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY

HOW

IMPACT MAP EFFEKTKARTA ®

Page 10: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY

HOW

WHAT

IMPACT MAP EFFEKTKARTA ®

Page 11: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

Page 12: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER BEHAVIOURS

NEEDS

CAPABILITY

FUNCTIONS

Page 13: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER BEHAVIOURS

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS and GENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 14: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

A few defined rules and structures makes the Impact Map a solid ground for design, planning and quality assurance, thus delivering desired value:

1. The WHY must consist of at least two actionable metrics with a timeframe

2. The HOW must be based on user studies, even if rudimentary

3. The HOW must be prioritized, based on impact on the WHY

4. Every point in the chain from WHY to WHAT should add a clear value

Page 15: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

#impactmap describe metrics

for desired outcome

Page 16: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS and GENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 17: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

START WITH DOMAINS

• Productivity

• Effectiveness

• Learning

• Customer satisfaction

• Recurrent customers

• Conversion

• Correctness

• Brand awareness

• Recommendation

• Learnability

• …

Page 18: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

CONTINUE WITH METRICS

Something that people think, feel or do when (or after) using the product

= there must be a causality

Page 19: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

SOME EXAMPLES ON METRICS

LEARNING

20% of visitors should move between 2 or more content types (learning, treatment, knowledge…)

80% of visitors shold consider that they have reached a much greater understanding on ….

GENERATE LEADS

5% of visitors to pages with ”contact me” button should fill in the form

Page 20: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

OBJECTIVE METRICS

QUANTITATIVE METHODS

QUALITATIVE METHODS

SUBJECTIVE METRICS

OBSERVED BEHAVIOUR Log analytics, user testing & field studies • Visitor behaviour • Success rate

ANALYSED OPINIONS User testing, in-depth interviews, focus groups • Attitudes • Explained behaviour

MEASUREMENTS Log analytics, absolute measurements

• No. of mistakes • Conversion rate

• No. of returning customers • Task time

MEASURED OPINIONS Surveys

• Attitudes

• Satisfaction • Estimated time spent

• Estimated quality

Page 21: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

MEANINGFUL AIMS/SLOGANS

• Consists of one sentence

• Summarises the metrics

• Describes the value that the solution brings to the business

Page 22: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 1 Metrics

Page 23: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 1 - METRICS

● Write metrics. 10 min.

● Read the aim and the domains

● Think about how to measure success

● Write at least one metric for each domain

● Presentation and discussion

Tip: Think about quantitative vs. qualitative methods, subjective vs. objective metrics.

Page 24: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS and GENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 25: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 26: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 27: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 28: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

The Eager

Page 29: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

The Focused

Page 30: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Spends time thinking about interior decoration and smart solutions for their own home, or even other peoples homes. Collecting smart and beatutiful solutions for now or the future, and likes to share their ideas with others.

NEEDS • Wants to be inspired about new design and renovations • Wants to daydream

The Dreamer ”This could be very nice when...”

Page 31: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 32: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

PRIORITISE

• Will give guidance for the project:

– Release plan

– Design

– Cuttings

• Defined by business managers. Based on:

– Number of users

– Activity

– Impact on others

Page 33: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

NEEDS

• A sentence that starts with either

– WANTS – close at heart

– MUST – resistance

• The sentence should give guidance for validating designs e.g ”wants to easily check what she has paid for”

Page 34: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

MEANINGFUL NEEDS

• Describes why the product or service is used

• Shall make it possible to know what is needed to satisfy the user

• Avoid talking about functions, keep asking ”Why?” until you get to the real need

Page 35: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 2 Users

Page 36: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 2 - USERS

● Name the users. 10 min.

● Read the user descriptions

● What sets them apart from each other?

● Come up with a name for each user that summarizes the description

● Presentation and discussion

Tip: Think about usage patterns, not demographics. E.g. ”The Busy Bee” instead of ”Female, age 37.”

Page 37: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

IMPACT

MAPPING MAP

MANAGEMENT Framework

Task

Model

Page 38: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

• Aim for sustainability

• Design for behaviours

• Test in use

• Decide on outcome

Page 39: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 40: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 41: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Ability to make investment decisions

Page 42: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Ability to make investment decisions

HIGH

LOW

Page 43: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Consequences of fail

Page 44: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Consequences of fail

SEVERE LIMITED

Page 45: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Ability to make investment decisions

HIGH

LOW

Consequences of fail

SEVERE LIMITED

http://www.infoq.com/articles/most-impact-mapping

Page 46: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Evaluate hypothezis

User Stories with UX acceptance criterias

Validate that design meets user needs

Validate that long-term metrics are met

EVALUATE SUCCESS – Early and continuously

Page 47: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

#impactmanagement makes it possible to validate ideas and deliveries along the

way

Page 48: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 3 Design evaluation

Page 49: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

WHY IMPACT ON BUSINESS

HOW IMPACT ON USE

WHAT SOLUTION

AIM or SLOGAN

DOMAIN and its METRICS

USER and her

NEEDS

CAPABILITY and its

FUNCTIONS

SCOPING

MEASURING LONG-TERM SUCCESS

PRIORITIZING

TESTING DESIGN

EVALUATING SOLUTIONS and GENERATING SUGGESTIONS

GROUND FOR SPECIFICATION

Page 50: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

EXERCISE 3 - EVALUATION

● Pick a design. 10 min.

● Study the impact map

● Study the two different designs

● Based on the impact map, decide which design is best

● Presentation and discussion

Tip: Which design can best help create the desired impact? Which design will satisfy the needs of the highest prioritised user?

Page 51: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 52: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015
Page 53: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

PRODUCT STRATEGY

Product Owner

UX Lead

- Buliding the right thing

- Thinking far ahead

DELIVERY

Scrum Master

Team

- Building in the right way

- Producing executable code

Page 54: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Some AMENDMENTS to Scrum in order to be IMPACT DRIVEN

• The Product Owner has clear priorities, based on expected user and business impact

• UX Lead answers to all User Interface design related questions and is always available for the team

• The Backlog is a transition of the Impact Map

Page 55: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

Some AMENDMENTS to Scrum in order to be IMPACT DRIVEN

• Backlog Refinement sessions are planned for by UX Lead, unclear issues are resolved as early as possible

• User Stories (with user interaction) contain design and UX acceptance criterias

• Definition of Done contains UX validation

• Deliveries are tested with users

Page 57: Impact-driven Scrum Delivery at Scrum gathering Phoenix 2015

THANK YOU!

inuseexperience.com

@HeedTheNeed @ingriddomingues

@inuse_swe