View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
Definition• What ? – 15 minute time-boxed meeting• Who? – People transforming the product backlog items into an increment• Why? – Used to create a plan for next 24 hours• How? – Inspecting – Forecasting
Mechanics• Same place• Same time• Explain: – What has been accomplished since the last meeting? – What will be done before the next meeting? – What obstacles are in the way?
Goals• Assess progress toward the Sprint goal• Assess how progress is trending toward completing the work in the Sprint Backlog• Re-plan to accomplish the goal and create the anticipated increment
Benefits• Improve communications• Identify and remove impediments• Highlight and promote quick decision-making• Improve project knowledge• Optimize the probability of meeting the Sprint goal
Misunderstanding• Not a status meeting• Not for the Scrum Master• Not for the Product Owner• Not for updating project management artifacts
Manifesto for Agile Software Development• People and interactions over processes and tools• Working software over comprehensive documentation• Customer collaboration over contract negotiation• Responding to change over following a plan
Principles Behind the Agile Manifesto• Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage• Business people and developers must work together daily throughout the project• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
Principles Behind the Agile Manifesto• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation• The best architectures, requirements, and designs emerge from self-organizing teams
Tips• Start on time• Apply fines or peer pressure• Attend by proxy• Follow the 3 questions format• Create a parking lot• Use a time-box• Tactfully interrupt• Speak-up• Come prepared
Tips• Use an index card• Updates by others• Round robin, pass the token, or by story• Highlight blockers• Pay attention to “no blockers”• Break eye contact• Have a standup champion• Keep communicating
References• The Scrum Guidehttp://scrum.org• The fishbowlhttp://fishbowl.pastiche.org/2003/11/19/standup_meeting_antipatterns/• Stand and deliver. Why I hate stand-up meetingshttp://queue.acm.org/detail.cfm?id=957730• Daily stand up withdrawal in scrumhttp://www.scrumalliance.org/articles/32-daily-standup-withdrawal-in-scrum-teams• It’s not just standing uphttp://martinfowler.com/articles/itsNotJustStandingUp.html
References• Daily stand-up beyond mechanics – a measure of self organizationhttp://agile.conscires.com/2010/12/01/daily-stand-up-beyond-mechanics-a-measure-of-self-organization/• The Art of Agile Development – Stand up meetingshttp://jamesshore.com/Agile-Book/stand_up_meetings.html• Getting started with agile – daily stand up meetinghttp://blogs.atlassian.com/developer/2009/06/getting_started_with_agile_daily_ standup_meetings.html• Why “No Issues” Is Not An Acceptable Answerhttp://lostechies.com/derickbailey/2009/03/24/why-no-issues-is-not-an- acceptable-answer/
References• Getting the most of your daily stand-up meetinghttp://www.xapware.com/post/Getting-the-most-from-your-daily-stand-up-meetings.aspx• Variations on the daily standhttp://agilecoach.typepad.com/agile-coaching/2005/01/variations-on-the-daily-stand-up.html• Tips for effective daily stand-up meetingshttp://blog.agilegamedevelopment.com/2010/11/effective-daily-stand-up-pointers.html• Scrum Butt – Daily Scrumhttp://blog.coryfoy.com/2009/09/scrumbut-part-3-daily-scrum/