Highly accurate estimates are critical under conditions of high uncertainty. Here's how to get a real-world grip on them.
If velocity is a lagging metric, what actually affects it in the first place?
Fix this _one_ thing, when you feel constantly weighed down by scheduling pressures and the passing of time
If a team really works well together, this one number will be really low under all circumstances.
Even though high growth requires you to adapt, how do you balance that with planning ahead? Here's how I learned about the sweet spot.
Running around after individuals with a stopwatch doesn't get you to "done" faster
The actual results of agile are significantly below what is promised. Most companies (often including vendors) applying agile focus on process, becaus...
Velocity this. Velocity that. Ultimately, if you want a quantiative early warning system, you need to have good metrics. And know how to use them.
Plan your team's capacity where there is a lot to get done and it all feels a bit wooly.
If your time frames are spinning out of control, it might be due this easily overlooked subtlety
Compare the true cost of centralized control and scope planning to alternative approaches
Resource optimization at most companies is still a bit medieval.