Double-Loop Scrum

double loop scrum is a modification for teams that require a higher level of approvals and documentation before development work begins

The work is schedule for the next sprint but is worked on during the current sprint making traditional cycle time and kanban columns difficult to create within most tools. However, there are some tricks within them that can make it work. For example, within Jira by creating a sprint-based board the team can plan work into sprints, but for visibility of ongoing work a kanban board that shows work items within the current and the next (future) sprints works well.

Cycle time can still be achieved but again within Jira a kanban board is required to show the total time taken to deliver the item (e.g. story).

Last updated

Was this helpful?