to perform the work. Team-related issues can include trouble with inter-team communication; lack of experience or required cross-functionality; lack of commitment/drive/motivation (i.e. poor team building and management). To stay on deadline, the following actions against the triple constraints are commonly evaluated: Reduce scope: drop requirements of lower impact (the ones that will not be directly missed by the user) Time is the fixed constraint here Increase cost: e.g., add overtime or resources Adoption in software development Many successful software development projects use timeboxing, especially smaller ones. Adopting timeboxing more than tripled developer productivity at DuPont in the '80s. In some cases, applications were completely delivered within the time estimated to complete just a specification. However, Steve McConnell argues that not every product is suitable and that timeboxing should only be used after the customer agrees to cut features, not quality. There is little evidence for strong adoption amongst the largest class of projects. Timeboxing has been adopted by some notable software development methodologies: Dynamic systems development method (DSDM) In lean software development, pull scheduling with Kanban provides short term time management. When developing a large and complex system, when long term planning is required timeboxing is layered above. Rapid application development (RAD) software development process features iterative development and software prototyping. According to Steve McConnell, timeboxing is a "Best Practice" for RAD and a typical timebox length should be 60–120 days. Scrum was influenced by ideas of timeboxing and iterative development. Regular timeboxed units known as sprints form the basic unit of development. A typical length for a sprint is less than 30 days. Sprint planning, sprint retrospective and sprint review meetings are timeboxed. In Extreme programming methodologies, development planning is timeboxed into iterations typically 1, 2 or 3 weeks in length. The business revalues pending user stories before each iteration. Agile software development advocates moving from plan driven to value driven development. Quality and time are fixed but flexibility allowed in scope. Delivering the most important features first leads to an earlier return on investment than the waterfall model. A lack of detailed specifications typically is the result of a lack of time, or the lack of knowledge of the desired end result (solution). In many types of projects, and especially in software engineering, analyzing and defining all requirements and specifications before the start of the realization phase is impossible. Timeboxing can be a favorable type of contracting for