50
Framgångsfaktorer för Agil Utveckling av Mycket Stora Programvaruprodukter PMI Sweden Chapter Passion for projects 2013 Svante Lidman, Senior Productivity Expert [email protected] @svante_lidman www.slideshare.net/SvanteLidman

My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Embed Size (px)

DESCRIPTION

This is my "Success Factors for Agile Development of Very Large Software Products" as it was presented at the PMI Sweden Congress on March 11 2013. The title of the presentation is in Swedish but the material is almost completely in English.

Citation preview

Page 1: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Framgångsfaktorer för Agil Utveckling av Mycket Stora ProgramvaruprodukterPMI Sweden ChapterPassion for projects 2013

Svante Lidman, Senior Productivity [email protected]@svante_lidmanwww.slideshare.net/SvanteLidman

Page 2: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

?

Page 3: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Large Products?Vafalls, Stora Progamvaruprodukter?

Star Wars - The Old RepublicLucas Arts, Bioware, Electronic ArtsMicrosoft

Autodesk

Ericsson

Boeing

Page 4: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Why Agile?

• Are we and customers happy with the lead time from idea to volume deployment?

• Are we and customers happy with product quality?

• Are we happy with R&D efficiency?

• What will our situation look like tomorrow if we continue as we do?

Page 5: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

SalesVolume

10% Efficiency increase in R&D

10% Increased speed

(Sales earlier)

R&D (~15%)

Jan Bosch - www.janbosch.com

The Importance of Speed

Page 6: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Conclusion

• Conformance to original budget is secondary• Conformance to original scope is secondary• Time to market and Quality is key!!

http://commons.wikimedia.org/wiki/File:PenroseTriangle.png

Page 7: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

The Themes of this Talk

• Look at product development holistically• All development work is not the same• Self-organization

Page 8: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Holistically Speaking...

8

http://commons.wikimedia.org/wiki/File:Whole_onion.jpg

Page 9: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

What is Our Job?

Opportunity / Problem

Value /Solution

Product management &Development

Page 10: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Feature X

What we set out for

Page 11: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Feasability

Prestudy

Development

FeasabilityFeasibility

Pre-study

The Traditional Way

Page 12: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Feasability

Pre-study

FeasabilityFeasibility

The Traditional Way

Development

Page 13: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Construction

Test

Feasability

Pre-study

FeasabilityFeasibility

The Traditional Way

Page 14: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Construction

Test

Feasability

Pre-study

FeasabilityFeasibility

The Traditional Way

Page 15: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Test

Feasability

Pre-study

FeasabilityFeasibility

The Traditional Way

Part NPart 1 …

Page 16: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Test

Feasability

Pre-study

FeasabilityFeasibility

The Traditional Way

Part NPart 1 …

?

???

???

??

Page 17: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Common Challenges

• Time slicing of people• Handovers of documents resulting in distortion• Coordination issues • Quality issues uncovered too late• Lead-time too long• Very few people understand the overall system• Too many meetings• Blame games

Claim: The fragmentation of value(work)is the single most important root cause for these issues

Page 18: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

What is Our Job?

Opportunity / Problem

Value /Solution

Product management &Development

Pre-study

Execution

Prestudy

Feasibility

Technical coordinationProject Leaders Integration Test

Program Management

ALM

FG

PG

BP4

PD1

PD2

PD3

TG1 TG2

TG3

Integration PlanningCCB

Design

Anatomy

Release Strategy

Go-model

Projects

Requirements Baseline

VisionResource Planning

Defect-handling

FEAD

1/3

2/3

System

Design

V-Model

PDU

PA

Project Plan

Business Case

CR-handling

War room

RequirementsManagement

Steering Group

Contract Management

Page 19: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Key Ideas

• Focus on flow, customer-to-customer– Optimize for short end-to-end lead-time – Stop-the-line mentality regarding faults

• This will expose inefficiencies and force:– Removal of handovers– Removal of overly detailed studies

and gold-plated designs– Removal of late and non-repeatable testing

