Dimitris Dimitrelos gave a very insightful presentation about the "agile" side of working with stakeholders, in an attempt to discover the benefits and pitfalls.
9. 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.
10. 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
14. 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
16. 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 Review
Transparency
Agile vs. traditional