Tags:
Change the format, regularly. Avoid status updates--use a story wall or a big visible version of your electronic tracking system (projected on the wall, or on a large monitor) to communicate status instead. Then focus on what decisions need to be made as a group.
Change the questions--try one of the following:
There's a lot more... what do you think of these ideas so far?
I really like the idea of changing the questions to keep people thinking.
The status updates thing does seem to happen organically. While a status on what they did is important, I am more interested in are they on target and what help they need from the team.
Keep the ideas coming. Thanks
Ravi and I have a few slides on this topic that we could use for the "Intro to Agile" section of the upcoming event--Wed the 14th at Devry--are you going to be there?
Just as a teaser, our slides point out how a stand-up needs to be about connection--once people's attention starts to wander, there's a problem. We also have worked with teams that use multiple stand-ups a day, since they can be great at reminding us to stop & look around at the team as well as the big picture.
And Martin Fowler posted this about Stand-ups just last month
http://martinfowler.com/articles/itsNotJustStandingUp.html
I like the idea of the Improvement Board, but I could see where that would be a Futures-Wishlist is not policed and acted upon.
At AgilePhilly, we have been Promoting Agile Ideas since 1776
AgilePhilly is a not-for-profit user group of volunteers in the Philadelphia area dedicated to better software development practices.
Meetings are monthly. Get meeting reminders by joining here.
Our attempt with the group is to provide an environment where you can exchange ideas and meet with individuals involved in agile community.
© 2024 Created by Ravindar Gujral. Powered by