A workshop for Product Owner and major leadership of a team. Typically predates a Scrum team immersion workshop by a few weeks.
4 - 12 contact hours, 1 Week before the Team Workshop
I find that one of the best ways to have a successful team is to have a successful product owner. This workshop is intended to help product owners create a starting point for their backlog; learn various approaches to slicing user stories and techniques for product backlog grooming. It will also introduce Product Owners to the concepts of Scrum and teach them how to manage product releases and scheduling using the empirical data gathered from the Scrum process.
Purpose: The purpose of this Workshop is to educate the Product Owner (one person) and prepare a product backlog for the scrum immersion workshop. Also included are the various consultants, SME, BA, developers, etc. in the backlog grooming process.
Expected Outcomes:
I find that one of the best ways to have a successful team is to have a successful product owner. This workshop is intended to help product owners create a starting point for their backlog; learn various approaches to slicing user stories and techniques for product backlog grooming. It will also introduce Product Owners to the concepts of Scrum and teach them how to manage product releases and scheduling using the empirical data gathered from the Scrum process.
Purpose: The purpose of this Workshop is to educate the Product Owner (one person) and prepare a product backlog for the scrum immersion workshop. Also included are the various consultants, SME, BA, developers, etc. in the backlog grooming process.
Expected Outcomes:
- Set realistic expectations for transition and next release
- Overview of Scrum & Product Owner role (and how the team supports this role)
- Set PO role responsibilities and expectations
- Alignment of Release goal (within the context of Project/Program & Scrum transition)
- Product Backlog ordered (prioritized) for the first 2 sprints
- Agreement to Scrum cadence for planning meetings and grooming backlog and sprint review meetings
Agenda:
Big Picture - Umbrella of Agile
- Agile - Lean - XP - Scrum - lightweight vs heavyweight processes
- The TEAM as a basic unit of 21st C. development - Team Performance Model
- Organization Cultural Differences (from individual contribution to teamwork)
- Visualizing work to be done and progress toward goals
- Economic models of interest
- Why are YOU doing this Agile transition?
High-Level Overview of Scrum Basics
- Basic of Scrum (history, principles, purpose)
- Basics of 3 roles
- Meetings (who, when, why, outcomes)
- Burndowns - visualizations
- Sprint Planning example
- Release Planning overview
- Indicators that the product is not meeting the PLAN
Work Products -- Workshop Artifacts -- Real Work
- Goal Setting - the purpose of the project (next release's goal - first few sprints goals)
- Project Sliders exercise (M. Cohn)
- Context Diagrams (various examples)
- Product Box exercise (Innovation Games)
- Establish the Backlog - (one list - ordered - understood by PO)
- Backlog Grooming (break epics up if ordered first, group stories if ordered last - themes/epics)
Techniques of managing Projects in Scrum -- Cookbook -- Examples & Exercises
- Prioritize the Backlog
- Ordering Techniques (20/20 Vision the Innovation Game)
- Story Writing (advanced technique Story Mapping)
- Story Slicing (the technique of decomposition and integration)
- Feedback Techniques
- Distributed teams & techniques for mitigation of non-colocated teams
- Continuous Improvement (Kaizen, A3 document, 5 whys, etc)
- Product Value Stream - Single piece flow
- Stakeholder Map - exercise
Comments