3 ms·
> What about online standups? Nobody is standing up and not likely to. Then it's not a standup. Maybe you can find another way to achieve the same aim, or mayb
by lmm 8y ago
> What about online standups? Nobody is standing up and not likely to.
Then it's not a standup. Maybe you can find another way to achieve the same aim, or maybe Scrum isn't suited to remote workplaces (I don't have enough experience either way) - if someone had tried to follow agile practice in a remote environment and found it doesn't work there, that could be criticism I'd be interested in hearing. But I just never get the sense that someone has actually engaged with Agile and found it wanting[1]; it always seems to come down to something like them: "Agile sucks" me: "What's wrong with it?" them: "We have this mandatory Agile meeting that everyone involved in agrees is pointless", just some criticism of something that has nothing in common with Agile except for both being a process.
> What about managers that fall into injecting themselves into every standup? Hard to fix that, hard to eject your manager from a meeting, and its a likely state that becomes the inevitable end point (see Markov Chain).
I haven't experienced managers in standups being a problem, but taking it as given that it is for you: if you're saying that you can't fix that then aren't you essentially saying that any process that your organization adopts will inevitably fail (unless you adopt a process with no meetings at all, which has other problems)? Agile gives you every possible explicit opportunity to fix the broken things in your process, including a regular dedicated meeting that's devoted solely to doing that; if your organization is incapable of doing that then I'm not sure what could ever work.
[1] Not actually true; there is a group of people who prefer more up-front planning and tend to give a quite different genre of critique. But they also tend to be more measured and don't frame it as a problem with agile as such.
- JoeAltmaier 8y agoHere's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities. In fact keep everybody out of my way. Agile explicitly puts people in my way, regularly, and with demands that I report progress with imaginary metrics. That's how I'd fix it. In fact I became a contractor so I didn't have to do agile any more. Now I get tremendous amounts of work done, using my experience and talent to attack root causes and write the critical code to get the job done. I see its a whole different attitude from Agile, I get that. But I'm adamant that I don't want what Agile does.
- lmm 8y ago> Here's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities. In fact keep everybody out of my way. Hah, I almost said that that's where this genre of agile criticism seems to come from: the coder who believes they can produce a good product by writing good code without interacting with a customer and so regards any process as an impediment, and isn't actually attacking agile so much as attacking the very concept of process. What you propose is a good way to produce elegant code that doesn't actually do what the customer wanted at all; even if you personally can magically understand the requirements every time, a customer (or a manager) is right to be skeptical, because most programmers can't.
- JoeAltmaier 8y agoMost of the friction in agile is not about the customer. Where did that come from? Not fair to switch the subject for a pretended win!
- lmm 8y agoCustomer collaboration is right there in the manifesto.
- BeetleB 8y agoConsistent with the comment lmm made, your comment is almost the reason Agile exists. Your approach doesn't work well for most employees. It may for you, but an expectation that all software developers be as reliable as you is poor. Now getting to specifics: >Here's a process that works: leave me alone to get the job done, and I'll report progress to you regularly. Leave the manager out of my day to day activities. I do not think agile requires the manager be involved in day to day activities. If he's insisting on it, he's the problem - not agile. Reporting progress daily is reporting progress "regularly". Having said that, I do not think agile requires daily progress reports. As for leaving you alone - that's great if your work doesn't depend on anyone and no one depends on your work. It works if your work is small enough that it can be done by one person. Rarely is that true. But if it is for your work, by all means it's a fine approach. >That's how I'd fix it. In fact I became a contractor so I didn't have to do agile any more. Now I get tremendous amounts of work done, using my experience and talent to attack root causes and write the critical code to get the job done. There's plenty of work that can be done that way. I think you'll find plenty that cannot. I don't think you can build a standards observing web browser as a contractor.
- Goronmon 8y agoThen it's not a standup. Maybe you can find another way to achieve the same aim, or maybe Scrum isn't suited to remote workplaces (I don't have enough experience either way) I haven't had too many problems with online scrums/standups. The basic rules are the same, every gives a quick breakdown on what they did, what they are doing and any issues they have. You just don't have people physically in the same location. I will say the biggest help when dealing with the remote situation is having someone willing to take decent notes and send a quick email with a summary, which helps compensate for the lack of face-to-face.
- wst_ 8y ago> Then it's not a standup Why not? Who cares if they're actually standing? They can lay on the floor if you ask me, as long as they can share the status with team members. I see a different problem with standup. Plenty of people applying the same rule over and over without understanding what's the real goal of standup. Plenty of people just take the virtual stick of the speaker (or sometimes not virtual) and say the same mantra every morning "I've done this, I'm doing that, no problems," and pass the stick to another. But the real goal is not to check up on people to make sure they are doing something. In fact I couldn't care less if you are doing something or not. You could sit there watching cats videos all day as long as, in the end, all TASKS are completed. If you can sit doing nothing your team have a different problem, obviously, but that's another story. The team have made a commitment on Monday that they deliver some features till Friday (assuming weekly iteration.) So what they do? They create tasks. The team is tracking the tasks on the board and the team should check all tasks every morning. Start with task #123. Who's doing it? John. So, John tell us about it - what's status, when can you complete, is everything smooth? Then you take next task - #124. Who is doing it? No one. But then John says he can complete current task today, so he's going to take it. And another task... Your standup should be about tasks, not about people. The difference is subtle, because it the end everyone should share the same info - progress, blockers, etc. But by checking on tasks the team members automatically build mental model of current iteration. How far are they? Is the tempo OK? Or maybe there's some delay and, finally, can they deliver on time? People will understand better where they are somewhere in the middle of the week and this is the key point. To share and understand. Not to report, forget and just go doing your job. The output of the iteration is the work done. Check the work, not the people.
- lmm 8y ago> Who cares if they're actually standing? They can lay on the floor if you ask me, as long as they can share the status with team members. Standing up was a specific solution to a specific problem. There may be other ways to achieve the same thing, but you should be aware of what you're doing. > Your standup should be about tasks, not about people. The difference is subtle, because it the end everyone should share the same info - progress, blockers, etc. But by checking on tasks the team members automatically build mental model of current iteration. How far are they? Is the tempo OK? Or maybe there's some delay and, finally, can they deliver on time? This really doesn't seem such an important distinction. You assign tasks to people in your iteration planning; if a task is stuck it will be because a person is stuck on it and vice versa.