Scrum Master Asking good questions: http://libizblog.files.wordpress.com/2007/10/question-mark.jpg
Don't go in same order each time : http://www.cs.jhu.edu/~pari/600.107/Horstmann/slides/Ch19/images/queue.png
PO goes last with updates
Have the team pick the time: http://www.infowit.com/images/time_graphic.jpg
Use humor: http://images.buycostumes.com/mgen/merchandiser/19788.jpg
Declare and End: http://kashifalvi.files.wordpress.com/2007/09/the-end.jpg
Take action afterward
Developers talk to eachother
Chickens are optional
Proper equipment for offsite folks, e.g. conference lines that work
Report to Leader
Only Discussion at Standup
Too Early, Too Big, ShoeGazers
Standup Used as a design session, Sitting Down
Standup as a separate room from the team room, Electronics being used
Standup Starts the Day, No impediments recorded, Ratholing
Use a token, somethign fluffy that you can throw to the next person when it is their turn Bring a different token each sprint Spin the Marker to decide who goes first Offer appreciations at the beginning of a meeting. <Name of Person>, I appreciate you for <this>. Celebrate progress (Woohoos!), burndowns, impediments removed, etc Offer Food, coffee: better if it is not routine but a special thing Random stuff is helpful (though switching the time of standup is generally not helpful, it's confusing) Ask "How are you feeling?" Tell a story, a personal anecdote to start the meeting When someone leaves for a few days and comes back, tell them to bring back a tacky toy Whoever speaks first says thank you after the meeting Welcome people to standup Use "speed dating method" for impediments. Ask who has an impediment and then who can help them Bring a joke to standup (look up on internet) Create a non-human enemy (Someone mentioned a vista machine that was the enemy on the project) Ask, "how are we doing this morning?"
How to run an effective (and fun) standup. Notes from session at Agile Open NW By Ed Kraay
Objective To communicate the learnings from an Agile Open NW Session to SIQ Goal: To learn to identify when your standup may become dull and pointless, and learn some ways to fix it if that happens.
SM Redirect decisions/approval back to the team
Pigs: Communicate lateness and report to the team, not to SM or PO
Don't say start, let the team say go: Spin the marker
Install a sense of team ownership. Do less for them. They will do more for themselves.
Reporting to Leader – How to fix.
People not prepared for Standup, how to fix Make a list of things you did the evening before. Bring in the morning Give some work time before the meeting to get in work mindset Look at commit logs, records of work as a refresher Minute timers: try to fill but not go over Frame your day in how it is relevant to the group Have a Splash Down: A second standup at end of the day or other time to review what we did Have progress charts/info visible during standup Don't tell the detail, pick up the highlights
Only discussion is at Daily Standup Status report takes away from the daily standup Use a parking lot Make sure folks follow up at the end of a meeting, not during the meeting Schedule a design discussion Have an all day chat with the team: why wait to report an impediment in 24 hours, why not bring them to up when they happen **Encourage a developer TODO list Have developers reference the story & the task End the scrum on a positive note
How to make a dull Standup Fun Now that you’ve figured out how to have an effective standup, how do you avoid a dull, repetitive, boring standup….
Spin the Marker Use a Token Bring a different token each sprint
Bring Appreciations. Team Member, I appreciate you for, X. Encourage Woohoo! Bring Food, Make it a surprise Last one to finish standup says “Thank you”
Do a dance if you’re late. Create a non-human enemy