Topic Title: How can we help Stakeholders change Goals and Product Initiatives to be more successful?
Participants: Erik Tandberg, ~10 USF People (go Bulls), ~other people (go team)
- Bi-weekly check in meeting in addition to review
- Esentially a planning session
- Stakeholder views board and makes priority decisions
- Use lots of graphs, data, heatmaps
- Try to stay high level
- Never promise something
- "This is something I have to take back to the team"
- "I am not a developer"
- The reality is that some things MUST be delivered by a deadline
- Stakeholder: "It has to be perfect!!!!"
- Get sign off on Definition of Done and Acceptance Criteria
- Escalate to executives if necessary
- Show the stakeholders the impact of the delays they are creating, use $$$$$ values
- Instead of showing features, show the impact of features
- How many people does this affect?
- How much time is saved?
- How much $$$?
- "How do you stay connected with stakeholders and users?"
- Bring a lower level, "boots on the ground" end user
- In fact, have the PO shadow those people!!
- How does a QA Dept fit in with an Agile team?
- "We don't have a QA Dept" :(
- Make the QA testers attend the review meetings. Succeed or fail together!
- The Pizza Game (look it up and try it!)
- "New stakeholder, what do I tell them? How to onboard?"
- YouTube "Building the Bradley". Great tool, really teaches people about scope creep
- Judgement Juggler Game
- Understand the cost of context switching, bad requirements
- Do Empathy Mapping