deweck-dynamics software projects - École Polytechnique

+

-

Copyright 2007Olivier L. de Weck and James M. Lyneis

Dynamics of Software Projects

Prof. Olivier de Weck

[email protected]

Guest Lecture at Ecole Polytechnique

October 5, 2007

10/05/07 2

+

-

Copyright 2007de Weck and Lyneis

Topics

Dynamic project problems

The system dynamics viewpoint

Causes of project dynamics

Application of System Dynamics to Modeling Small to Medium Size Software Projects

10/05/07 3

+

-


Topics





10/05/07 4

+

-


Project Dynamics

What does “dynamic” mean in the context of a project?What are some key measures typically monitored on a project?Sketch “desired” (or planned) and typical actuals for these measures.

10/05/07 5

+

-


Sketch Plan and Actuals for ...

Time

ProjectStaffing

10/05/07 6

+

-



FractionComplete

Time

.5

1

10/05/07 7

+

-



Productivity(Normalised)

Time

1

2

10/05/07 8

+

-


Trouble-free Projects Behave as Planned: Design Labor (Equivalent People)

Simulated Data100.

75.

50.

25.

0.

TIME91 92 93 94 95 96

Disguised resultsfrom an actualsoftware project

Year 1 Year 5Year 4Year 3Year 2 Year 6

10/05/07 9

+

-


Design Progress (Percent Complete)Simulated100.

75.

50.

25.

0.

TIMEYear 1 Year 4Year 3Year 2 Year 5 Year 6

Disguised resultsfrom an actual

software project

10/05/07 10

+

-


Design Labor (Equivalent People)Simulated Data80.

60.

40.

20.

0.

TIME

Disguised results from an actual Ship-building project

Year 1 Year 4Year 3Year 2

10/05/07 11

+

-


Design Progress (Percent Complete)Simulated100.

75.

50.

25.

0.

TIMEYear 1 Year 4Year 3Year 2

Disguised results from an actual Ship-building project

10/05/07 12

+

-


So while some projects are trouble-free, more typically, projects ...

10/05/07 13

+

-


Typical Project “Disasters”

The Channel Tunnel -- original estimate, $3 billion; final cost, $10 billionBoston’s “Big Dig” -- original mid-1980’s estimate, $2.5 billion; latest estimate, $14.5 billion (9/2001)

10/05/07 14

+

-


Microsoft’s next major release of Windows operating system

January 2003: Longhorn will ship in 2004 http://redmondmag.com/news/article.asp?EditorialsID=5674

August 2004: Will Ship late 2006http://arstechnica.com/news.ars/post/20040828-4139.html

Windows Vista (AKA “Longhorn)

10/05/07 15

+

-


FBI’s Virtual Case File

Virtual Case File is would allow agents to share info easilyCongress and others believe VCF is “critical to enabling the FBI and intelligence agencies to ‘connect the dots’ in preventing [terrorist] attacks”InformationWeek Feb 4, 2005

May 2004: Project will be delivered by end of 2004 Feb 2005: Mueller acknowledges he doesn’t know how much it will cost ($170 million already spent) or when it will be deliveredFBI may have to scrap what they’ve done so far and start fresh

InformationWeek Feb 4, 2005 from the Associated Press

10/05/07 16

+

-


Software Projects are Tough

On average software projects overshoot schedule by 50%⅓ of large-scale software projects never complete (cancelled)¾ of all large systems that are completed are operating failures*

Source: Gibbs, W. 1994. “Software’s Chronic Crisis”. Scientific American. September. pp. 86-95

10/05/07 17

+

-


Lamri Survey

http://www.lamri.com/CMMI_Survey_results.pdf

10/05/07 18

+

-


So while some projects are trouble-free, more typically, projects ...

... Surprise us with late requests for additional time or resources... Have schedule and budget overruns... Seem to get stuck at “90%” complete... Result in new products with flaws discovered after release... Hinder learning because of difficulty in comparing the performance of different, “unique” projects

