Introduction to Agile and SCRUm

Thursday 19 March 2009

Implementing SCRUM Responding to change Training & Education Thursday 19 March 2009

Objectives Thursday 19 March 2009

Building a house Thursday 19 March 2009

Some history Thursday 19 March 2009

Software Engineering Thursday 19 March 2009

The people who build this Thursday 19 March 2009

NASA’s Defect Density Industry NASA 5 3.75 2.5 1.25 0 Bugs/ KLOC Thursday 19 March 2009

NASA’s Defect Density Industry NASA 5 3.75 2.5 1.25 0 Bugs/ KLOC pretty good, right? Thursday 19 March 2009

Another data point... 5 900 3.75 675 2.5 450 225 1.25 0 0 Cost ($/LOC) Bugs/ KLOC Industry NASA Thursday 19 March 2009

heavy method... Thursday 19 March 2009

high risk Thursday 19 March 2009

high cost Thursday 19 March 2009

less ﬂexibility to change Thursday 19 March 2009

Waterfall Thursday 19 March 2009

Requirements Thursday 19 March 2009

Requirements Design Thursday 19 March 2009

Requirements Design Develop Thursday 19 March 2009

Requirements Design Develop Verify Thursday 19 March 2009

Requirements Design Develop Verify Maintain Thursday 19 March 2009

Strengths Thursday 19 March 2009

Weaknesses Thursday 19 March 2009

People make mistakes Thursday 19 March 2009

Pitfalls Thursday 19 March 2009

big Thursday 19 March 2009

Bang big Thursday 19 March 2009

early change Thursday 19 March 2009

late change Thursday 19 March 2009

Change is expensive! Thursday 19 March 2009

Fixed Plans Thursday 19 March 2009

predicting change... Thursday 19 March 2009

is difﬁcult ... Thursday 19 March 2009

without a crystal ball Thursday 19 March 2009

Adversarial Relations Thursday 19 March 2009

and hence... Thursday 19 March 2009

not fun! Thursday 19 March 2009

Introducing Agile Thursday 19 March 2009

An approach Thursday 19 March 2009

given human reality Thursday 19 March 2009

Values Guiding Thursday 19 March 2009

Feedback Thursday 19 March 2009

Communication Thursday 19 March 2009

Courage Thursday 19 March 2009

Simplicity Thursday 19 March 2009

build your manifesto Thursday 19 March 2009

Comprehensive Individuals & Documentation Interactions Working Software Processes & Tools Customer Collaboration Contract Negotiation Following a plan Responding to Change Thursday 19 March 2009

The Agile Manifesto Individuals & Over Processes & Tools Interactions Comprehensive Over Working Software Documentation Customer Contract Over Collaboration Negotiation Responding to Over Following a plan Change Thursday 19 March 2009

Approach Your Thursday 19 March 2009

SCRUM Thursday 19 March 2009

Moving from... Thursday 19 March 2009

Software Delivery Marathon Analysis Design Develop Test Maintain Thursday 19 March 2009

Moving to... Thursday 19 March 2009

Tweak Tweak Sprint Sprint Sprint Analysis Develop Test Analysis Develop Test Analysis Develop Test Simple Design Continuous Integration Build & Deployment Automation Thursday 19 March 2009

Incremental Development Thursday 19 March 2009

Iterative Development Thursday 19 March 2009

once != iteration Thursday 19 March 2009

The Scrum Master Thursday 19 March 2009

Guru NOT Nanny Thursday 19 March 2009

Sprint Planning Thursday 19 March 2009

Typical of a SCRUM Team Thursday 19 March 2009

Typical of a SCRUM Team Yesterday’s Weather Thursday 19 March 2009

Collective ownership Thursday 19 March 2009

My Project Plan Thursday 19 March 2009

QA Complete In QA Dev Complete In Dev Ready for Dev In Analysis Thursday 19 March 2009

Our Card Wall! QA Complete In QA Dev Complete In Dev Ready for Dev In Analysis Thursday 19 March 2009

Burn Up Chart Scope Planned Actual Projected Thursday 19 March 2009

Burn Up Chart Scope Planned Actual Projected 150 112.5 75 37.5 0 I1 I2 I3 I4 I5 I6 I7 I8 I9 I10 I11 I12 I13 Thursday 19 March 2009

Burn Up Chart Scope Planned Actual Projected 150 112.5 75 37.5 0 I1 I2 I3 I4 I5 I6 I7 I8 I9 I10 I11 I12 I13 When we planned to finish Thursday 19 March 2009

Burn Up Chart Scope Planned Actual Projected 150 112.5 75 When we should finish 37.5 0 I1 I2 I3 I4 I5 I6 I7 I8 I9 I10 I11 I12 I13 When we planned to finish Thursday 19 March 2009

Burn Down Chart Planned Actual Projected Thursday 19 March 2009

Burn Down Chart Planned Actual Projected 150 112.5 75 37.5 0 Day1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Thursday 19 March 2009

Burn Down Chart Planned Actual Projected 150 112.5 75 37.5 0 Day1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 When we planned to finish Thursday 19 March 2009

Burn Down Chart Planned Actual Projected 150 112.5 75 When we should finish 37.5 0 Day1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 When we planned to finish Thursday 19 March 2009

Tips for Implementation Thursday 19 March 2009

Analysis Development Management Thursday 19 March 2009

Analysis Thursday 19 March 2009

