[stewiecat]

This is the battle I fight every day. I'd rather have a workload that's 110% of my capacity than be at 50%, which I generously where I'm at now.

We're an "agile" shop that grossly under-allocates out of fear of failing a sprint.

[Stormbringer]

This also happens in those implementations of Agile where they try to pretend that programmers are all easily interchangeable cogs in a machine. The problem is, anybody they get who is better than average or has some natural talent is going to be bored out of their tree.

What I would do, is start picking future cards and then when they come up give ridiculously low estimates for them (because they were already finished on my machine :D ).

"Oh, you want a persistence layer for all this? Okay, that will take... -17 minutes."

Or, alternately, if I didn't want to bend people's minds or break the wills of the junior programmers (messing with the jps is half the fun of these sorts of things :D ), I'd work on some technical debt, since Agile projects tend to accumulate it faster than a sophmore with Daddy's credit card.