Amplified Agile through Flow

Get Started. It's Free
or sign up with your email address
Rocket clouds
Amplified Agile through Flow by Mind Map: Amplified Agile through Flow

1. Presenter

1.1. Daniel S. Vacanti

1.2. [email protected]

1.3. @danvacanti



1.6. Suggests

1.6.1. Reading Principles of Product Development Flow -- Don Reinsertsen

2. Flow

2.1. definition

2.1.1. the movement through and delivery of customer value in a system

2.2. Continuous Flow

2.2.1. seems like kanban

2.3. Metrics

2.3.1. Work in Progress predictor of lead time and throughput

2.3.2. Lead Time answers "When will I get it"

2.3.3. Throughput answers "how many will I get"

3. Achieving Flow

3.1. Smaller Batch Size

3.1.1. Major benefit of scrum is shrinking the batch size

3.1.2. Some Scrum still have large batches and don't realize how that is problematic

3.1.3. Reduces Lead Time shortens the customer feedback cycle

3.1.4. Increases Quality defects are found sooner

3.2. Small Development Queue Size

3.2.1. Development queue needs to stay small as well problem comes in when blocked/bored and pulling on new (small) batches and work in progress (queue) gets too big

3.2.2. Creates true pull systems process and teams are not overburdened improves work life balance

3.2.3. Allows us to "see" flow impediments to the delivery of customer value are discovered more quickly

3.3. Blocked and Waiting Items

3.3.1. Show (kanban board) when a task is in a 'done'/'waiting' state for the next stage

3.3.2. Flow efficiency is by reducing the time items spend blocked or waiting

4. What's Hampering Flow

4.1. asside

4.2. Agile teams have optimized heavily the development part of the process

4.2.1. awesome, but from a system it eventually is shining a cannonball

4.3. Capacity Utilization

4.3.1. Highway joke 100% utilized highway is called a parking lot

4.4. Control through Planning and Estimation

4.4.1. Graph of story point estimate compared to cycle time (to done)