Collaborating                               with                          StakeholdersTuesday, November 1, 11
•      Stuart Turner                   •      Originally from England                   •      Lives in Singapore         ...
Why not just consider the                         Customer?Tuesday, November 1, 11
What is a stakeholder?                   A person, group, organization or system                    which affects or can b...
Why do we need                           Collaboration?Tuesday, November 1, 11
• Most modern software is complex                    • Numerous and varied skill sets are required                    • A ...
But we’re agile!                    • Yes, it helps to remove BDUF                    • Yes, it brings people to work as t...
“There is nothing so useless            as doing efficiently that which              should not be done at all.”           ...
64          %                              of software                          features are rarely                       ...
Why do we build things                 we don’t really need?Tuesday, November 1, 11
Confirmation BiasTuesday, November 1, 11
Tuesday, November 1, 11
• PO, customer, users just want what                          someone else has                    • Ticks more boxes      ...
Implementation team(s)                  are too far removed                    • Large organization                    • D...
Language                    • Ambiguous                    • Insufficient or incapable                    • Lengthy        ...
User Stories                    • User story for a user                    • User story for a product owner               ...
We introduce                               complications                    • We want to use a tool                    • W...
It’s not technology...                    • Software is complex but not complicated                    • The technical pro...
• Most problems are caused by...Tuesday, November 1, 11
MiscommunicationTuesday, November 1, 11
Tuesday, November 1, 11
Tuesday, November 1, 11
The unknown is                                unknown                    • Each individual has their own view             ...
Solutions are often                 conceived before we’ve                    understood the                        proble...
Established Application                    • Developed over the past ten years by an                          average of 1...
Collaboration helps to                  expand our knowledge and                        understandingTuesday, November 1, 11
How do we collaborate                  more effectively?Tuesday, November 1, 11
Tuesday, November 1, 11
• Go and see                    • More direct feedback                    • Simple interaction                    • Knowin...
It’s complexTuesday, November 1, 11
CollaborationTuesday, November 1, 11
Collaboration                    • Bring together all stakeholders                    • Share the vision and goalTuesday, ...
Shared Mental ModelsTuesday, November 1, 11
Establish a shared                          understanding of the                               problemTuesday, November 1,...
The problem isn’t the                           problem!Tuesday, November 1, 11
Overcoming the                           problem is the                             problem!Tuesday, November 1, 11
With direct feedback                   from all stakeholders                  you realize you’re not                  deli...
You’re providing an                              ExperienceTuesday, November 1, 11
Experiences                    • Usage of delivered software                    • Engagement and interaction              ...
“We act as though comfort                  and luxury were the chief                     requirements of life.            ...
You’re able to delight                           your stakeholdersTuesday, November 1, 11
Tuesday, November 1, 11
How do we                          achieve this?Tuesday, November 1, 11
Large brained animals                    perform better when                 they’re enjoying themselves                  ...
Tuesday, November 1, 11
Bring people togetherTuesday, November 1, 11
Tuesday, November 1, 11
Tuesday, November 1, 11
Tuesday, November 1, 11
Overcoming the                             problem                    • Games and role playing really help                ...
Capture the                          important details                    • Use drawings and physical models              ...
I’m always doing things I                                   can’t do.                            That’s how I get to do   ...
Future Experiences                    • How are you going to delight your                          stakeholders?          ...
Upcoming SlideShare
Loading in …5
×

Collaborating with Stakeholders

1,231 views

Published on

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

