|
As a comparison, despite the agile suggested recognition that pointless wastes of time are pointless, we continue to do standup for approximately 15 minutes each day where the only thing anyone pays any attention to is whether its their turn to spout some words.
|
#
¿
Feb 22, 2016 02:11
|
|
|
|
| # ¿ May 11, 2024 11:05 |
|
|
Virigoth posted:This is my life but with derails often. I gave up trying to right the ship and just sinking with the rest of the crew. We don't even get that, I guess I can best describe it in contrast to THE SCRUM PRESCRIBED STANDUP. In theory, of course, the team is largely supposed to be self-organizing and "ok lets get stuff done!" So standup is a way to go "ok here's where stuff is at I'm making progress, could use a hand on, etc". But what we end up having occur is more: 1. *Most* of the team just blathers words because it's the ritual: "Yesterday I don't remember what I did. Today I'm going to be responsive to anything that comes up from QA. No roadblocks." is pretty much status quo. 2. Our Product Owner sits on the meetings and will tend to, maybe one day a week, toss random thoughts at us at the end of standup. It's the most pointless 15 minutes of my days, and probably incurs at least an hour of productivity loss for me on average(15 minutes for meeting, 15 minutes in either direction of 'don't get too involved with anything because standup soon' & 'ok that's over let's make some more tea and get settled in', and some additional time for follow-up meetings from standup, or just plain lose-my-concentration-gotta-get-back-into-it).
|
|
#
¿
Feb 22, 2016 05:04
|
|
|
Lord Of Texas posted:If no one pays any attention the problem might be that I hate noting it every time Agile enters the conversation, but there's a fundamentally greater problem at work: the majority of the team are either burnt out or mediocre. So the project runs less in an ideal "folks just dive in to get work done!" sense and more into "wait to be assigned something and then just keep using standup as a means to ensure folks know you are working on the thing you said you would work on and never ever step on people's toes." Oddly enough, this may actually be ideal, given the situation. Every time two developers work side-by-side on something that requires some coordination/integration of efforts, we inevitably end up in a room, for an hour or two, debating the practical merits of writing code like it's 2001, or accepting that a web project with modern web technologies should probably be written in modern fashion. Project Management: Ritualizing your attempts to solve personnel issues.
|
|
#
¿
Feb 22, 2016 21:17
|
|
|
My development team, sprint after sprint, continues to decide that *more* meetings is helpful. And every single one of them just devolves into bikeshedding and/or having to spend hours explaining the domain.
|
|
#
¿
Aug 26, 2016 11:47
|
|