Here's This Agile Thing

00:17 Organizations trying to dictate delivery schedules

PMI project constraints: * Resources * Time * Features

11:40 How are target dates for release established?

19:15 Two different definitions of Minumum Viable Product (vs Minimum Marketable Product)

21:00 What happens when deadlines move back in an Agile development process?

25:00 How to accomodate unmovable, can't-miss dates in Agile: manage the risk

27:54 Value, and how to measure it

29:30 Verify the problem to solve, don't just take an order for a predefined solution

34:20 The value of automation (Continuous Integration / Continuous Deployment) in making value measurement easier

4:30 | Project to product

The 4 flow items (What flows through value stream networks) * Features * Defects (bugs) * Risks (security, compliance, etc.) * Debts

The 5 flow metrics (How to measure flow items) * Flow Distribution (how much of each type of flow item) * Flow Velocity (how much stuff total) * Flow Time (cycle time) * Flow Load (WIP) * Flow Efficiency 

Product Modeling Aggregating data from multiple tools (e.g., Jira, ServiceNow, Trello, VersionOne, etc.) into a single view of value flowing through the value stream network. Creates one unified view of product status fof senior leaders.

12:58 | How to set targets for flow items relative to each other

17:17 | Support:  Should product teams do it, or separate support teams?

24:53 | Estimation of defects * How to plan for the proper level of defect flow?

31:03 | Should you assess estimated effort vs. actual effort?

33:15 | What if defects overwhelm the system? * The relationship between defect flow items and debt flow items.

35:00 | What elements go into an estimation? * Effort, risk, complexity, etc. (Not time.) * Whole-team estimate, not individual estimates for roles added up. 

We start to unpack the implications (and meaning) of Team Topologies.

This is the story of the distraction monkey and the panic monster and the struggle to maintain focus.