When too much time is spent documenting project requirements
An initial plan that stipulates the tasks to be accomplished, the labor and other resources assigned to those tasks, and the schedule for completion
The final work-breakdown structure that shows the planned tasks, dependencies, durations, and resource assignments
(1) Traditionally, the process of allowing future system users to try out the new system on their own. Used to locate program failures just prior to final program shipment; (2) In the Web-2.0 world, a tactic used by vendors of license-free software to enable the vendor to perpetually change the program, principally its user interface, at its own discretion and on its on time-frame. Such programs are labeled "beta" for many years with no announced schedule for making them "non-beta"
The famous adage that states: Adding more people to a late project makes the project later. BLANK is true not only because a larger staff requires increased coordination, but also because new people need to be trained. The only people who can train the new employees are the existing team members, whoa re thus taken off productive tasks. The costs of training new people can overwhelm the benefit of their contribution.
A set of management policies, practices, and tools that developers use to maintain control over the projects resources