> getting everyone to frequently think about deadline/feature trade-offs I never let anyone else impose a deadline and a list of features on my schedule. If t

> getting everyone to frequently think about deadline/feature trade-offs I never let anyone else impose a deadline and a list of features on my schedule. If the features are mandatory, I will provide the deadline. If the deadline cannot be missed, I will accept a sorted list of features (by priority). In both cases, I'll do my best to cram the most value possible in the next release, but the sooner I need to commit to its content, the poorer it will be. If the deadline and the list of features are both set in stone, then it's not my problem.