[itamarst]

The best way to manage output (since that comes up a lot in other comments) is to:

1. Figure out bottlenecks and fix them, they may be individual, they may be on level of way team operates. E.g. "our tests are slow", or "Jane knows C++ but Joe doesn't, so only Jane can do C++ code reviews when they come up."

2. Talk about the reasons you want stuff done. This gives the team the opportunity to figure out better solutions, rather than just being code monkeys writing a spec.

Focusing on hours is a mistake: you focus on the thing you can measure since it's easy, even if that reduces productivity. Micromanaging people's hours is not a good way to increase productivity.