• The focus on flow and lead-time will act as aforcing function to address impediments toquality and efficiency

http://commons.wikimedia.org/wiki/File:Bulbgraph.svg

Page 20: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Key Concepts• End-2-End Cross Functional Teams for Development• Pull based approach• Continuous programs rather than finite projects• Continuous Integration (and Testing)

– Automated, continuous, fast and reliable feedback to teams• Requirement Areas (RA) as scaling concept

– Yearly budgeting (in terms of teams) per RA coupled to business strategy– Independent prioritization per RA– Limits competence challenge for Teams without code ownership

http://commons.wikimedia.org/wiki/File:Stock_keyring.svg

Page 21: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Flow Based OrganizationAnalysisProgram

DevelopmentProgram

- Identify- Analyze- Prioritize

- Detail- Design- Implement- Test- Document

- Package- Verify- Roll out

ReleaseProgram(Project)

Page 22: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Seen Another Way…

Release Program (Projects)

Page 23: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Meanwhile @ Spotify...

23Henrik Kniberg, Anders Ivarsson http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify

Page 24: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products
Page 25: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

25

http://commons.wikimedia.org/wiki/File:Pears_%26_Apples.jpg

Page 26: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

All Software is not the Same

Custom Hardware + Firmware

OS Extensions (e.g. Protocols, Scalability, Security etc.)

Device Drivers

Domain General

Domain Specific

Application Specific

Features

Page 27: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Low Architectural Impact

Custom Hardware + Firmware

OS Extensions (e.g. Protocols, Scalability, Security etc.)

Device Drivers

Domain General

Domain Specific

Application Specific

Features

Page 28: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

High Architectural Impact

Custom Hardware + Firmware

OS Extensions (e.g. Protocols, Scalability, Security etc.)

Device Drivers

Domain General

Domain Specific

Application Specific

Features

CodeImpact

Page 29: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

High Architectural Impact

Custom Hardware + Firmware

OS Extensions (e.g. Protocols, Scalability, Security etc.)

Device Drivers

Domain General

Domain Specific

Application Specific

Features

Test Impact

Page 30: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Handling the Differences

• Low Architecural Impact– Single Team with end-

to-end ownership

• High Architectural Impact– Many teams– PO team– Anatomy to support vision

and rolling planning– May require pure test teams– Traps:

• Planning too much upfront• Locking down the plan• Disempowering the teams

30

Page 31: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

31http://centrim.mis.brighton.ac.uk/events/irnop-2007/papers-1/Jarkvik%20et%20al.pdf

Page 32: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

http://commons.wikimedia.org/wiki/File:Fugle,_%C3%B8rns%C3%B8_073.jpg32

Self-organization

Page 33: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

33

Why do we want Self-organizing Teams?

Page 34: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

34

A team is a group of people with complementary talents and skills, aligned to a common objective.

Page 35: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

35

It is a Powerful Management Strategy

• End-to-end ownership Motivation Higher quality results

• Local decision making Adaptability Results more fit for purpose

• No hand-overs Reduced time-to-market

http://commons.wikimedia.org/wiki/File:Tic_tac_toe.svg

Page 36: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

36

Typical Advice on Self-organization

• Don’t assign roles• Don’t assign leadership• Don’t assign tasks• Don’t say how

http://commons.wikimedia.org/wiki/File:Stop_hand_nuvola_alternate.svg

Page 37: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

37

Foundations

Self-organization

People

Page 38: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

38

Människor

Självorganisation

Foundations

Objectives Knowledge/Learning Communication/Feedback Way-of-working/Decision making High standards & expectations

Page 39: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

39

Foundations

Självorganisation

People

Motivated individuals Group development

Page 40: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

40

Motivated Individuals

Autonomy

Competence

Relatedness

Self-Determination

Theory

Self-Determination Theory, Deci and Ryan 

Page 41: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

41

Susan Wheelan, Integrated Model of Group Development

Group Development

Dependencyand

Inclusion

Counter-dependency

andFight

