lego4scrum
- About Scrum
Whys of Scrum 20 min.
Scrum framework 10 min.
Large Scaled Scrum frameworks 20 min.
LeSS principles and some details
Complecity thinking
Whys of roles
Cerimonies
Artifacts
Adaptive thinking
- Forming the teams and selecting roles
Teams selecting Scrum Masters few min.
Make a list of the key responsabilities
- Product vision
Start-up incubator for passionate geeks aka Silicon Village 10 min.
Several weeks
Warm season
Each team like living independently
Common areas to socialize
Stay to produce their early working products
Need full speed working infrastructure
Investors come over weekly for a big product review
Personas
Inventors
Investors
Geeks
Founders
Creators
Rich and busy people
Staff employees
Helicopters
Short periods
Serve the city
Creating shared understanding
User Story Mapping
Identify users # 5/7 min.
Mapping user tasks and user journeys 15 min. 
Prioritize on personas
Imagine a day in life from the arrival of an inventors
PO polls and write verbs from the class
PO challenges the assumptions about the users
Team of 4-6 people
Self selection by the team
Ideating backlog items 7 min.
Diverging
Come up with a list of features
Delegated to the participants
Converging (unrefined backlog)
Maximize outcome, minimize output
Define 3 releases putting 3 lanes on the map
R1: MVP
R2: Higher quality of service
R3: Scaling up
Backlog refinement
PO provides a brief of the essential details 5 min.
Fast-and-dirty joint estimation round
Detailed refinement of individual backlog items 15-20 min.
Wishes and constraints
Magical estimates
Triangulation board (Fibonacci up to 20 or t-shirt sizes)
Agree on a sample estimate (e.g. simple to build but not trivial)
Assign 2 o 3 points to the sample
Silent sorting 2 min.
Poker Planning by each team pulling out stories
Prioritizing the backlog
Short break
PO takes a photo of the board
PO arranges backlog item based on his perception of business priorities
Discussion with the teams
- Building the product
Multi-team joint sprint planning 3 min.
Landscape-specific first (help to understand the plan of the city)
ASAP How to build properly simple elements
Build more complex stuff
Additional things (shop, dining hall, etc.)
Each team pulls items from a shared Product Backlog into his Sprint Backlog
Scrum Masters don't plan!
2-3 representatives from each team move the cards and build the plans
Forecasting vs. Commitment
Commitment is internal: team members - to each other
Forecasting is external: teams - to the world
Confidence voting
Scrum Masters here are good helpers
Fist-of-five
Eventually re-planning of the Sprint Backlog
Building an increment
Short Sprints of 7-8 minutes to maximize fostering and learning
Reviewing an increment
Where is my city?!?
Deployment and integration
Deployment environment emerges
Late integration comes with a price
Inspect and adapt (not inspect and accept)
PO increases the level of collaboration asking questions
Add concrete todo's into the backlog
Retrospecting the process
Overall retrospective 5 min.
Team's retrospectives
Scrum Master facilitates the team's retrospective
Standing rather then sitting
Visualize progress
Fixed scope
Fixed time
How many more sprints we need to deliver given feature set
How many PBI are we forecasting to be done by this time (e.g. 3 sprints)
Few minutes for a quick internal team's retrospective
Burn-down chart with the help of Scrum Masters
Optimizing the whole avoiding local optimizations
Poll the teams to share key learnings
Raise the level of discussion to focus on the overall organization
Planning next sprint #
- Debrief
Discussions from product to process
Draw an overall simulation timeline
What helped us in the end despite all the unknowns and limiting constraints build this great product?
Which process elements were the most valuable?
Which were the least?
If we were to run this simulation again from scratch, what would you differently and why?