Timeboxing Flashcards
Encompasses the bulk of the development, addressing requirements and testing (technical and business) the Timebox products, in line with agreed priorities
Refinement
DSDM recognises two styles of timebox:
A DSDM structured Timebox
A free format Timebox
agreement on the Timebox deliverables happens during
Investigation
higher-level Timeboxes are managed through…
the control applied at the lower level – the Timebox
agreement on the acceptance criteria for the deliverables happens during
Investigation
The suggested timescale of a Kick Off
Approx. 1-3 hours for a 2-3 week Timebox
Refinement ends with a review from…
Business Ambassador
ensures all products meet their previously agreed acceptance criteria
Consolidation
The suggested timescale of a Close Out
Approx 1-3 hours for a 2-3 week Timebox
Formal acceptance of the Timebox deliverables by the Business Visionary and Technical Coordinator
Close Out
scenarios outside the empowerment of the Solution Development Team
Changing the breadth of the solution (i.e. adding to the high-level requirements or removing Must Have requirements)
Increasing the percentage of Must Have effort, either by introduction of new Must Have requirements, or by upgrading Won’t Have, Could Have or Should Have priorities to Must Haves
At the end of investigation the whole Solution Development Team review the following:
dependencies
Timebox Plan
Risks
short session for the Solution Development Team to understand the timebox objectives and accept them as realistic
kick-off
A DSDM structured Timebox comprises three main steps:
Investigation
Refinement
Consolidation
includes short Timebox retrospective workshop, to learn from the Timebox and to take actions to improve future Timeboxes
Close out
