InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Keep those Stand Up Meetings Short and Sweet

Posted by Deborah Hartmann Preuss on Jun 05, 2006

Sections
Process & Practices,
Development
Topics
Artifacts & Tools ,
Agile Techniques ,
Agile
Tags
Scrum ,
Facilitation
Keeping the daily Scrum, or standup meeting, short is a challenge for some teams. Conversations get out of hand and distract the team, or developers forget and go into too much detail. Any number of elements can derail a standup meeting, making it boring or too long.

Many of us are familiar with the "Talking Stick", a token some indigenous peoples use in meetings (and they have apparently been running well organized tribal meetings for many thousands of years).  It's an elegantly simple way to keep a group focused and respectful.  Kane Mar, a west coast XP coach has blogged about how several teams have adapted this idea.  The photos are great.

Now, a pig mascot as a "talking token" may be brilliant - or disrespectful, depending on how you feel about the oft used Scrum story of the Chicken and the Pig.

If you are intrigued, Jeff Sutherland has blogged on how the three questions of the daily Scrum improve effectiveness, and you can find out more about running a Scrum meeting on Simon Baker's blog, where he's also given links for further reading. It's a useful tool for any Agile team, even if team members are not all on-site - distributed teams can use a conference phone - though the visuals get lost if the team uses a physical task board.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.