scrum

Motivation and origin

• change
• complexity
• empowerment

Jeff Sutherland Jeff McKenna

Ken Schwaber Mike Smith, Chris Martin

1995

a process framework

not a specific solution

iterative

incremental

founded on empiricism

transparency

inspection

adaption

every scrum event is an opportunity to inspect and adapt

the scrum team

self-organizing

cross-functional

Gamestorming roles and responsabilities

Roles and Responsabilities

• everyone contributes with post-its with responsabilities for each role, expept your own role
• put postits on role poster
• persons playing the role facilitates a discussion about their role
• the team should have a common understanding of the roles

Takeaways

• It's important to have clear and transparent roles and responsabilities
• A role is not a position
• Someone can play different roles at different time even without realising it
• You should return to this exercise from time to time

Gamestorming team agreements

Team agreements

• split in 6 small teams
• receive an item and paper: Daily, Retro, Review, Planning, Refinement, DOD
• write down answers to the questions: Why? and How?
• present your answers to the team
• vote happiness with fist of five
• discuss on how to improve the lowest rated

Takeaways

• Scrum process works for you not the other way around
• As a team, you are empowered to return to team agreements, adapt and change them
• You don't need to wait for the retrospective to do this
• Anyone can initiate change

the sprint

has a goal

creates a cadence

releasable product increment

scope can be clarified and re-negociated

the backlog

a living document

a priority

an estimate

a business value

past progress predicts future progress

empiricism

the future is unknown

user stories

• Independent
• Negotiable
• Verifiable
• Estimable
• Small
• Testable

Splitting User Stories

Spikes

• Drive out risk and uncertainty
• New domain
• Story too big
• Technical/functional risk
• Estimable
• Demonstrable
• Acceptable

Pitfalls of scrum

• No project design
• No sponsor support
• No training
• Not focused
• Excessive planning
• Tasks are assigned
• Directive approach
• Fixed time, resources, scope and quality

Learn more