As we work toward in enhancing our agile practices, we(the team) took it upon ourselves to enhance the way we handle our stand ups. However this practice may not work for all teams, but as a team of larger size who works a lot in pairs and feature sets we thought these following things would be beneficial to the team organizing there day efficiently. 

  1. New & Improved Daily Stand Up Routine
    1. Impediments that stand in the way of moving forward addressed first
    2. Story Work
      1. New or Changed Stories
        1. Meeting with Product Owner, Development, QA for new stories should be identified and take place (New Stories only)
        2. Identify Story that Pair Programming Team is going to work on, and how they are going to begin
        3. Identify the tester who is going to be building the test with requirements
      2. In Progress Story
        1. Identify the Pair Programming Team
        2. Identify the tester who is going to be building the test with requirements, or running the tests
        3. Any Impediments related to story
    3. Stories that are completed from day before.(Finished)
      1. Is it ready for PO to review the story/close
        1. Deployed in an Integrated/Customer Level Environment
        2. All Tests Pass
    4. What was accomplished outside of Stories(and does it need a story)
      1. Escalations
      2. Large Meetings, Discussions, etc
    5. Product Owner Update
      1. Change of Directions, Escalations coming our way, etc

4 thoughts on “Stand-ups

  1. Does this meeting fit into 15 minutes?

    I support adjusting the scrum/standup agenda once a team is maturing, but this list seems like it is turning into a long meeting. I would be concerned that people find it too long and start to check out.

    If you can get this format to fit in 15-20 minutes, I like it. I especially like that the PO goes last. They have a voice, but they are secondary to the team!

    If you are interested in my team’s tweaks, check it out here:

  2. Chris says:

    We actually keep this into 15-20 minutes, because as part of our stories we have a pre-story gathering. So the stand up is to identify the pairs that will be undertaking that story and any impediments they have for starting/completeing that story. It moves quickly as we only identify the stories that are inprogress on our Story Board, after that and there is still developer/testers available we then move to the top “approved” story to be worked on and then acknowledge it, and move on.

  3. Lisa Crispin says:

    I like how you cover all these different areas in a shot time. Do you go around the room so each team member speaks, or do you just raise each topic and only people with something relevant speak up?

  4. Chris says:

    I think the layout was the “written down” approach to it, to give us an idea on how we should structure it. We still actually go person to person, but what we like to do for each person is identify stories that are done(worked on yesterday and completed), still in progress, or about to start, and then identify what we need then if it is a new story or inprogress to meet our goals.

    I think this may of been more clear, if i did a sort of logic path diagram, and showed how we started with each person and depending on their responses, we would then go into further inquiry. However we try to make sure everyone speaks and all stories that are approved/inprogress/in build are accounted for(if not yet covered).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: