Difference between revisions of "Scrum"

From Pearl Language
Jump to navigation Jump to search
(Xebia » Martien van Steenbergen's slide deck on Deriving User Stories from Scenarios)
(Added Thieu van Loosdrecht's findings)
Line 1: Line 1:
Martien van Steenbergen primarily uses these sources:
Martien van Steenbergen primarily uses these sources:
*[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]  
*[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
**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;
*[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's Priming Kanban] with Martien's highlights.
*[http://pearllanguage.org/images/1/10/Priming-kanban.pdf Jesper Boeg's Priming Kanban] with Martien's highlights.

Revision as of 12:10, 2 July 2012

Martien van Steenbergen primarily uses these sources:

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