97. HANDS-ON
▸Write down 5 user stories and give each of them a business
value.
▸Please prioritize those user stories.
▸Write down how to confirm them.
107. HANDS-ON
▸Each sprint will be take 3 minutes.
▸Put user stories in the backlog for next sprint.
▸Convert each user story to tasks.
▸Estimate story points of each tasks.
113. SCRUM BOARD WITH BURNDOWN
CHART
http://old.xpday.net/Xpday2008/sessions/SCRUM%20Board%20Game.html
114. MISUNDERSTANDING OF STORY
POINTS
▸Equating Story Points To Complexity, Uncertainty or Value.
▸Translating Story Points To Hours.
▸Averaging Story Points.
▸Adjusting Story Point Estimates of Issues During Sprint.
▸Never Story Pointing Bugs.
▸Conforming To The Expert In The Room.
▸Not Discussing Incorrectly Story-Pointed Issues In Retrospective.Not
Discussing Incorrectly Story-Pointed Issues In Retrospective.
https://medium.com/bynder-tech/12-common-mistakes-made-when-using-story-points-f0bb9212d2f7
120. THE DAILY STAND-UPS
ARE MORE THAN JUST
ASKING WHAT YOU DID
AND IF YOU’RE BLOCKED.
IT’S ABOUT REACHING
THE SPRINT GOAL!
Patrick van Marsbergen
TEXT
121. HANDS ON
▸Let's develop (2 min)
▸Please hold a stand-up meeting in 30 seconds
▸Let's develop again (2 min)
▸Please hold a stand-up meeting in 30 seconds
136. SMALL TEAM, MULTIPLE PROJECTS: AN
AGILE APPROACH TO PLANNING
https://davidmarquis.wordpress.com/2011/12/03/small-team-multiple-projects-agile-planning/
140. FOCUS ON EACH PERSON
https://medium.com/@anttihavanko/how-to-handle-multiple-projects-with-a-small-team-ebdfde5f6714
141. FOCUS ON EACH PROJECT
https://medium.com/@anttihavanko/how-to-handle-multiple-projects-with-a-small-team-ebdfde5f6714
142. LET VALUE STREAMS SMALLER THEN
NUMBER OF MEMBERS
▸floor(team size / 2) + 1
▸ Team of 3: 2 value streams
▸ Team of 6: 4 value streams
▸ Team of 7: 4 value streams
159. ▸Visualizing the flow
▸Limiting the WIP (Work In Progress)
▸Measuring the Lead Time
▸Optimize iteratively with data
https://www.avantica.net/blog/2016/11/17/dont-stay-in-the-shu-box-agile-is-not-a-recipe-4