andrewducker: (Default)
andrewducker ([personal profile] andrewducker) wrote2018-05-20 12:00 pm
skington: (chicken)

[personal profile] skington 2018-05-21 05:30 pm (UTC)(link)
As it happens, we dropped sprint partially because we weren't doing one thing for a fortnight and then switching to something else. (How would that even work, anyway, if you couldn't neatly divide all the work available into fortnight-sized chunks?)

But for the brief period when we did, by dint of people working flexitime and in different time zones (US, UK and Russia), the scrum meetings were unavoidably in the middle of the working day. And there's no telling where you'd got to before a scrum meeting became imminent; maybe there's only 15 minutes between the natural stopping point and your meeting, but maybe if you've finished something and your next thing is going to be large and consequential you might be unlucky and need 2 hours of uninterrupted time. Maybe I'm lucky, but I don't normally have an hour of admin stuff to do every day.

Look, it's not like we're waterfall-worshipping brutes; we have version control, continuous integration and code review, we do test-driven development, we refactor our code base to avoid tech debt, and all sorts of other sensible things that most programmers would naturally do without being told about them by someone trying to sell a buzzword-ladel book or course. It's just that on the narrow point of daily scrum meetings, we didn't find them useful.
ironymaiden: (Default)

[personal profile] ironymaiden 2018-05-21 06:40 pm (UTC)(link)

ah, missing data point! yes, I agree that scrum doesn't work well with distributed teams - been there. it was indeed a bad fit and an unrewarding chore, someone always got screwed on timing, it was easy for people to tune out of meetings or feel left out. (we had enough people to reorganize by geolocation, but obviously that's not a fit for everyone.)