Collaborating with Stakeholders

53
Collaborating with Stakeholders Tuesday, November 1, 11

description

How do we collaborate with stakeholders and why is it necessary for software development?

Transcript of Collaborating with Stakeholders

Page 1: Collaborating with Stakeholders

Collaboratingwith

Stakeholders

Tuesday, November 1, 11

Page 2: Collaborating with Stakeholders

• Stuart Turner

• Originally from England

• Lives in Singapore

• Works for Odd-e

• Agile coach, SW developer

• Experience with startups and Financial Institutions

• Java, Low-latency Trading Systems, Operational Risk

Tuesday, November 1, 11

Page 3: Collaborating with Stakeholders

Why not just consider the Customer?

Tuesday, November 1, 11

Page 4: Collaborating with Stakeholders

What is a stakeholder?

A person, group, organization or system which affects or can be affected by an

organization's actions

Tuesday, November 1, 11

Page 5: Collaborating with Stakeholders

Why do we need Collaboration?

Tuesday, November 1, 11

Page 6: Collaborating with Stakeholders

• Most modern software is complex

• Numerous and varied skill sets are required

• A team is the basic unit necessary

Tuesday, November 1, 11

Page 7: Collaborating with Stakeholders

But we’re agile!

• Yes, it helps to remove BDUF

• Yes, it brings people to work as teams

• Focuses on building things better, not necessarily building the right things

Tuesday, November 1, 11

Page 8: Collaborating with Stakeholders

“There is nothing so useless as doing efficiently that which

should not be done at all.”Peter Drucker

Tuesday, November 1, 11

Page 9: Collaborating with Stakeholders

64%of software

features are rarely or never used!

Tuesday, November 1, 11

Page 10: Collaborating with Stakeholders

Why do we build things we don’t really need?

Tuesday, November 1, 11

Page 11: Collaborating with Stakeholders

Confirmation Bias

Tuesday, November 1, 11

Page 12: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 13: Collaborating with Stakeholders

• PO, customer, users just want what someone else has

• Ticks more boxes

• Might be a language, framework, library or design patterns

• New buzz words

• The latest ‘cool’ technology

• Your manager’s pet project

Tuesday, November 1, 11

Page 14: Collaborating with Stakeholders

Implementation team(s) are too far removed

• Large organization

• Departmentalized specialization

• Local optimization

• ‘Broken telephone’

• Jerry Maguire

Tuesday, November 1, 11

Page 15: Collaborating with Stakeholders

Language

• Ambiguous

• Insufficient or incapable

• Lengthy

• Unsuitable

Tuesday, November 1, 11

Page 16: Collaborating with Stakeholders

User Stories

• User story for a user

• User story for a product owner

• User story for a developer

• No business value or benefit to the customer

• No acceptance criteria

Krystian Kaczor

Tuesday, November 1, 11

Page 17: Collaborating with Stakeholders

We introduce complications

• We want to use a tool

• We are able to work remotely

• Just because we can doesn’t mean we should

Tuesday, November 1, 11

Page 18: Collaborating with Stakeholders

It’s not technology...

• Software is complex but not complicated

• The technical problems have almost certainly been solved before

Tuesday, November 1, 11

Page 19: Collaborating with Stakeholders

• Most problems are caused by...

Tuesday, November 1, 11

Page 20: Collaborating with Stakeholders

Miscommunication

Tuesday, November 1, 11

Page 21: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 22: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 23: Collaborating with Stakeholders

The unknown is unknown

• Each individual has their own view

• We don’t know if our views are the same

• If often appears our views are the same

• Customers sometimes don’t know what they want

• They often don’t know what’s possible

Tuesday, November 1, 11

Page 24: Collaborating with Stakeholders

Solutions are often conceived before we’ve

understood the problem!

Tuesday, November 1, 11

Page 25: Collaborating with Stakeholders

Established Application

• Developed over the past ten years by an average of 100 developers

• How do you tell if features are no longer useful?

• Should you REMOVE some or all of those features?

Tuesday, November 1, 11

Page 26: Collaborating with Stakeholders

Collaboration helps to expand our knowledge and

understanding

Tuesday, November 1, 11

Page 27: Collaborating with Stakeholders

How do we collaborate more effectively?

Tuesday, November 1, 11

Page 28: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 29: Collaborating with Stakeholders

• Go and see

• More direct feedback

• Simple interaction

• Knowing what your work means to the customer

Tuesday, November 1, 11

Page 30: Collaborating with Stakeholders

It’s complex

Tuesday, November 1, 11

Page 31: Collaborating with Stakeholders

CollaborationTuesday, November 1, 11

Page 32: Collaborating with Stakeholders

Collaboration

• Bring together all stakeholders

• Share the vision and goal

Tuesday, November 1, 11

Page 33: Collaborating with Stakeholders

Shared Mental Models

Tuesday, November 1, 11

Page 34: Collaborating with Stakeholders

Establish a shared understanding of the

problem

Tuesday, November 1, 11

Page 35: Collaborating with Stakeholders

The problem isn’t the problem!

Tuesday, November 1, 11

Page 36: Collaborating with Stakeholders

Overcoming the problem is the

problem!

Tuesday, November 1, 11

Page 37: Collaborating with Stakeholders

With direct feedback from all stakeholders you realize you’re not delivering a product or

a service

Tuesday, November 1, 11

Page 38: Collaborating with Stakeholders

You’re providing an Experience

Tuesday, November 1, 11

Page 39: Collaborating with Stakeholders

Experiences

• Usage of delivered software

• Engagement and interaction

• Empathy and understanding

• Enthusiasm

Tuesday, November 1, 11

Page 40: Collaborating with Stakeholders

“We act as though comfort and luxury were the chief

requirements of life.All that we need to make us happy is something to be enthusiastic about.”

Albert Einstein

Tuesday, November 1, 11

Page 41: Collaborating with Stakeholders

You’re able to delight your stakeholders

Tuesday, November 1, 11

Page 42: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 43: Collaborating with Stakeholders

How do we achieve this?

Tuesday, November 1, 11

Page 44: Collaborating with Stakeholders

Large brained animals perform better when

they’re enjoying themselvesNancy Frishberg

Tuesday, November 1, 11

Page 45: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 46: Collaborating with Stakeholders

Bring people together

Tuesday, November 1, 11

Page 47: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 48: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 49: Collaborating with Stakeholders

Tuesday, November 1, 11

Page 50: Collaborating with Stakeholders

Overcoming the problem

• Games and role playing really help

• Use physical and interactive media

• Act out different scenarios

• Prototype solutions

• Gauge stakeholder feedback

Tuesday, November 1, 11

Page 51: Collaborating with Stakeholders

Capture the important details

• Use drawings and physical models

• Stakeholder value and acceptance criteria

• Automated acceptance tests

Tuesday, November 1, 11

Page 52: Collaborating with Stakeholders

I’m always doing things I can’t do.

That’s how I get to do them.

Pablo Picasso

Tuesday, November 1, 11

Page 53: Collaborating with Stakeholders

Future Experiences

• How are you going to delight your stakeholders?

• How are you going to improve your own working experience?

• One small thing...

Tuesday, November 1, 11