A detailed discussion of these questions can be found in the "Appendix A" section on page 550.
How can you rescue a slipping project and bring it back on track?
What's the correct response to having a deadline imposed on you before feasibility or planning work commences?
How do you ensure that a development plan is genuinely useful?
Why do different programmers work at different rates? How can you reflect this on the plan?
What percentage of the projects that you've worked on have run to schedule?
For those that did: What contributed to the success of the planning effort?
For those that failed: What were the main problems?
How accurate are your timescale estimates? How far off target are you normally?