4 ms·
> but at least this way if the developers are working a late shift because of a rash promise they’ve made, they are the authors of their own misfortune, which i
by wink 8y ago
> but at least this way if the developers are working a late shift because of a rash promise they’ve made, they are the authors of their own misfortune, which is easier to bear. It’s a social contract: we give people control, they accept responsibility.
Congratulations, your lead developer is now a middle manager.
I've never been a fan of "committing to a certain amount of stuff done by the end of the week" as in scrum sprints. It's a zero sum game. Sometimes you do 3 days' worth of work in an afternoon and sometimes finding an extra semicolon takes 2 days...
- accnumnplus1 8y agoTo your first point, I had a very productive project where instead of as in the article the devs become managers, our project manager was brought very much into the dev team, almost as a tester, using the product daily. He became attuned to the pace of development and never over-promised anything. To your second point, I've had projects where I simply assigned a day to every task, and it turned out remarkably accurate.