This document discusses common objections to adopting Scrum and provides responses to each. It addresses concerns about the need for fixed dates and milestones, benefits of early development and testing, fears about changing scope or "descoping" work, working with clients, dealing with changing features, including various roles on Scrum teams, and addressing irrational objections to change. The key messages are that Scrum already provides planning mechanisms, changing scope can be managed, transparency builds control, and addressing people's concerns is important to overcoming resistance to the change that Scrum requires.