Dimitris Dimitrelos Agile Coach
Working with Stakeholders
All photos by Christos Georgalas (christosg.org)
S/W projects fail…
44%
24%
32%
S/W Project Success
ChallengedFailedSuccessful
Source: CHAOS MANIFESTO 2013, The Standish Group
…miserably
30%
50%
20%
% Features Used
InfrequentlyHardly ever/neverOften
Source: CHAOS MANIFESTO 2013, The Standish Group
Waterfall: Build the product right?
Early decisions hurt!
Time
Knowledge
Decisions
Waterfall vs. Agile
Waterfall vs. Agile (2)
The Scrum Framework
The Rules
• Features are captured as items in a list of “product backlog”.
• Product progresses in a series of 1-4 week cycles called “sprints”.
• The business sets the priorities. Teams self-organize.
• Every one week to a month anyone can see real working software.
Scrum Roles
Product Owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product (ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or reject work results
Scrum Master
• Responsible for enacting Scrum values
and practices
• Remove impediments
• Ensure that the team is fully functional
and productive
• Enable close cooperation across all roles
and functions
• Shield the team from external
interferences
Development team
• 3-9 members
• Cross functional
• Self organized / self managed
• Decide how / how many
• Commit / Deliver
Agile coach
• Not a consultant
• Propose best practices
• Train, guide, mentor
The Product Owner as a HERO
BusinessTechnical
CEO
TestersVision
Detail
Product Backlog
Ass’s
Req’sLim’s
The Product Owner as a FUNNEL
Who is the stakeholder?
Stakeholders are…
“Stakeholder: An individual, group or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity or outcome of the project”PMBOK, 5th Edition
“Stakeholders are the reason we develop Products in the first place. ”3Back Team
SupportOperationsLegal / RegulatorySecuritySuppliersCompetitorsFamilySociety
Stakeholders are…
• Sponsors• Customers• Users• Developers• Testers• Managers• Marketers• Salespeople
Factor Traditional Agile
Communicate at Project Start Throughout project
Medium Formal (written) Informal (oral)Formal (written)Team (co-work)
Interaction Defensive Inclusive
Acceptance Sign-off Buy-in
Feedback Progress Reports Sprint ReviewTransparency
Agile vs. traditional
Power & Interest Levels
2-21
1. Monitor2. Keep Informed3. Keep Satisfied4. Manage Closely
Engage
• Release Planning• Formal set of Req’s / Reg’s• Sprint Reviews• Sprint Retro’s• One on one’s• E-mails
Enact
• User Stories• Non-functional Req’s• Definition of Done• Direct involvement in team• Updates / Progress Reports
Manage their Expectations
Protect their rightsRight to KNOWRight to CARE
Protect your stakeholders
Thank you
All photos by Christos Georgalas (christosg.org)