This document discusses challenges with software scheduling and provides recommendations to improve software schedule estimation and tracking. It notes that software schedules often slip despite experience and process improvements. Common causes of scheduling issues include poor estimates due to undefined requirements, changing requirements, or inexperience. The document recommends that software schedules align with system schedules and allow time for requirements, design, implementation, and testing cycles. It presents techniques like Evidence-Based Scheduling using past performance data to generate realistic schedules and functional progress metrics rather than lines of code to improve schedule tracking.