A Practical Advice to Shorten Daily Stand-up Meetings in Software Projects

Daily Automate End-to-End (via UI) Regression Testing.

Let’s start with two joke images (by IT people).

Credit: https://twitter.com/TheAnkurTyagi/status/1653297711616016386/photo/1; https://www.linkedin.com/posts/michael-lloyd-124621177_it-worries-me-how-often-i-see-scrum-masters-activity-7104575606557679616--Kva

Long stand-up meetings are common in software projects and are bad. As an engineer, I will quantify the three adjectives in the above statement:

• Long (stand-up meetings)
  According to the classic “The Art of Agile Development” book, 11 minutes is already too long.

from the classic “The Art of Agile Development” book, “https://www.jamesshore.com/v2/books/aoad1/stand_up_meetings,

• Common
  Over the last 16 years, most of the software projects I have been involved with or witnessed had long (30 min+) stand-up meetings daily. Typically, the team members talk about the user stories they have been assigned (with Jira open) one by one.
• Bad
  The purpose of ‘stand-up’ is to make meetings short. In fact, in many software projects, “stand-up meetings’ became ‘sit-down meetings’.

Table of Content
∘ How shall ‘Daily Stand-up Meetings’ be? and vs. the reality.
∘ Most Attempts to Shorten Stand-up Meetings Failed, Why?
∘ How dose my approach solve the problem?