Darío Macchi

Nobody in history has gotten better at software development by having more meetings. Calling those meetings "events" doesn't change that. Time spent in meetings is time spent not working. Looking at Scrum, I can't see anything done in a single one of those meetings that couldn't be done better without the meeting. Let's look at a few: Daily Scrum: Unnecessary if you're working collaboratively in an ensemble or even talking to each other throughout the day. This is a meeting for the benefit of people who work in isolation so they can coordinate once a day. Stop working in isolation. Retros: Teams working in an ensemble don't need them. It assumes scatter/gather. That doesn't mean an occasional chapter/guild meeting isn't a bad way to coordinate with other teams, but the by-rote bi-weekling thing most Scrum Teams do is not that. When something goes wrong, pull the Andon Cord. Sprint Reviews. Dog and pony shoes are worthless. Release often--daily if you can. People who are interested in the state of the software can just look at it. Sprint planning--Have regular chats with customers all the time. If you haven't gleaned enough info to start from those chats, maybe you should work on that. Get active feedback as you work and collect additional info as you do that. Dump the damn tickets and the story points. They're actively destructive.

Gente que aprovecha la promo Guinness GRATIS para hacerse un buen set