Trustand

StructureWork Break up

Child Teenager Young Adult Adult Retirement

Page 42: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

42

Grunder

Människor

Self-organization

Values Results Balance

Page 43: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

43

Committment

Trust

Openness

Respect

Courage

Communication

Feedback Simplicity

Honesty Transparency

Authenticity

Accountability

Page 44: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

44

Balance

Permission to failSpecialisation

LearningCentralization

ConsensusRisk/Opportunity

PlanningAnalysis

CreativityFun

Expect successGeneralisationDeliveryDecentralizationQuick/Good decisionsPrecisionImprovisationActionQuality

Boring

Page 45: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

45

GUT of Self-organization

Values Results Balance

Motivated Individuals Groupdevelopment

Objectives Knowledge/Learning Communication/Feedback Way-of-working/Decision making High standards/Expectations

Page 46: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Summary

• Focus on end-to-end flow• Focus on product evolution rather than

running projects• Distinguish functional enhancements from

architectural evolution• Foster self-organization consciously

46

Page 47: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

47

Frågor på det?

http://commons.wikimedia.org/wiki/File:Ostrich2010_2.jpg

Page 48: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Selected References• Creating Effective Teams (Wheelan) - http://

www.amazon.com/Creating-Effective-Teams-Members-Leaders/dp/1452217076/ref=sr_1_1?s=books&ie=UTF8&qid=1362513243&sr=1-1&keywords=susan+wheelan

• Agile Software Requirements (Leffingwell) - http://www.amazon.com/Agile-Software-Requirements-Enterprise-Development/dp/0321635841/ref=sr_1_1?s=books&ie=UTF8&qid=1362513353&sr=1-1&keywords=leffingwell

• Drive (Pink) - http://www.amazon.com/Drive-Surprising-Truth-About-Motivates/dp/1594484805/ref=sr_1_2?s=books&ie=UTF8&qid=1362513408&sr=1-2&keywords=dan+pink

• Corps Business (Freedman) - http://www.amazon.com/Corps-Business-Management-Principles-Marines/dp/0066619793/ref=sr_1_1?s=books&ie=UTF8&qid=1362513452&sr=1-1&keywords=corps+business+the+30+management+principles+of+the+u.s.+marines

• The Principles of Product Development Flow (Reinertsen) - http://www.amazon.com/Principles-Product-Development-Flow-Generation/dp/1935401009/ref=sr_1_1?s=books&ie=UTF8&qid=1362513506&sr=1-1&keywords=reinertsen

• Scaling Lean & Agile Development (Larman) - http://www.amazon.com/Scaling-Lean-Agile-Development-Organizational/dp/0321480961/ref=sr_1_1?s=books&ie=UTF8&qid=1362513556&sr=1-1&keywords=larman+vodde

• The System Anatomy (Taxén ed.) - http://www.amazon.com/System-Anatomy-Lars-Taxen/dp/9144070748/ref=sr_1_3?s=books&ie=UTF8&qid=1362513689&sr=1-3&keywords=lars+taxen

• The Essence of Software Engineering (Jacobson, Ng, McMahon, Spence, Lidman) - http://www.amazon.com/The-Essence-Software-Engineering-Applying/dp/0321885953

Page 49: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Thanks!

Svante Lidman, Sr Productivity [email protected]@svante_lidmanwww.slideshare.net/SvanteLidman

Page 50: My talk at PMI Sweden Congress 2013 on Agile and Large Software Products

Licensing of this Presentation

50

The artwork in this presentation is licensed under the terms defined by each respective source as indicated on each respective slide. If no source is given, then the artwork is in the public domain.

Trademarks and books, depicted in the presentation are owned by the respective tradmark owner and are only included for reference purposes and is not in any way an endorsement of the presentation contents.

If you make use of this material in whole or part, you should clearly state the source.

All original art work and the presentation as such is is licensed underCreative Commons Attribution-Share Alike 3.0 Unported license.See: http://creativecommons.org/licenses/by-sa/3.0/deed.en