Please enable JavaScript.
Coggle requires JavaScript to display documents.
PRODUCT VS PROJECT - Coggle Diagram
PRODUCT VS PROJECT
PIVOTING TO A PRODUCT MODE
High performing teams
Maintain trategic focus
Truly iterative approach also for strategy
Costumer focused
Knowledge retention
Ownership of the code and systems
TRANSLATING
ENTERPRISE
STRATEGY
Product Portfolio (or Product Line)
: tied to a distinct business capability to deliver measurable business outcomes
Portfolio Management board
:
allocates funding across
each of the Product Lines
Product Line Council
: splits into
individual product streams
Product Council
:
splits into individual feature teams
Business outcomes
: business
needs in a measurable way
measurable
product outcomes
:
tied to those business outcomes
Key Performance Indicators (KPIs)
for each Product Feature team
ADAPTIVE FUNDING
From Annual
to Quarterly Cycle
(Re)allocation of Funds across Product Portfolios
(Re)allocation of Funds within a Product Portfolio
IMPEDIMENTS
partners reluctant to cede control of budgets
Product Managers lacking finance expertise
Resistance to funding not” fully detailed”
Requires structural changes to support
product-centric organization
Caratteristiche
Timeline: continuos
Team: Long lived teams
Funding: flow based value delivered
Delivery: iterative and incremental
approach continuously evolving
Success Measure: improvement directly
related to a business outcome
Caratteristiche
Timeline: defined start and end date
Team: Short term team
Funding: “all in” (the entire scope is funded)
Delivery: developed over a long period,
and released big bang
Success Measure: delivery on time
and in budget