5 ms·

In my opinion, the good thing about Scrum is that you can tweak the rules to fit your needs, aka, "Scrum in name only". The daily standup, IMO, should be only

by mms1973 10y ago

In my opinion, the good thing about Scrum is that you can tweak the rules to fit your needs, aka, "Scrum in name only". The daily standup, IMO, should be only to remove impediments, and if you have none, then a sentence or two will suffice. I see the DS as the most useful meeting, as you are aware of what your workmates are doing. And if Scrum is still a pain in the back, then you have Kanban, which is sort of Scrum without the straitjackets.

blub 10y ago
This kind of tweaking is frowned upon and you will be chastised for doing it. Yes you can do it (and probably should when you understand the purpose of each Scrummy practice), but don't expect to be praised by Scrummers.
- nl 10y ago
  I've had people on my team frown at my tweaking. I'm extremely happy to discuss the reasons I want to change something, but all to often the only counter-argument is "that isn't Scrum". I'm 100% fine with that, but I'm not going to do something if the only reason for it is religion.
- matthewmacleod 10y ago
  That's nonsense, in my experience. Most people doing Scrum-like development in my experience are much more interested in a development process that works well and produces good results than they are about over-attachment to process.
humanrebar 10y ago
> The daily standup, IMO, should be only to remove impediments, and if you have none, then a sentence or two will suffice. 100% this. The only thing a synchronous team-wide meeting is useful for is revealing a significant issue and getting a prompt and definite acknowledgement from the team. And then, if it's a priority, some help with the issue. But given the proper tool, even that feature can be made asynchronous.
- gtirloni 10y ago
  IMHO, unfortunately standups tend to become status report meetings just for the sake of it (article talks about control, I think it nails it). I rarely see anyone bring a blocker. It's just "yesterday i did this, today i'll do this. Next!". It gets worse if the team is actually 2-4 different teams with not much overlap (because companies tend to adopt these agile methodologies without much thought and it just keeps growing and including more people because.. it's nice, right?). Then you're ignoring (or not having a clue) about 90% of the meeting, and it's _daily_.
mobiuscog 10y ago
If developers talk within their team, they should constantly be aware of what their workmates are doing. If communication is a problem, having a daily standup just pretends the problem doesn't exist, rather than solve it.
afroisalreadyin 10y ago
This is also what I see the best-led companies do, not caring about what is Scrum and what it is not, and taking the pragmatist path. One thing I really regret at my current job is missing the Kanban workshop. It definitely appears to be much nicer.

by mms1973 10y ago

blub 10y ago

This kind of tweaking is frowned upon and you will be chastised for doing it. Yes you can do it (and probably should when you understand the purpose of each Scrummy practice), but don't expect to be praised by Scrummers.

nl 10y ago
I've had people on my team frown at my tweaking. I'm extremely happy to discuss the reasons I want to change something, but all to often the only counter-argument is "that isn't Scrum". I'm 100% fine with that, but I'm not going to do something if the only reason for it is religion.
matthewmacleod 10y ago
That's nonsense, in my experience. Most people doing Scrum-like development in my experience are much more interested in a development process that works well and produces good results than they are about over-attachment to process.

humanrebar 10y ago

> The daily standup, IMO, should be only to remove impediments, and if you have none, then a sentence or two will suffice. 100% this. The only thing a synchronous team-wide meeting is useful for is revealing a significant issue and getting a prompt and definite acknowledgement from the team. And then, if it's a priority, some help with the issue. But given the proper tool, even that feature can be made asynchronous.

gtirloni 10y ago
IMHO, unfortunately standups tend to become status report meetings just for the sake of it (article talks about control, I think it nails it). I rarely see anyone bring a blocker. It's just "yesterday i did this, today i'll do this. Next!". It gets worse if the team is actually 2-4 different teams with not much overlap (because companies tend to adopt these agile methodologies without much thought and it just keeps growing and including more people because.. it's nice, right?). Then you're ignoring (or not having a clue) about 90% of the meeting, and it's _daily_.

mobiuscog 10y ago

If developers talk within their team, they should constantly be aware of what their workmates are doing. If communication is a problem, having a daily standup just pretends the problem doesn't exist, rather than solve it.

afroisalreadyin 10y ago

This is also what I see the best-led companies do, not caring about what is Scrum and what it is not, and taking the pragmatist path. One thing I really regret at my current job is missing the Kanban workshop. It definitely appears to be much nicer.