The Worst Agile Mistake I Ever Saw
Look, most software developers do not like Agile. Estimating your work, when you’ve never done that particular task before, doesn’t make any sense at all. Yet I think I’ve found the fatal mistake, which is destroying good software development at my company. I’m on a call with 19 people right now. Nobody can keep track of what is going on. I actually don’t know what most of the people do in my current team. People move from one team to another and oftentimes fail to give their status update in the morning as they are with the ‘other’ team at that time.Worse stand-up status meetings go on for a half-hour each and every morning.
That means I spend 2.5 hours every week not listening to my colleagues.I guess I should be grateful for our status ceremony. All our agile ceremonies overrun. People often come off mute in our mainly remote team and ask ‘sorry, what was the question’. Across the industry, I see the same problems regularly coming up. Recently I had a first-stage interview and the recruiter happily shared thatA single team should be a single team, no more and no less. That team should be as large as it needs to be to get the work done, no more and no less.
0 Comments