3 ms·
Disclaimer: I teach this stuff I don't make a big distinction in scrum, Kanban, Agile, agile, Crystal, etc. If the burndowns were buggin' you, stop the burndo
by DanielBMarkham 17y ago
Disclaimer: I teach this stuff
I don't make a big distinction in scrum, Kanban, Agile, agile, Crystal, etc.
If the burndowns were buggin' you, stop the burndowns. If the daily standups seemed pedantic, stop them (or better yet, fix them). If your team is too large, Kanban might give you a better sense of control but development's big obstacle is communication, not control.
I think Kanban boards are great. If it tickles your fancy, go for it.
But it's no more a silver bullet than scrum was. At the end of the day, teams that regularly adapt beat teams that jump from one big thing to another, apply it rigidly, then wait too long to jump to the next big thing. The idea is continuously tweaking what you're doing, not latching on to a marketing term.
Hope that didn't tick you off :)
- wallflower 17y agoNo you didn't tick me off and I will write a much longer response later. Disclaimer: We use this stuff. We are taught this stuff.
- DanielBMarkham 17y agoI should probably point out that I'm also a code monkey on an active startup and have written several programs over the years, some of which are in production serving millions of folks. So I use the stuff too. (The reason for the disclaimer is that saying I teach it should probably set off your alarm bells!)
- AlecM 17y agoDo you consult companies in implementing these practices? What was the largest team using Scrum that you felt was still effective? At my job, there's 30 people at the daily stand-up and it just seems out of control, especially as we pass a speaking stick across the group. What is this, Lord of the Flies?
- DanielBMarkham 17y agoYes. I'm a startup junkie and coder who ended up consulting companies in implementing these practices because once your development group starts growing, performance usually tanks. Big companies are looking at the stats and seeing that in some cases they are spending 10 times the cost and taking 4 times as long to develop similar software to what a small company can put out. So there's a big pain out there. Avoid large teams! The daily stand-up should be 5, maybe 10 minutes, and should move along very quickly. A 30-person team, especially if the PM is playing scrum master and doing Q&A during the stand-ups, can be the worst kind of death march. I've watched/participated in about 60 teams, and consulted with other coaches on probably 300 or so. Yes, there are 30-person teams that do well, but it's very rare, and usually there are other things that made them do well. Organizations consistently over-staff teams, especially those in trouble. It's depressing to watch, because it just makes matters a thousand times worse for everybody involved. Here's a corny tip that I found actually makes standups a little more bearable: Forget the speaking stick. Use a nerf ball, and forbid hand-offs. Everybody stands and nobody knows who's getting the ball next until the guy throws it. Also you have about 30 seconds to do your standup and then you're done, one way or the other. Standups should always add energy to the team and help with the day's agenda. If it's "Lord of the Flies" you guys are really out-of-whack somewhere.
- AlecM 17y agoWell, I was being figurative there, we actually do use a nerfball but I'm pretty sure it's universally despised. What usually happens is someone is done speaking, holds the ball up and looks around for a taker. No one ever really says, "Me next!" so it's thrown to a random person. At least one or two people will drop it per stand-up and someone else will always go, "Nice one, butterfingers!" and there's the awkward, uncomfortable laugh. I observed this practice for a couple weeks and came to an average of 2.8 seconds per ball movement. Times that by 29 (amount of passes) and you get 81.2 seconds per day we spend tossing that ball around. At an average salary of about $65K amongst the group, the company spends $42.29 per day on passing a ball around; that's just under a $11,000 a year! But I digress...
- DanielBMarkham 17y ago
- WorkerBee 17y agoWhat was the largest team using Scrum that you felt was still effective? At my job, there's 30 people at the daily stand-up Largest feasible scrum team size is around 12 people. Daily stand-up should take less than 15 minutes. If you can't consistently get it down to that, split into 2 or three smaller scrum teams. Do all 30 people work on exactly the same deliverables? I doubt it, so there should be a natural seam along which to split.