Embed Size (px)
Citation preview
ABOUT ME
WHAT IS THIS TALK ABOUT?
AGENDAWaterfallScrumAgile
Waterfall model
Product requirements documentProduct requirements document
Software architectureSoftware architecture
Implementation
Design
Requirements
Maintenance
Verification
SoftwareSoftware
WATERFALL PROBLEMSNo working software is produced until late.High amounts of risk and uncertainty.It is difficult to measure progress within stages.Cannot accommodate changing requirements.Integration is done as a "big-bang. at the very end, whichdoesn't allow identifying any technological or businessbottleneck or challenges early.
SCRUM
XP - EXTREMME PROGRAMMING
MANIFESTO FOR AGILE SOFTWARE DEVELOPMENTWe are uncovering better ways of developing software by
doing it and helping others do it. Through this work we havecome to value:
Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
That is, while there is value in the items on the right, we valuethe items on the left more.
"Agile is ordering tapas until you're full, notordering a 10-course meal" - Neil Killick
"Build projects around motivated individuals.Give them the environment and support they
need, and trust them to get the job done." -5th Principle from Agile Manifesto
The necessity of estimates is the lack of trust
"Customer collaboration over contractnegotiation" - Agile Manifesto
"Until each specific feature is understood indetail, it’s impossible to estimate the cost of a
software project accurately." - McConnell
That's not very Agile.
date estimated 2011 - terminated on 2015
cost estimated 288 millions - final cost 506 millions
WHY ESTIMATE?
PREDICTION
"Working software is the primary measure ofprogress." - 7th Principle from Agile Manifesto
PRIORITISATIONFocus on value not in cost
ANALYSIS & UNDERSTANDINGDo it but don't make magic numbers from it
THE NATURE OF SOFTWARE DEVELOPMENTOrganising By FeaturePlanning Feature by FeatureBuilding the product, feature by featureSlice features thinlyBuild quality in every day
SLICING HEURISTIC“A user story ready to be worked on must
have only one acceptance test." - Neil Killick
