In time management, a time box allots a fixed period of time for an activity. Timeboxing plans activity by allocating time boxes; and is a distinctive feature incremental and iterative application development.
Overview
Timeboxing is used as a project planning technique. The schedule is divided into a number of separate time periods (timeboxes), with each part having its own deliverables, deadline and budget
Importance
Timeboxing is a common and key Agile practice PMI-ACP Exam Outline Reference
c:Guide of the PMI-ACP|Community Guide of the PMI-ACP >Adaptive Planning
Body
History
Current practice
Agile Methods that use timeboxing
- Dynamic Systems Development Method (DSDN)
- In '> 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.(1)
- ' target='_blank'>Scrum was influenced by ideas of timeboxing and Extreme programming values communication, simplicity, feedback and courage.(6) For [[planning]],' target='_blank'>development is timeboxed into iterations typically 1, 2 or 3 weeks in length. The business [[[Requirement_prioritization '> 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. See also
Sources & Reference
(1) Poppendieck, Mary (2010). Leading Lean Software Development : Results are not the Point. Upper Saddle River, NJ: Addison-Wesley. pp. 137–140. ISBN 978-0-321-62070-5. (2) Coplien, James (2010). Lean Architecture for Agile Software Development. Wiley. Chichester Hoboken, N.J pp. 25 ISBN 978-0-470-68420-7 (3) Cohn, Mike (2010). Succeeding with Agile : Software Development using Scrum. Addison-Wesley. Upper Saddle River, NJ. pages = 257–284. ISBN 978-0-321-57936-2
(4) Leffingwell, Dean (2011). Agile Software Requirements : Lean requirements practices for teams, programs, and the enterprise. Addison-Wesley. Upper Saddle River, NJ. Page 15. ISBN 978-0-321-63584-6
(5) Schwaber, Ken (2009) Agile Project Management with Scrum. O'Reilly Media, Inc. New York. ISBN 978-0-7356-3790-0
(6) Beck, Kent (2000). Extreme programming eXplained : embrace change. Addison-Wesley. Reading, MA. pages 29-35 ISBN 0-201-61641-6
External Links
Enter Content Here
