Why Projects Fail_risk review

7/23/2019 Why Projects Fail_risk review

1/20

and what you can do about it

A presentation by Jennifer Greene and Andrew Stellman

Why Projects Fail

Evenifitsnotyourfa

ult!

PhotobyDanTaylor(CCl

icense

)

These are the slides for our Why Projects Failtalk. Weve given it many times, and it always

gets a good response. If youd like us to comeand give it for your group or organization,

contact us at http://www.stellman-greene.com.


2/20

AndrewStellmanstartedprogramminginthe80s,andlostcountofhowmanylanguageshesworkedwith.

Hesledteamsofprogrammers,requirementsanalysts

andprocessengineers.

JenniferGreenesspentthelast20years

orsomanagingdevelopmentandtestingteams.

Jenny and Andrew truly believe that with better development practicesand good programming habits, we can all build better software.

Shescurrentlydoing

consultingandtrainingforagroupwithalarge

(500person)ITteam.

Who we are


3/20

Our books

2008 (1sted)

2010 (2nded)

2005

2007 (1sted)

2009 (2nded)

2010


4/20

WARNING: This is NOT an

academic presentationThe topics we are about to cover maybe deadly serious, but we wont be


5/20

Not all failures are this easy to spot

butsomeprojectsdofail

spectacularly.

TheTacomaNarrowsBridgeprojectfailed

beforethefirst

yardofconcretewaspoured.Therewasnothingwrong

withtheconstruction.

Poordesignandbadlyplannedcostcuttingin

materialsledtoanunfortunateend.

If this video doesnt play, try using a newer version of Acrobat or you can download the video here:http://www.stellman-greene.com/GallopingGertie


6/20

Dont go in the basement!

a lot like cheesy horror movies

This time its different


7/20

What does a failing project look like?

You know youre on a failed project when


8/20

uncomfortable

A show of hands, please

Are there any here?

Sometimes failure seems normal


9/20

Four basic ways projects can fail

Things the boss does

Things the team shouldve done

is

Things the software does (or doesnt do)

Things that could have been caught


10/20

leading ourprojects

Things the boss does

Likeitornot,whenyoureleadingaprojectteamyouretheboss!


11/20

Up close: A Vision & Scope Document keeps everyone on the same page

Vision and Scope document who

what how


12/20

Things the team shouldve done


13/20

Up close: Wideband Delphi keeps estimates honest

http://www.stellman-greene.com/chapter3

The


14/20

Things the software does (or doesnt do)

U l U h l d


15/20

Up close: Use cases can help you avoid requirementsproblems


16/20

not

before

before

Things that could have been caught


17/20

Up close: Dont overlook your acceptance criteria!

more than just user acceptance


18/20

doesnt fail

What you can do about it


19/20

Repeat after me: Practices, practices, practices.

better software

process

concrete goals

specificyour

hurt


20/20

One last quick note from the marketing department

Buythesebooks!

And check out our blog, Building Better Softwarehttp://www.stellman-greene.com/

Thanks for coming! Any questions?

Documents

Why Projects Fail_risk review