BC1-Establish Flow Of Work

  1. /
  2. Basecamp 1
  3. /
  4. BC1-Establish Flow Of Work

Why

Teams must understand how work flows through the system based on the Agile Governance model. Each level within the model has a role in breaking work down as it flows through the system, all while getting prioritized and solutions are created. Breaking the work down helps clarify the backlog. It ultimately allows the Delivery team to have a refined, manageable backlog and an understanding of their capacity and velocity to plan sprints. All teams will track work through an ALM tool and potentially a visual board to accompany the digital version.

How

Now that teams have been formed, they are holding ceremonies and have a common understanding of Agile fundamentals, it’s time to help them understand how work will flow through the system. In order to understand when work is in a “ready” state for intake and in a “done” state that meets the success criteria, teams must create their Definition of Ready (DoR) and Definition of Done (DoD) and add it to their team Charters.

In order for teams to write good Epics, Features, and User Stories, they must understand the customer and the problem the customer is trying to solve. Through Empathy Mapping, Impact Mapping, and Story Mapping activities, teams will journey through scenarios to help create solution options. As those options are discussed, they will be crafted into either Epics or Features based on rapid estimations.

As the work starts to take shape, it needs to be visible and transparent to all teams; this will be accomplished by building the Governance Model into an ALM tool. Teams will utilize the backlog created in the tool, along with either Kanban or Scrum methodology to track the work in the system. As the Epics are created, the Product and Delivery Teams will continue to elaborate on Features and begin to write initial User Stories that the Delivery Teams can use to refine and create solutions for.

Success Criteria

  • Agile Governance model is understood and followed (shu-level)
  • Team workflows are created and used within the ALM tool 
  • Definition of Ready (DoR) and Definition of Done (DoD) created and published as part of each team Charter 
  • Entrance/Exit criteria for Kanban state created and published 
  • ALM & Visual Management boards created and used

Supporting Material 

Coaching Activities

 

General Training

Provide training and help to create an understanding, through various tools, of how teams can best understand their customers and how they can create solutions to their customers’ problems . 

Create a common understanding of how to write User Stories. 

For teams that will not be working within a Scrum environment, provided training and guidance on how to structure their Kanban environment best

Establish How to Manage Epics

Further understanding of the governance model by training Product Category and Product Line Teams on how to write Epic Briefs. 

Ensure that a clear policy is in place for Epic intake

Establish How to Manage Features

Further understanding of the governance model by training Product Line Teams on how to write Features. 

Provide hands-on training for Story Mapping

Establish How to Manage Stories

Further understanding of the governance model by training 

Product Line and Delivery Teams on how to write User Stories

Define Backlogs

The Expedition begins to craft and ready their backlogs to flow through the System of Delivery

Basecamp 1 Outcomes

Form Teams     |     Establish Flow of Work     |     Make & Meet Commitments   |     Improve the system     |     Stable Throughput     |     Road Map     |     Release Plan     |     90 Day Rolling Backlog