Skip to main content

WHY the same place and time for your daily stand-up?

"we're all here, let's just have stand-up now"
"so-and-so isn't coming today, so let's have stand-up now"
"hey, I'll just come over there and we'll do stand-up there"

It seems so easy and innocent to simply change the time and place of stand-ups, especially when key people such as the PO or Scrum master may not be attending the meeting for the day. The reasons I recommend for not changing are:


The need for good habits is possibly the most obvious reason for not changing the time and place of your daily stand-up. If the daily stand-up becomes a habit it will be ingrained into the psyche of your team and the operation of the stand-up becomes something that individual team members provide, rather than an action that is demanded of them. By making stand-up a habit, you have left them with extra creative juices to use in more mentally demanding tasks, like design or architecture.

There's a reason why Steve Jobs used to wear the same clothes everyday, it's because it was a habit he had developed. He did not need to use will power or creative juices to make a decision on what to wear, meaning he used these mental resources later on in the day for more important things.

Rings alarm bells for more ingrained problems

The daily stand-up should not be a status update for any particular individual, but this may become the case if its timing is continually changed due to an individual’s absence. Instead of a status update, the daily stand-up should be an opportunity for the team to re-gather and plan their day in order to achieve a previously committed goal.

Team building

There's a lot to say about a team who consistently – day in and day out – has a stand-up. If the habit of a daily stand-up develops within a team, it has done so because the team itself has found the stand-up rewarding. If the stand-up is rewarding, it means the team is delivering. In addition, a simple 'good morning', 'how are you?' or 'how was your weekend' from just one person in the team can strengthen an individual's morale who may be having a hard time at home, or that just has many things on his or her mind. An individual who knows that he or she  will be greeted politely at a set time, would probably sub-consciously be prepared for the kind words received at such a meeting.


Popular posts from this blog

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.

Have You Ever Produced Negative Value in a System!?

As developers we encourage our product owners to order the priority of their backlog in order of value. However, every time a new feature is implemented by a development team, there is a certain degree of risk associated with the introduction of that new code. Namely, risk of breaking another part of the product and maintenance cost. When a development team pulls in a new feature to implement there is a certain acceptance of this risk. In many cases, the risks that arise due to additional code complexity doesn't justify the value added by the new feature itself, so the development team can start implementing it.

Are there scenarios where the value added to a software product can be negative though?