A Model for Software Development Effort and Cost Estimation
IEEE Transactions on Software Engineering
Rapid Development: Taming Wild Software Schedules
Rapid Development: Taming Wild Software Schedules
Measures for Excellence: Reliable Software on Time, within Budget
Measures for Excellence: Reliable Software on Time, within Budget
Multi-Project Management in Software Engineering Using Simulation Modelling
Software Quality Control
Time boxing planning: buffered moscow rules
ACM SIGSOFT Software Engineering Notes
| Hi-index | 4.10 |
A time-bound project is constrained by hard deadlines, in which the delivery's timing is as important as the delivery itself. Because most time-bound projects start with more requirements than developers can handle within the imposed time constraints, requirements often must be slashed halfway through the project, resulting in missed deadlines, customer frustration, and wasted effort. A better approach defines requirement priorities before the project's start. But failing to prioritize requirements is not the only reason that projects miss deadlines.Traditional planning methods' inability to deal with uncertain estimates and their failure to recognize that development work does not progress linearly are also to blame. Statistically Planned Incremental Deliveries offer an approach that addresses these problems by combining ideas from critical chain planning, incremental development, and rate monitoring into a practical method for planning and executing time-bound projects.