10/05/07 19

+

-


On typical development projects ...Design Labor (Equivalent People)

Simulated Actual

Year

800.

600.

400.

200.

0 0 3 6 9 12 15 18 21

ApproximateOriginal Plan

Disguised results from actual aerospace project

… Staffing experiences an extended tail

10/05/07 20

+

-


Program Staff, Simulated vs. Data (Equivalent Staff)

400.

300.

200.

100.

TIME

0 Year 1 Year 2 Year 3 Year 4 Year 5 Year 6

Simulated Original Plan Actual

Disguised results from actual vehicle project

… Or a second staffing peak

10/05/07 21

+

-


Two software development projects for the same aerospace company experienced dramatically different results

[see next 3 pages; figures show disguised results shifted so that the 2 projects started in the same year]

10/05/07 22

+

-


1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003

150

100

50

0

Program staff (Program A ...)

10/05/07 23

+

-


1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003

150

100

50

0

Program staff (Program B)

10/05/07 24

+

-


1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003

150

100

50

0

Program staff (Program B vs. Program A)

10/05/07 25

+

-


What caused the differences between Program A and Program B?

Differences in work scope?

External Conditions?

Management policies and processes?

And how can a company learn from these differences, and therefore

Bid better?

Plan better?

Manage better?

10/05/07 26

+

-


Progress has been made: Many firms have cut development times in half ...

Source: Smith, Preston G. and Donald G Reinersten, Developing Products in Half the Time (2nd edition), Wiley 1998.

10/05/07 27

+

-


PERT and CPM (Critical Path Method)Waterfall, Spiral, …Emphasis on “soft,” people factorsMicrosoft Project

.. and Learning is not happeningWhy???

Project problems persist in spite of numerous advances in the last 30 years

10/05/07 28

+

-


Topics





10/05/07 29

+

-


Events “Change Occurred,Project behind schedule”

Three ways of looking at a problem --

10/05/07 30

+

-


Events

Patterns of

BehaviorEst. CompletionDate

Add.Resources

“Project behind schedule”


10/05/07 31

+

-


System Structure

EstimatedCompletion

Date

AddResources

BehindSchedule

RemainingWork

Experience Dilution,Quality Problems


10/05/07 32

+

-


Events

Patterns of Behavior

System Structure

Est. CompletionDate

Add.Resources

EstimatedCompletion

AddResources

BehindSchedule

RemainingWork

Experience Dilution,Quality Problems

“Project behind schedule”


10/05/07 33

+

-


The System Dynamics Viewpoint

Events


System Structure

External Factors

10/05/07 34

+

-


The System Dynamics Viewpoint

Events


System Structure

Low

Medium

High

Ability toInfluence

External Factors

10/05/07 35

+

-


Why??

Project performance problems are fundamentally dynamic problems,

but Managers mental models and typical tools (computer models):

Attribute all problems to external factorsView a project statically (no iteration, no feedback)Treat projects as if they were unique

10/05/07 36

+

-


System Dynamics Concepts

Focus on dynamic behaviorSystem structure as cause of that behaviorEmphasis on internal dynamics and how we can change structureA model is an integral part of organizational learning

10/05/07 37

+

-


Examples of Behavior Modes

"Plan"

Growth

ProjectStaffing

Stability

10/05/07 38

+

-


What Causes Dynamics?

All dynamics are driven by –Feedback processesAccumulation processes

10/05/07 39

+

-


The basic element of system structure is the feedback loop...

Chickens

TIME

...This one a “positive,”or reinforcing feedback loop.

+

+

EGGS CHICKENS

Adapted from Professor John Sterman, MIT

10/05/07 40

+

-


Loops of effects interact with one another, making traditional diagnosis quite difficult...

...Such as with this “negative,” or balancing, feedback loop, which may

slow or reverse growth

Chickens

TIME

+

+

EGGS CHICKENS ROADCROSSINGSX