e een r Gr e nnif Je n& a tellm S rew And the n, ctio ce fun h. pla d-re lace ent rc e h-an -rep tive sea he sam m c age nd sear ch-a e-sensi s t e user n in ha t Ma ensitivity the se do a cas t which nt. If th urned ar ojec Pr re ty t ex es s to fe t ase k any e is dif ensitivi t where nvo re ion -4: C user i the opt twa tch of s s en a ca FR - case ill m cum ed S ve the a st gi h w ven if ne with the do li en Wh are mu App inal earc m, e in e do orig he s ext r w soft lt, t arch te is to b atch t erm. ces by the a u repl fied e defa rch only m arch t Nam se ents By s as the the sea are s: i irem oftw xt spec follow e will of the s Requirements equ r e s t te t lette tes tha ftware that t as n th R ent en x e al te ca so , wh cem o cem indi en the ntical t lace e repla e origin e repla rep th e on, se is id th of th th and hen ent ith arch ent w he case rcase, t e ca acem se th repl pe case. t g a docum tains p the all u upper in Dur n the specification re then the was are and ase, . ext d in all xt i e softw case nt text erc se al t erte te r w ca igin ins , th ppe ll lo e user r e or ter u acem as a lowe e If th must b arac the repl xt w in all r of ch n al te ed lette text irst • rigin e insert first ust be e he f ase, th eo ad t erc the If th must b m xt h here text w al te cters lo well. e (w ement xt • igin ara te cas lac s e or se a rted nce e rep h If th of the c t this ca inse ente as s then th d be t c • res t refle l xt w ), shou r. al te rcase mus text rigin s uppe e case. e ent the us nts, eo acem by eme i If th word sentenc repl ecified quir each rted in e , the as sp • ce r ases man inse er c e that w rfor the th pe asy all o he cas h as w e itions In g t (suc e ho ond usin clud tion • are c enta s in pected rch ents tic nts ea plem teris n unex quirem 8: S or im e UC- ac char al re irem whe sign hese ehaves unction . e de them u k. T it b th eq f ying must or s on non al R ill w l t ntif are ces wel . (The ”.) rain eren qua re w onst ion ow e s Ref ftwa , and h system ttribute e by e softw disk, th se c . nct so on po l the ble it is out the uality a is d hich th se on ples of s im raints) nfu wel elia ent nst s , thi ts w ba ab exam q irem data No ften how are cts co r n requ design e. O sureme ize of a rted are out es, how se aspe “softw nal ibl ab r oss c mea s t tio rds or tion t execu fine the ents” o m s suppo lity func as p imu qua ecta a ifi s Non y stand exp uickly i ents de equirem isely e spec he max nt user and ments prec rovid licit ance quire lit ,t rre r q m qua imp , how require avioral d as task ncu orm p e ave fine hould form a r of co r. perf ional r se h l rs h e -be ou na be d ents s o per e mbe ehavio f th funct Use are is t functio as “non ould irem all o as e nu its b et on ts sh w t tak d th soft The n erred to fine qu te e men nal re it mus ble, an chang o de templa . f ht ire e aris times re requ functio econds e availa t do not oug same , en the nal e n s som ents b ent: t bu e no ctio r of ust nfun ble, th numbe stem m plemen irem an use quirem equ ts c no lace i e The e poss ximum ay a sy lr lr m ust i ona rep ona en kly nd- ncti quirem nfuncti re m her he ma rd quic -a pe a fu W re. urs he softw arch non nal re f a no rch .T ftwa t a o se le mee er of h hat t a se ultip functio mple o for e so MB m ints g th rfor t in m Non b num rements xa a 3 ed usin stra t pe onta an e mus con ill c ftware. shows void on lac ui nce req e ep ill a ed atur nw be r ms orm rma e so e ctio tabl rs w e fe perf ms to der 500 at erfo is se s of th owing , use plac lace ch ter ke un 2000 7: P Th ute -re gh l u d NF- fol -rep sear eno h-an b attri e). The ta fast -and ows earc ust r not arch haracte term m t Wind he s ov h is se (ab T sof tive ty 30-c search c sear icro ensi If a -ins th twen aracter ning M ame ase N run i h A c ent w nt 30-c y mar III Sum cum iffere entium le do a d ona zP Rati ts with 700mh d. men ire 4! a u a on CPU lo Req 50% ! .com ene re n-g lma stel ww. ://w http Thursday 19 March 2009

User Stories ole aR As ess roc oP nt t wa I oal at G th So Thursday 19 March 2009

A useful resource Thursday 19 March 2009

] Thursday 19 March 2009

Lo/Mid Fi Prototypes Thursday 19 March 2009

Development Thursday 19 March 2009

Testing Thursday 19 March 2009

Unit Tests Thursday 19 March 2009

Test Automation Thursday 19 March 2009

Developers Thursday 19 March 2009

Solo Coding Thursday 19 March 2009

Pairing Thursday 19 March 2009

Mentorship Pairing Thursday 19 March 2009

Continuous Integration Thursday 19 March 2009

Management Thursday 19 March 2009

Story Wall Thursday 19 March 2009

Self Organizing Team Thursday 19 March 2009

Standup Meeting Thursday 19 March 2009

Big, Visible Charts Thursday 19 March 2009

Retrospectives Thursday 19 March 2009

Questions? Thursday 19 March 2009

Thank You Thursday 19 March 2009

Introduction to Agile and SCRUm

0 comments

Notes on slide 1

Favorites, Groups & Events