4 ms·

> I'm in the lucky position to work in a fully output-based role, based on sprints and clear deliverables. One week before the new sprint, we agree in detail wh

> I'm in the lucky position to work in a fully output-based role, based on sprints and clear deliverables. One week before the new sprint, we agree in detail what gets delivered. And then I deliver, consistently and reliably. I take this extreme reliability very serious, as I don't want to be seen as some part-time worker or somebody not doing their part Is the nature of your work very predictable, or, do you tend to work overtime if you're not able to get a task finished when you estimated you could?

fleddr 5y ago
Nope, I rarely work overtime. Our estimation process is quite mature by now. I break down a larger technical solution into smaller pieces, which are then individually estimated by the team. Any potential pitfalls, risks and challenges I already researched, so they're calculated in. It leads to very few surprises. In the rare case that me or the team was way off, say something takes twice as long than expected, then we just move the second half to the next sprint. Some might find that a "luxury", we do not. Because we know that when we double load people, they stress out and make mistakes. Quality isn't optional in our game, we deploy to millions of consumers. Our rhythm is so predictable, that if you'd take away my agenda entirely, I'd still know exactly what to do on any given day.
foolinaround 5y ago
In an earlier workplace, where my team was delivering all the tasks agreed to sprint after sprint, my manager told me that i was less demanding on my team, since they seem to easily finish what they agreed on! Make more bricks!! Soon, the games started on inflating story points, etc, and i soon made my way out of there...
- actually_a_dog 5y ago
  > Make more bricks!! > Soon, the games started on inflating story points, etc, and i soon made my way out of there... Are you saying your response to your manager's observation was to crack the metaphorical whip and demand more from them? And that they adjusted their estimates upward in response? Do you think they were actually at their maximum sustainable velocity before? Would you have done it differently if you could go back in time and change what you did?
  - foolinaround 5y ago
    i never bought in to this, since the team was working hard, and had to support the odd production issues as well. However, the team did inflate the points for some stories, and then moved some stories across sprints from time to time. i hated the slavedriver attitude, and it was one of the reasons I left.

fleddr 5y ago

Nope, I rarely work overtime. Our estimation process is quite mature by now. I break down a larger technical solution into smaller pieces, which are then individually estimated by the team. Any potential pitfalls, risks and challenges I already researched, so they're calculated in. It leads to very few surprises. In the rare case that me or the team was way off, say something takes twice as long than expected, then we just move the second half to the next sprint. Some might find that a "luxury", we do not. Because we know that when we double load people, they stress out and make mistakes. Quality isn't optional in our game, we deploy to millions of consumers. Our rhythm is so predictable, that if you'd take away my agenda entirely, I'd still know exactly what to do on any given day.

foolinaround 5y ago

In an earlier workplace, where my team was delivering all the tasks agreed to sprint after sprint, my manager told me that i was less demanding on my team, since they seem to easily finish what they agreed on! Make more bricks!! Soon, the games started on inflating story points, etc, and i soon made my way out of there...

actually_a_dog 5y ago
> Make more bricks!! > Soon, the games started on inflating story points, etc, and i soon made my way out of there... Are you saying your response to your manager's observation was to crack the metaphorical whip and demand more from them? And that they adjusted their estimates upward in response? Do you think they were actually at their maximum sustainable velocity before? Would you have done it differently if you could go back in time and change what you did?
- foolinaround 5y ago
  i never bought in to this, since the team was working hard, and had to support the odd production issues as well. However, the team did inflate the points for some stories, and then moved some stories across sprints from time to time. i hated the slavedriver attitude, and it was one of the reasons I left.