[TsomArp]

Before the Agile manifesto, before Scrum/XP/Lean became popular, I had my own way of delivering software which basically was: meet with users/stakeholders, talk about what they need, build a first version in 2 to 4 weeks, release, test, adjust, repeat. For me it makes so much sense agile that I don't get why some devs don't understand the beauty and simplicity of it.

If you want to know more about the why of the standup, and what is the idea behind it, read Borland's tell: https://www.scruminc.com/origins-daily-standup/

[FZ1]

The origin of the "standup" is just a regular daily coordination meeting - like thousands of organizations have always had.

Ever heard of a "morning sales meeting"? They've existed for decades - short, to the point, 15-20 min. No one's ever heard of scrum in sales meetings. This kind of thing exists in hundreds of other businesses as well.

Much like everything else in scrum, they are just trying to take credit for something people already did - so they can package it and sell it back to people as if it were a novel idea.

There's nothing new or special about scrum - except a reduction in productivity because of the additional overhead and meetings.

[_y5hn]

So it's a copy of a copy (Borland team), of something entirely unrelated (rugby).

Also, it's for "our own good" and "we should own the process ourselves". While saner interpretations of AM are to be strictly verboten.

Only time I've seen such meetings not devolve into a status meeting, is when PM actively sought to cast light on potential issues and inquired about who need information, etc. This was effectively rooted out when SAFe came and eliminated PM-role entirely, while hiding discovery and decisionmaking processes, keeping them secret.

Of course, past poster child examples have nothing to do with Attention- and Selection bias either.

[oxfordmale]

Being Agile has often little to do with being agile. True "agile" development has nothing to do with story points, daily stand up, bi-weekly planning poker sessions, retrospectives, spikes, scrum masters, etc, etc