3 ms·
I think the problem is that in your average job, the company is paying you for your time, not your productivity. I mean they should be paying you for your produ
by overgard 12y ago
I think the problem is that in your average job, the company is paying you for your time, not your productivity. I mean they should be paying you for your productivity, but that's pretty hard to measure and easy to game.
I think it does have an unfortunate cooling effect though, in that, if they're paying you for your time there's no particular reason to put in extra effort to do things faster or better (other than personal pride and the nebulous possibility of a raise somewhere down the line).
There's been times I've gotten my entire sprint done in a couple days, only to get rewarded with... more stuff to do. That's not a criticism, I mean, that's the employment agreement I signed up for, I'm expected to do stuff 5 days a week, but I imagine that if I could get a sprint done in 3 days and then take 2 days off, I would be more motivated to get that stuff done quickly, and then QA would have more time to test it, and so on.
- vacri 12y agoWhich highlights another issue - when problems are found in what the dev has 'finished', where is the dev to talk it over or rework? It's like the good old "Don't push on a Friday", except now "Friday" can be Wednesday or Thursday. I imagine that there'd be more than a few of the less scrupulous devs who would push stuff earlier than they should (which creates more work for everyone downstream), to get the promised day off. In any case, if you do find yourself with extra days left-over in your sprint, why not tackle some tech debt or documentation, things that are usually lacking?