FARMSIZE

-

+

10/05/07 41

+

-


Effects interacting makes traditional diagnosis quite difficult in a business setting as well

PRICE

UNITCOSTS

USAGE

SERVICECAPACITY

SERVICEQUALITY

10/05/07 42

+

-


Accumulation processes involve ...

Stocks or “levels” -- define the state of the system

Flows or “rates” -- define the rate of change in system states

Bank Account Balance

Deposits

(iThink Rate Symbol)

Deposits

(Vensim/DYNAMO Symbol)

10/05/07 43

+

-


Connecting stocks and flows ...

Bank Account Balance

Deposits Withdrawals

“Clouds”represent stocks outside the system boundary

StaffHiring Firing

10/05/07 44

+

-


Interacting positive and negative feedback loops of cause-effect relationships, with stocks, flows, delays, and non-linearities, are capable of generating all observed modes of behavior.

10/05/07 45

+

-


Topics





10/05/07 46

+

-


System dynamics modeling provides a means of ...

... understanding the structure of projects, and how that structure creates behavior;... designing robust projects... learning across projects

10/05/07 47

+

-


But every project is unique ...

Many similarities, some uniquenessWe will discuss the characteristics of different kinds

of projects later in the term.

SD is a framework for assessing dynamic similaritiesBut, there is no “one way”, “right answer”We will discuss heuristics and rules of thumb during

the course.

10/05/07 48

+

-


Examples of Behavior Modes on a Project

ProjectStaffing

Time

TypicalPlan

10/05/07 49

+

-


Examples (continued)

FractionComplete

Time

.5

1

TypicalPlan

10/05/07 50

+

-


Examples (continued)

Productivity(Normalised)

Time

1

2Typical

Plan

10/05/07 51

+

-


The Drivers of Project Dynamics --

The “rework cycle”Feedback effects on productivity and work quality (often “vicious circles”)Knock-on effects between work phasesKnock-on effects between projects

10/05/07 52

+

-


What are typical stocks & flows on a project?

Stocks Flows

10/05/07 53

+

-


The Traditional View of a Program – Task Accomplishment

WORKBEING DONE

PEOPLE PRODUCTIVITY

WORKTO BEDONE

WORKDONE

WORK TO DO STAFF % DONE

TIMETIMETIME

Task Accomplishment

10/05/07 54

+

-


The traditional view, expanded to multiple tasks with logical links ...

... becomes a Critical Path Network

Task A

Task B

Task C

Task D

Task E

Task F Task Z

10/05/07 55

+

-


But traditional approaches fail to consider iteration and rework

WORKBEING DONE

PEOPLE PRODUCTIVITY QUALITY

WORKTO BEDONE

WORKREALLYDONE

REWORK


RWK

TIME TIME TIME

10/05/07 56

+

-


Or Undiscovered Rework

WORKBEING DONE

PEOPLE PRODUCTIVITY QUALITY

KNOWNREWORK

UNDISCOVEREDREWORK

REWORK DISCOVERY

WORKTO BEDONE

WORKREALLYDONE


RWK

UR REALLY

TIME TIME TIME

10/05/07 57

+

-


On typical development projects ...Simulated Actual

Year

800.

600.

400.

200.

0 0 3 6 9 12 15 18 21

ApproximateOriginal Plan

Disguised results from actual aerospace project

… Staffing experiences an extended tail

10/05/07 58

+

-


Caused by the need to accomplish rework

0 3 6 9 12 15 18 21

800.

600.

400.

200.

0

Work Assignments of Staff to...

Original Work

Rework

Total

10/05/07 59

+

-


Program Staff, Simulated vs. Data (Equivalent Staff)

400.

300.

200.

100.

TIME


Simulated Original Plan Actual


… A second staffing peak

On typical development projects ...

10/05/07 60

+

-


Work Assignments of Staff to...

Again caused by the need to execute rework

400.

300.

200.

100.

TIME


Original Work Rework


