Experiment:
Is it valid / valuable to replace bottom-up scheduling with top-down scheduling + slack + bottom-up scope control?
Context:
Currently I'm working as a Product Owner for a team of 7 developers. As a result, I've been thinking a lot about iteration planning and release planning. About 15 iterations ago we switched to top-down estimates--verified by bottom-up estimates and the team is allowed to reduce scope until they can find something achievable.
Results:
http://dhondtsayitsagile.blogspot.com/2010/04/fan-out-release-planning.html
What do you think? Comment here: