WHAT ABOUT THE TEAMS
PROGRAM KANBAN
DEFINING FEATURES
WHAT'S WRONG?
100

Number of trains or teams that can own and develop a feature?

What is MULTIPLE teams on a SINGLE train

100

WIP limited phase/state used for refinement>requirement elicitation, business value, sizing and splitting features 

What is Analysis

100

Required in a fully refined feature, describes the proposed value for the end-user or business


What is benefit hypothesis

100

Feature Title/Summary: Build the alert table 

Describes internal work required rather than the functionality or deliverable to the customer

200

True/False - PO's / BA's must wait until after a Product Manager refines/analyses a feature before they can decompose features into stories?

False. POs contribute to the feature refinement process and can start decomposing into stories for the team backlog DURING the Program Kanban Analysis State.

POs/BAs MUST understand the vision, purpose and acceptance criteria of a feature in order to create stories that support and are within the scope of the defined feature.

200

3 key roles expected to contribute and collaborate to define features in the local context of an ART

What is Product Managers, Product Owners, Epic Owner

Will also accept: Solution Architect (enabler features) or "Other key stakeholders"

200

True/False - Features should be written in the user story voice (As a , I want, So that)

False

200

Summary: First year commissions for brokers

Benefit Hypotheses: pay and retain advisers

Estimate: 12 Story points

Missing Acceptance Criteria

300

Highly collaborative event where teams take ownership of the suggested Features and work with their Product Owners to identify, estimate and elaborate the Features and their Stories.

What is Program Increment Planning (PIP)

PI events are not just intended to identify the work and sequencing of stories for the PI. CONTINUOUS refinement of the features by the team and collaboration with other teams during PI is encouraged

300

Product Manager planning/forecasting tool used to communicate the planned sequence of capability or feature delivery

What is PI Roadmap
300

The duration used when sizing and splitting features. 

A feature should be easily delivered in what timeframe?

What is 1 Program Increment (PI)

300

Title/Summary: Perform analysis

No value to customer. Analysis is expected for each feature as part of the Program Kanban phases. If work is required before a feature can be defined, a SPIKE should be created rather than a business feature.

400

True/False - TEAMS can negotiate the scope, stories and acceptance criteria for each Feature during PI planning

TRUE

400

When and how are features estimated?

What is Analysis state, in normalized story points

Feature estimation usually occurs in the analysis state of the Program Kanban and relies on normalized estimation techniques

400

MVP and Capabilities are a deliverable of what and by who?

What is Epic Refinement, Portfolio Layer

Owner: Lean Portfolio (BPMs for Guardian)

PMs/POs are recipients of information and may be asked to contribute or participate in relevant epic refinement sessions but can not own or take away too much time/effort from Program and Team level responsibilities

400

PI Objectives: Deliver systematic onboarding (application submission) & Create a centralized customer data repository

Team's Feature Planned for PI: Move commission cycle time to monthly instead of quarterly.

What is: Feature doesn't align or support any of the established Program Level Objectives for the PI.

500

Name 2 behaviors that contribute or cause "The Waterfall Downward Spiral" for Features. SEE IMAGE

What is:

Hand-offs and sequencing efforts through Program and Team layers.

A handover mentality-Limiting discussion or NEGOTIATION during feature refinement or  PI planning. See INVEST

500

Where fully refined features are found (in priority order) and pulled from for PI planning purposes

What is Program Kanban BACKLOG

500

Multiple ARTs functioning simultaneously to build a solution in fully integrated increments

What is Large Solution

500

Feature Summary: PI-6 KTLO Maintenance



What is EVERYTHING (smile). You can't identify benefit nor Acceptance Criteria with no defined work. Consider discussing and negotiating the key maintenance items during PI planning.