• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Collaborating with Stakeholders
 

Collaborating with Stakeholders

on

  • 1,199 views

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

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

Statistics

Views

Total Views
1,199
Views on SlideShare
960
Embed Views
239

Actions

Likes
1
Downloads
18
Comments
0

3 Embeds 239

http://visibletrap.wordpress.com 122
http://visibletrap.posterous.com 108
http://posterous.com 9

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Collaborating with Stakeholders Collaborating with Stakeholders Presentation Transcript

    • Collaborating with StakeholdersTuesday, November 1, 11
    • • 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
    • Why not just consider the Customer?Tuesday, November 1, 11
    • What is a stakeholder? A person, group, organization or system which affects or can be affected by an organizations actionsTuesday, November 1, 11
    • Why do we need Collaboration?Tuesday, November 1, 11
    • • Most modern software is complex • Numerous and varied skill sets are required • A team is the basic unit necessaryTuesday, November 1, 11
    • 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
    • “There is nothing so useless as doing efficiently that which should not be done at all.” Peter DruckerTuesday, November 1, 11
    • 64 % of software features are rarely or never used!Tuesday, November 1, 11
    • 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 • Might be a language, framework, library or design patterns • New buzz words • The latest ‘cool’ technology • Your manager’s pet projectTuesday, November 1, 11
    • Implementation team(s) are too far removed • Large organization • Departmentalized specialization • Local optimization • ‘Broken telephone’ • Jerry MaguireTuesday, November 1, 11
    • Language • Ambiguous • Insufficient or incapable • Lengthy • UnsuitableTuesday, November 1, 11
    • 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
    • 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
    • It’s not technology... • Software is complex but not complicated • The technical problems have almost certainly been solved beforeTuesday, November 1, 11
    • • 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 • 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
    • Solutions are often conceived before we’ve understood the problem!Tuesday, November 1, 11
    • 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
    • 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 • Knowing what your work means to the customerTuesday, November 1, 11
    • It’s complexTuesday, November 1, 11
    • CollaborationTuesday, November 1, 11
    • Collaboration • Bring together all stakeholders • Share the vision and goalTuesday, November 1, 11
    • Shared Mental ModelsTuesday, November 1, 11
    • Establish a shared understanding of the problemTuesday, November 1, 11
    • 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 delivering a product or a serviceTuesday, November 1, 11
    • You’re providing an ExperienceTuesday, November 1, 11
    • Experiences • Usage of delivered software • Engagement and interaction • Empathy and understanding • EnthusiasmTuesday, November 1, 11
    • “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
    • 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 Nancy FrishbergTuesday, November 1, 11
    • 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 • Use physical and interactive media • Act out different scenarios • Prototype solutions • Gauge stakeholder feedbackTuesday, November 1, 11
    • Capture the important details • Use drawings and physical models • Stakeholder value and acceptance criteria • Automated acceptance testsTuesday, November 1, 11
    • I’m always doing things I can’t do. That’s how I get to do them. Pablo PicassoTuesday, November 1, 11
    • 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