The document discusses agile principles in software development, emphasizing the importance of culture, people, and processes over rigid documentation and planning. It highlights the failure rates of traditional projects and the benefits of agile methodologies, such as increased productivity and improved project visibility. The content outlines various agile frameworks, such as Scrum and Kanban, and underscores the necessity of continuous learning and adaptation in a changing environment.

1. AgilePrinciplesAgilePeopleGaetano MazzantiGama-Tech

2. > “Hello, I’m Agile”

3. “and I’m not alone”

4. projectproductAgile is aboutchangeculturepeopleorganization

5. Processesand ToolsComprehensiveDocumentationa recipe for success?Followinga PlanContractNegotiation

6. “all you need is a good process and good tools”“even monkeys could write good software”

7. requirementsdesignimplementationtestingdo you spot any problem?

8. ODYSSEYSOFTWAREAProcesses and ToolsContract NegotiationComprehensive DocumentationFollowing a Plan

9. 31% ofprojectscancelled53% challenged1994 Chaos Report(Standish Group)

10. why projects fail:lack ofuserinputincomplete requirementschanging requirements1994 Chaos Report(Standish Group)

11. 45%offeatures are neverused2002 Chaos Report(Standish Group)

12. software is about learning, continuouslyplanning is guessingestimating is notcommitting

13. AGILEMANIFESTO2OOI:Individuals and InteractionsWorking SoftwareCustomer CollaborationResponding to Changeover Processes and Toolsover Comprehensive Documentationover Contract Negotiationover Following a Plan

14. Agile timelineEdwardDemingtheory ofconstraintscrystalnew new product development1993DSDMleanthinkingcomplexadaptivesystems1996Agile manifesto2001leandevelopment2004queueingtheory

15. “I don’t know what I want,but I know how to get it”Johnny RottenSex Pistols

16. delivervalue in small evolutionarystepsdelay commitment, makedecisionsat the last responsible momentbuild in qualityonlywhatisneeded andonlywhenisneededmakeproject statustransparent and visible,highlightissues and impediments

17. XPrebellious and prescriptive (!)on site customerfrequent small releasessmall colocated teamspair programmingunit tests / TDDrefactoring...

18. flattening the cost of changetraditionalcost of changeAgiletime

19. Scrumused by 58% of Agile adopters2010 State of Agile Development Surveycross-functional teamtimeboxed iterations(sprints)split & prioritize

20. Scrumproductownerstandupmeetingscrummasterproductbacklogsprintbacklogteamsprintdeliverabledemo & retrospective

21. frequent and repeated success builds trust and motivationmanagercoachservant guidance provides feedbackenable excellenceconnects the team to the businessteamtrustedrespectedsupportedwork autonomouslymakes allday-to-day decisions{

22. burndown chartinstantfeedbackstory pointsdelaydays

23. lean & agilevaluewastepullflowcadencekaizenrespectfor people

24. Kanban inproduct developmentvisualizemeasureoptimize}flowpulllimit WIP (work in process)

26. visualize flowbacklogto doin progressdone

27. visualizeflowlimit WIP (work in process)measure and optimizeflowexplicit policies(limit WIP, pull, definition of ”done”, etc) ->project and process trasparencyWIPthroughputcycle time =backlogto doin progresstestdone232cycle timelead timeslide credit: H.Knibergwww.crisp.se

28. pullin progressreadybacklogto dodone231

29. WIP excessslide inspired by Claudio Perrone

30. WIP limit slide inspired by Claudio Perrone

31. no WIP limit -> queue!in progressreadybacklogto dodone23

32. stuck!in progressreadybacklogto dodone231

33. up to the teamin progressreadybacklogto dodone231

34. on teams, againperformingcollaborativesupportinggroupa highlyhelpslearning fromeveryoneeach otherthe commitmentthe processthe deliveryeveryoneowns

35. cumulative flow diagrambacklogWIPto docycle timein progressWIPstory pointscycle timethroughputWIPdonedays

36. Chaos Report 2009cancelledprojectswere31%24%were53%challengedprojects44%

37. concerns about Agile adoption36%loss of management controlbarriers to furtherAgile adoptionability to change organizational culture51%2010 State of Agile Development Survey Results

38. benefits from Agile implementation87%manage changing priorities74%increase productivity70%accelerate time to market66%enhance product quality77%improve project visibility2010 State of Agile Development Survey Results

39. Agile encourages/favorschangeany other methodologysupporting this?

40. changeis the only constant

42. Gaetano MazzantiGama-Techinfo@gama-tech.netphoto credits:Flickr, iPhotostock, life.com