Daily StandUp in a small co-located team
Let's suppose we have a small development team: a front-end developer, a back-end developer and a tester working in the same room and therefore able to communicate freely throught a day.
Is it reasonable to have daily StandUp's for such team (whether they use Scrum or Kanban)?
Scrum prescribes these daily StandUp's, but they just don't seem to be always necessary.
Analeea last edited by
One of the advantages of having such a small team is that, indeed, the people in the team are able to communicate freely throughout the day. A lot of the daily stand-ups might thus often end very quickly and may look like they are a waste, but they can still have a purpose even in a small team like this: to provide extra focus.
The daily standup allows people to keep the sprint goal in sight so that they don't just organize their work, but organize their work to make progress towards the goal. That's the important thing. Your team might work and communicate efficiently, but sometimes they might focus too much on the work they are doing. A daily discussion around the goal of the sprint reminds people of why they are doing that work.
Of course, nobody forces you to have daily standups if not much is discussed or agreed upon there. You can build your own process around whatever events or artifacts you want, basically keeping from Scrum what works for you and discarding the rest, but the result can no longer be called Scrum, it will be your own thing.