3 ms·
Everyone can, but why would anyone do? Our default state is "I don't care what you do, that knowledge is a distraction detrimental to my own work. Ideally I'd w
by usrusr 4y ago
Everyone can, but why would anyone do? Our default state is "I don't care what you do, that knowledge is a distraction detrimental to my own work. Ideally I'd want you all to work, if you have to, when I don't". The rituals exist to break down those walls, even if just a little.
It's best illustrated by the author's failure indicator "If the manager or “scrum master” can’t show up, the stand-up doesn’t happen". That's so very telling.
The alternative approach of the chat reminder tries to minimize friction (short writeup is so much easier to consume than trawling The Board) instead of forcing everybody to be present (and presumably listen, which does not necessarily happen)
- nivertech 4y ago> "Everyone can, but why would anyone do?" Some of us do care and see the big picture of things, but that mostly limited to tech/product companies/startups, much less so to enterprise employees, or agency-supplied contractors. I.e. it boils down to incentive alignment, and to a lesser extent professional curiosity. > "I don't care what you do, that knowledge is a distraction detrimental to my own work." Agree, so it doesn't matter whether this distraction is done by issue tracker, email, or an actual meeting. At least in the issue tracker case it's stored in a structured database which I can easily query (even programmatically via API/bots), and much less distractive than in email/meeting.