Daily stand-up with a goal

Why your daily standup should be driven by a daily goal

Let’s face it, the daily standup can be a boring affair. I’m not talking about abominations with 16 people or half-hour long status reporting meetings. I’m talking about the ones that are kind of okay and adhere to the rules but nonetheless are a bit boring and lack focus and enthusiasm.
 

To me the point of the daily standup is not to rattle off what you did yesterday, what you’re planning to do today and if you have any blockers. The point is to decide, as a team, what each of you can do to make this an awesome and productive day that helps you get closer to building something great.
 
I’d like to share a technique that I have used during the past year to help teams increase focus and clarity of purpose during the day: The daily goal.
 
What is the daily goal?

Surprisingly enough, the daily goal is a goal the team aims to achieve by the end of the day.

I usually introduce it as the part of Agile that I have made up and ask people during the daily standup to define a goal that would make them go home at the end of the day thinking they have had a productive and meaningful day. I ask people to imagine that it is the end of the day and what, as a team, would have made them happy to have achieved.

 

Daily goals

 

Examples of daily goals are:

  • Finish user story 3
  • Get story 1 into test
  • Automate testing for story 5
  • Know how to deploy the migration
  • Design concepts for search agreed
  • Smash story 1 and 2
  • Ship to Apple

 
Goals that involve everyone’s work are by far the best but unfortunately that’s not always possible. If we can’t define a goal where everyone is hands-on involved we are pragmatic about it and just pick the most important thing for the day.

 

How does it work?

We usually define the daily goal either at the beginning or at the end of the daily standup; depending on mood and team preference. We always make sure that the goal is aspirational and not just a list of individual tasks, and that we can determine at the end of the day whether or not we have achieved it.
 
When we find it hard to come up with a goal for the day usually the question “At the end of the day when you go home – what would make you happy?” works really well.
 
By its very nature the daily goal is the most important thing for the day. Therefore most teams have a ground rule that it trumps everything else during the day and everyone working on a task that directly supports the daily goal has the power to interrupt other people’s work and to divert their efforts towards achieving the daily goal.
 
Why does it work?

For people to work as a team and to truly collaborate they need to have clarity of purpose and a shared, compelling goal. I often find that visions for teams, products, waves, and, if you’re running SCRUM, sprints – while working really well – can sometimes seem far in the future.
 
Adding a short-term goal for the day adds this clarity of purpose to everything we do on a daily basis. Shared goals work well and shared daily goals work well, too.
 
Also, as a coach I find the focus, clarity and purpose that agreeing on a daily goal generates extremely helpful when working on building Agile teams as it helps people practice collaborating towards a shared goal more often and to gather feedback on team collaboration more frequently.

 

What do we do with past daily goals?

We usually put the day’s goal in a special place on our task boards as a reminder during the day.

We start our standups by assessing whether we have achieved yesterday’s goal and put a visible check or cross on the sticky note before placing it on the past timeline.
 

Achieved the goal

 

What next?

The daily goal has worked really well for me for more than a year and has been taken up by the 10 teams I have coached during that time.
 
I recommend trying it out and would love to hear what you think and how it works for you. I might be stating the obvious but it’s of course irrelevant whether you’re running SCRUM, Kanban or Borkiborki; the point is that small daily goals for a team are good for your focus and team spirit.
 
Last but not least, don’t give up if it doesn’t work right away – some of my teams abolished and then re-introduced it when they had got the hang of working towards a shared goal.

 

 

Sandy Mamoli
5 Comments
  • Manish
    Reply

    Excellent article Sandy. We have been following a similar approach with our teams. I would like to add that DEFINING GOALS is also a challenge. A goal has to be definite, concise and most importantly PRACTICAL..! Understanding whether we are Aiming too high or too low is what people understand with experience..!

    September 24, 2013 at 1:10 am
    • smamol
      Reply

      That is very true; good point! I agree, it takes some experience to aim right and create practical goals.

      September 24, 2013 at 10:14 am
  • Russell Pannone
    Reply

    Your approach takes the focus off the bigger picture of what the team committed to do during sprint planning to deliver this increment of the product and how they are tracking based on what is actually getting done and planning on doing.

    September 27, 2013 at 5:21 am
  • UDAY
    Reply

    Excellent Article to focus on the Productivity on a day to day basis achieving goals to reach the set milestone.

    January 18, 2016 at 7:44 pm
  • Anybody with a complex project can benefit from using Scrum. It prioritizes a large to-do list into a manageable task with an improved framework, better communication and a faster result. Scrum has a streamlined software development – and professionals from all over the world are starting to see the value of using Scrum. It is the most popular Agile framework being used worldwide. In fact, 66% of companies are using Scum or a Scrum variant.
    Please visit http://www.scrumboards.com
    Linkedin Page:https://www.linkedin.com/company/scrumboards-com?trk=top_nav_home

    May 3, 2016 at 12:23 am

Post a Comment