Difference between revisions of "Scrum"
m (typo.) |
(Restructured; added Michael Sahota's Agile Culture) |
||
| Line 1: | Line 1: | ||
Martien van Steenbergen primarily uses these sources | ==Martien's Sources== | ||
Martien van Steenbergen primarily uses these sources. | |||
===Slide Decks=== | |||
*[http://visionier.nl/xebia-scrum-master-and-product-owner.pdf Xebia » Martien van Steenbergen's slide deck on Agile, Scrum and Kanban] | *[http://visionier.nl/xebia-scrum-master-and-product-owner.pdf Xebia » Martien van Steenbergen's slide deck on Agile, Scrum and Kanban] | ||
*[http://visionier.nl/xebia-pof-scenarios-and-user-stories.pdf Xebia » Martien van Steenbergen's slide deck on Deriving User Stories from Scenarios]; focusing on the needs of the user roles: | *[http://visionier.nl/xebia-pof-scenarios-and-user-stories.pdf Xebia » Martien van Steenbergen's slide deck on Deriving User Stories from Scenarios]; focusing on the needs of the user roles: | ||
| Line 7: | Line 9: | ||
**relates to activities on the work floorl | **relates to activities on the work floorl | ||
**prevents gold plating; | **prevents gold plating; | ||
===Articles=== | |||
Some of these articles contain Martien's highlights. | |||
*[http://leanandkanban.files.wordpress.com/2009/04/kanban-for-software-engineering-apr-242.pdf David Joyce » Kanban for Software Engineering] | *[http://leanandkanban.files.wordpress.com/2009/04/kanban-for-software-engineering-apr-242.pdf David Joyce » Kanban for Software Engineering] | ||
*[http://pearllanguage.org/images/1/10/Priming-kanban.pdf Jesper Boeg | *[http://pearllanguage.org/images/1/10/Priming-kanban.pdf Jesper Boeg » Priming Kanban] with Martien's highlights. | ||
*[http://pearllanguage.org/images/4/45/Babushka_of_Value.pdf Babushka of Value (PDF)] | *[http://pearllanguage.org/images/4/45/Babushka_of_Value.pdf Martien van Steenbergen » Babushka of Value (PDF)]—a starting point for Kanban policies (admission criteria) on columns, and include {{p|ready to build}} and {{p|ready to ship}} (a.k.a. DoR and DoD). | ||
*[http://pearllanguage.org/images/4/4f/Agile_Transition_Survival_Guide.pdf Michael Sahota » An Agile Adoption and Transformation Survival Guide: Working with Organizational Culture] with Martien's highlights. | |||
==Most Relevant Scrum Pearls== | |||
*{{p|product owner}} | |||
*{{p|scrum master}} | |||
*{{p|babushka of value}} | |||
*Sources on [http://pareltaal.nl Pareltaal.nl]: | *Sources on [http://pareltaal.nl Pareltaal.nl]: | ||
Revision as of 11:52, 27 August 2012
Martien's Sources
Martien van Steenbergen primarily uses these sources.
Slide Decks
- Xebia » Martien van Steenbergen's slide deck on Agile, Scrum and Kanban
- Xebia » Martien van Steenbergen's slide deck on Deriving User Stories from Scenarios; focusing on the needs of the user roles:
- leads to product earlier;
- makes everything more practical, usable;
- limits you te create what is needed, not per sé what is possible;
- relates to activities on the work floorl
- prevents gold plating;
Articles
Some of these articles contain Martien's highlights.
- David Joyce » Kanban for Software Engineering
- Jesper Boeg » Priming Kanban with Martien's highlights.
- Martien van Steenbergen » Babushka of Value (PDF)—a starting point for Kanban policies (admission criteria) on columns, and include ready to build and ready to ship (a.k.a. DoR and DoD).
- Michael Sahota » An Agile Adoption and Transformation Survival Guide: Working with Organizational Culture with Martien's highlights.
Most Relevant Scrum Pearls
- Sources on Pareltaal.nl:
- Pareltaal » Seizoenslag is a starting point for creating organizational rhythm over multiple teams and releases.
- Pareltaal » Dienstklassen
- Pareltaal » Verhalenhakker
Right now, the first pearls on agile and scrum are emerging…
Accelerator list
Agile architect
Agile team dōjō
Ambiguity test
Ask for the moon
Babushka of value
Beauty of constraints
Belief statement
Blocker waiting room
Consent
Cruise missile
Customer segment pivot
Daily scrum of scrums
Daily standup
Decouple stages
Definition of done
Don’t just do something, stand there!
Five whys
Focus on focus off
Foreign glimpses
Goldilocks sizer
Habit of changing habits
Improvement board
Innovation accounting
Just say no
Ka-ching a day makes product owner hurray
Kanban
Knowledge injection
Lazy finish
Learning milestone
Minimal viable product
Obeya
One service deserves another
One team
Open space
Pair working
Physical information radiators
Pivot
Product backlog
Product owner
Product portfolio
Product review meeting
Product vision
Product vision board
Ready to build
Reciprocal altruism
Refactor code
Relative estimation
Release burndown chart
Ritual dissent and assent... further results