Value Stream Levels Library

The Value Stream represents the work involved in the flow of Business value from initial idea to realization of value by the customer. It includes Business Discovery (prioritization, planning, staging, getting ready to pull) and Business Development (iterative development and incremental release).

In Lean-Agile, there are three levels in the value stream: Portfolio, Program, and Team.

Resources related to value stream levels

About the ADM and TDM Roles (Article)
Are We Using Automated Acceptance Tests? (Article)
Capability (Article)
Cross-Functional Teams: Improving Communication Between People who Work Together (Case Study) (Article)
Daily Stand-Ups (Article)
Do We Push, Plan or Pull Our Work? (Article)
Dynamic Feature Teams: When Static Won't Work (Case Study) (Article)
Going Beyond Scrum, Part 2 (Blog Entry)
How Easily Can We Import a Lean or Agile Framework Into the Organization? (Blog Entry)
How Is Integration Across Teams Being Handled? (Article)
How Is Work Within the Program Being Sequenced? (Article)
How Should We Manage the Number of Items in the Portfolio? (Article)
How Should Work at the Portfolio Level Be Sequenced? (Article)
How Small Are Our Stories? (Article)
How Will Architectural Capabilities Be Handled? How Will Architecture Be Prioritize Against Business Needs? (Article)
How Will DevOps Be Involved? (Article)
How Will Shared Services Be Handled? (Article)
How Will Teams Work and Deliver Together? (Article)
How Will UX Work With the Teams? (Article)
How Will We Make Visible Our Work at the Program Level? (Article)
If We Do Estimate, What Estimation Method Should We Use? (Article)
Iteration 0 - Conduct (Article)
Lean Leadership and Systems Thinking (Article)
Lean Portfolio Management (Blog Entry)
Lean-Agile Budgeting (Blog Entry)
Lean-Agile Coach Library (Article)
Lean-Agile Team Checklists (Article)
Maximizing Value Across Many Programs (Article)
Meetings for Lean-Agile (Article)
Middle Management and Lean-Agile (Blog Entry)
Online Learning (Article)
Overview of Roles (Article)
Portfolio Level Supportive Inflection Points (Article)
Product Portfolio Management: Essential for Agile at Scale (Blog Entry)
Program Level Supportive Inflection Points (Article)
Scrum of Scrums (Article)
Should We Estimate Our Work? (Article)
Software Development Skills Roadmap (Article)
Team Level (Process) Supportive Inflection Points (Article)
Team Level (Technical) Supportive Inflection Points (Article)
Technology Delivery Manager Library (Article)
To What Extent Will Test-First Methods Be Used? (Article)
Types of Tests for Code (Article)
Using Consistent Objectives to Enable Self-Organization of Teams Across an Enterprise (Article)
Using Visual Controls (Article)
Value Stream Mapping (Article)
What Design Method Will Be Used? (Article)
What Is the Budgeting Cycle? (Article)
What Is the Economic Cost of Delay for Software Delivery? (Blog Entry)
What Is the Ecosystem Structure at the Team Level? (Article)
What Roles Are Missing? Which Roles Need To Be Redefined? (Article)
What Test Harness for Acceptance Tests Will Be Used? (Article)
What is Agile at Scale? The Different Approaches to Achieve It | FLEX from Product Management to the Team (Article)
Why Looking at Time Is So Important (Article)
Writing Explicit Policies (Article)
Writing Tasks (Article)
Writing a Capability (Article)