Published in: Education, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,231
On SlideShare
0
From Embeds
0
Number of Embeds
283
Actions
Shares
0
Downloads
23
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Collaborating with Stakeholders

  1. 1. Collaborating with StakeholdersTuesday, November 1, 11
  2. 2. • 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 RiskTuesday, November 1, 11
  3. 3. Why not just consider the Customer?Tuesday, November 1, 11
  4. 4. What is a stakeholder? A person, group, organization or system which affects or can be affected by an organizations actionsTuesday, November 1, 11
  5. 5. Why do we need Collaboration?Tuesday, November 1, 11
  6. 6. • Most modern software is complex • Numerous and varied skill sets are required • A team is the basic unit necessaryTuesday, November 1, 11
  7. 7. 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 thingsTuesday, November 1, 11
  8. 8. “There is nothing so useless as doing efficiently that which should not be done at all.” Peter DruckerTuesday, November 1, 11
  9. 9. 64 % of software features are rarely or never used!Tuesday, November 1, 11
  10. 10. Why do we build things we don’t really need?Tuesday, November 1, 11
  11. 11. Confirmation BiasTuesday, November 1, 11
  12. 12. Tuesday, November 1, 11
  13. 13. • 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 projectTuesday, November 1, 11
  14. 14. Implementation team(s) are too far removed • Large organization • Departmentalized specialization • Local optimization • ‘Broken telephone’ • Jerry MaguireTuesday, November 1, 11
  15. 15. Language • Ambiguous • Insufficient or incapable • Lengthy • UnsuitableTuesday, November 1, 11
  16. 16. 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 KaczorTuesday, November 1, 11
  17. 17. We introduce complications • We want to use a tool • We are able to work remotely • Just because we can doesn’t mean we shouldTuesday, November 1, 11
  18. 18. It’s not technology... • Software is complex but not complicated • The technical problems have almost certainly been solved beforeTuesday, November 1, 11
  19. 19. • Most problems are caused by...Tuesday, November 1, 11
  20. 20. MiscommunicationTuesday, November 1, 11
  21. 21. Tuesday, November 1, 11
  22. 22. Tuesday, November 1, 11
  23. 23. 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 possibleTuesday, November 1, 11
  24. 24. Solutions are often conceived before we’ve understood the problem!Tuesday, November 1, 11
  25. 25. 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
  26. 26. Collaboration helps to expand our knowledge and understandingTuesday, November 1, 11
  27. 27. How do we collaborate more effectively?Tuesday, November 1, 11
  28. 28. Tuesday, November 1, 11
  29. 29. • Go and see • More direct feedback • Simple interaction • Knowing what your work means to the customerTuesday, November 1, 11
  30. 30. It’s complexTuesday, November 1, 11
  31. 31. CollaborationTuesday, November 1, 11
  32. 32. Collaboration • Bring together all stakeholders • Share the vision and goalTuesday, November 1, 11
  33. 33. Shared Mental ModelsTuesday, November 1, 11
  34. 34. Establish a shared understanding of the problemTuesday, November 1, 11
  35. 35. The problem isn’t the problem!Tuesday, November 1, 11
  36. 36. Overcoming the problem is the problem!Tuesday, November 1, 11
  37. 37. With direct feedback from all stakeholders you realize you’re not delivering a product or a serviceTuesday, November 1, 11
  38. 38. You’re providing an ExperienceTuesday, November 1, 11
  39. 39. Experiences • Usage of delivered software • Engagement and interaction • Empathy and understanding • EnthusiasmTuesday, November 1, 11
  40. 40. “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 EinsteinTuesday, November 1, 11
  41. 41. You’re able to delight your stakeholdersTuesday, November 1, 11
  42. 42. Tuesday, November 1, 11
  43. 43. How do we achieve this?Tuesday, November 1, 11
  44. 44. Large brained animals perform better when they’re enjoying themselves Nancy FrishbergTuesday, November 1, 11
  45. 45. Tuesday, November 1, 11
  46. 46. Bring people togetherTuesday, November 1, 11
  47. 47. Tuesday, November 1, 11
  48. 48. Tuesday, November 1, 11
  49. 49. Tuesday, November 1, 11
  50. 50. Overcoming the problem • Games and role playing really help • Use physical and interactive media • Act out different scenarios • Prototype solutions • Gauge stakeholder feedbackTuesday, November 1, 11
  51. 51. Capture the important details • Use drawings and physical models • Stakeholder value and acceptance criteria • Automated acceptance testsTuesday, November 1, 11
  52. 52. I’m always doing things I can’t do. That’s how I get to do them. Pablo PicassoTuesday, November 1, 11
  53. 53. 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

×