Rework

Original Work

10/05/07 61

+

-


The Rework CycleKey to Project Dynamics

WORK

BEING DONE

People Productivity Quality

Rework Discovery

WORKTO BEDONE

KNOWNREWORK

UNDISCOVEREDREWORK

WORKREALLYDONE

10/05/07 62

+

-


Why? The Drivers of Project Dynamics --


10/05/07 63

+

-


What drives productivity & quality?

UndiscoveredRework

KnownRework

WorkReally Done

WorkTo Be Done

Progress

Rework Discovery


CustomerChanges

Dynamics are initiated by (1) an infeasible initial plan, or (2) changes adding scope and obsoletingcompleted work ...

Scope Growth

10/05/07 64

+

-



UndiscoveredRework

KnownRework

WorkReally Done

WorkTo Be Done

Progress

Rework Discovery


ApparentProgress

CustomerChanges Schedule

Acceleration

Overtime

Hiring

Scope Growth

… that initiate corrective actions to get the project back

on track...

10/05/07 65

+

-



UndiscoveredRework

KnownRework

WorkReally Done

WorkTo Be Done

Progress

Rework Discovery


ApparentProgress

CustomerChanges Schedule

Acceleration

Out-of-SequenceWork, Worksite

Congestion, CoordinationProblems,

Morale Problems

AverageEmployee Skill

and Quality

Fatigue,Burnout

Overtime

Hiring

Scope Growth

… that create vicious circles that undercut intended effects

10/05/07 66

+

-


A system dynamics model usually represents several phases of work, but is more aggregate than a CPM model

SystemEngineering

Software Codeand Test

HardwareDesign

Hardware Buildand Test

Integrateand Test

SoftwareDesign

10/05/07 67

+

-


Summary: The Drivers of Project Dynamics --


10/05/07 68

+

-


Topics





10/05/07 69

+

-


SM Thesis

A Comparative Study of Iterative Prototyping vs. Waterfall Process Applied To Small and Medium Sized Software Projects

Eduardo Malaga ChocanoMIT System Design and Management ProgramJune 2004

10/05/07 70

+

-


Objectives

1. Identify the main strengths and weaknesses of iterative cycle based models vs. sequential-based models applied to small and medium sized software projects.

2. Measure the impact these features have in the management of projects

3. Understand under which conditions each of these approaches is recommended.

4. Study the new trends in this field and propose recommendations regarding their use.

10/05/07 71

+

-


Waterfall Projects

10/05/07 72

+

-


Spiral Projects

10/05/07 73

+

-


Interviews of Peruvian SW Project Leaders

10/05/07 74

+

-


Characteristics of Successful Projects

10/05/07 75

+

-


Source of Problems

10/05/07 76

+

-


Software Project Model (overview)

10/05/07 77

+

-


Software Project Model (detailed)

Model Parameters

-Number of Tasks-Development Rate-Verification Rate-Flag

-sequential-iterative

-Verification Period-Phase Size Table-Insight per Phase-Insight Development-Verification Accuracy-% dedicated to verify

10/05/07 78

+

-


Results (I) – Speed vs Quality

Speed vs QualityRun with nominal parameters

10/05/07 79

+

-


Results (2) – Task Distribution

10/05/07 80

+

-


Results (II) – Amount of Rework

Iterative Approach causes more relative rework

10/05/07 81

+

-


Conclusioniterative

iterative

10/05/07 82

+

-


SummarySoftware Development Methodology have a significant impact on project success

Iterative Approach:more effective use of developer’s timeshort iterations, minimize idle time waiting for tasks to be reworked

Sequential Approach:programmers wait idle while testing is underwayless rework necessary if insight can be developed fastless variance of outcome

Hybrid Approaches existFinal Note – large difference between software for business applications and safety-critical real-time embedded software

business software – very suitable to spiral approachreal time embedded software – rather sequential

deweck-dynamics software projects - École Polytechnique

Documents