From f0be38061b1a2c1947e202dec6b1739e1a5078bb Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Wed, 26 Jun 2024 10:12:41 +0200 Subject: [PATCH] Remove a part already described in another heading --- engineering/workflow/default-workflow.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/engineering/workflow/default-workflow.md b/engineering/workflow/default-workflow.md index d30719f3..47cea699 100644 --- a/engineering/workflow/default-workflow.md +++ b/engineering/workflow/default-workflow.md @@ -197,14 +197,6 @@ Team members are expected to try populate the board ahead of time to the extent The general rule is that actions are also work and should be refined and prioritized like any other work. -As such actions will enter the team's next sprint through the following process: - -1. At the end of the retrospective, the facilitator should create issues representing the actions on the Team's iteration board, in the `Backlog` or `Refined` queue depending on the level of detail/information detailed in the action. - -1. The retro action (having also met the team's Definition of Ready), is discussed during Iteration Planning and if committed, then it is added to the Committed Queue. - -1. Do the work :) - (coordination:deliverables)= ## Deliverables and work issues