levels of portfolio management in a lean software enterprise @ cloud 2011/q2 review 14.6.2011 jarno...
TRANSCRIPT
Levels of Portfolio Management in a Lean Software Enterprise
@ Cloud 2011/Q2 review14.6.2011
Jarno Vähäniitty ([email protected])Software Process Research GroupSoberIT
To see all Aalto WP2 results per quarter, Google for
”Aalto WP2 results”
Five topic alternatives for today:
• “Levels of portfolio management in a lean software enterprise” (10 votes)
• ”How the product backlog really works - results from a systematic study of research and practitioner literature” (8 votes)
• “Towards agile product and portfolio management” (5)• “Backlog management tool requirements for the lean
software enterprise” (2)• “Transparent collaboration and progress follow-up of
research themes in Aalto WP#2 using Agilefant” (1)
Audience demographics
• Please raise your hand if…– You are a university-paid researcher– You are an industrial participant
Overview of this ”collaboration thread”
Cloud Software Program2011 Deliverable:
BP for Scaling Agile
Collaboration Thread:
Linking Strategy with Action in Lean/agile R&D OrganizationsJarno Vähäniitty
Publication:
”Towards Agile Product and Portfolio Management” (Ph.D. Jarno Vähäniitty, submitted to preliminary examination 6/2011)
Aalto University
Software Process Research Group (SPRG)
Focus area:
Software Product Management
Publication:
”Blind Men and the Product Backlog” Submission to Journal of Empirical Software Engineering in Q3-Q4/2011
Presentation:
”Levels of Portfolio Management in a Lean Software Enterprise” (Q2/2011 review)
Today
For all results by Aalto WP2 per quarter, Google for
”Aalto WP2 results”
WP#2:
Lean Software Enterprise
The Product Backlog – Far From Simple!
“Product backlog as a prioritized, constantly emerging list of work” (Ambler 2008b)
The Product Backlog – Far From Simple!T
he product planning iceb
erg, adapted from
(K
eith 2010) – w
ho got it from (C
ohn 2
009)
Blind Men and the Product Backlog• ”It is a …”
– List of ”everything that needs to be done”• but idea pool kept separate
– Transcends any single release; sections:• Ongoing iteration• Up next• Ongoing release• Future releases
– Prioritized & elaborated just-in-time• Driven by vision => product & business goals• Ongoing iteration / Immediate future
– Ordered sequentially– Estimated in man-hours
• Further ahead– Estimated in abstract units– Order ”less sequential”
• A flat list … and a hierarchy!
Portfolio Management as Project Resourcing Decisions
Adapted from (Shalloway 2009)
Feature A1
Feature B1
Feature C1
Feature D1
Project A
Project B
Project C
Project D
Feature A2
Feature A3
Feature A4
Feature A5
Feature A6
Feature B2
Feature B3
Feature B4
Feature C2
Feature C3
Feature C4
Feature C5
Feature D2
Feature D3
Feature D4
Time