More Related Content
Similar to Agile development introduction
Agile development introduction
- 1. AgileDevelopmentStarting at thebasicsArne Vandamme
- 2. AgileManifestoHowitstarted…In 200117 softwaredevelopersdiscussedlightweightdevelopmentmethodsand published the“ManifestoforAgile Software Development”2
- 3. AgileManifestoIndividuals and interactionsover processes and tools3
- 4. AgileManifestoIndividuals and interactionsover processes and toolsWorking software over comprehensive documentation4
- 5. AgileManifestoIndividuals and interactionsover processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiation5
- 6. AgileManifestoIndividuals and interactionsover processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan6
- 7. Agilemanifesto: underlyingprinciplesCustomer satisfactionby rapid delivery of useful softwareWelcome changing requirements, even late in developmentWorking software is delivered frequently (weeks rather than months)Working software is the principal measure of progressSustainable development, able to maintain a constant paceClose, daily cooperation between businesspeople and developersFace-to-face conversation is the best form of communication (co-location)Projects are built around motivated individuals, who should be trustedContinuous attention to technical excellence and good designSimplicitySelf-organizing teamsRegular adaptation to changing circumstances7
- 8. Typicallyagile?Smallincrementswith minimal planningVerylittlelong-termplanningAdaptive PredictiveIterationsWaterfallEachiteration is more orless a tinywaterfall…8
- 9.
- 10.
- 11. Mythbusting: planningIn agiledevelopment,planningis not important.11
- 12. Mythbusting: planningIn agiledevelopment,planningis not important.Wrong!12
- 13. Mythbusting: planningIn agiledevelopment,planningis not important.Wrong!Predictive = plan-drivenAdaptive = planning-driven13
- 14. Mythbusting: planningIn agiledevelopment,planningis not important.Wrong!Predictive = plan-drivenAdaptive = planning-drivenContinuous planning!14
- 15. Mythbusting: informalAgilemethods areveryinformal:no procedures, nocommitment…15
- 16. Mythbusting: informalAgilemethods areveryinformal:no procedures, nocommitment…On the contrary!16
- 17. Mythbusting: informalAgilemethods areveryinformal:no procedures, nocommitment…On the contrary!well-definedlightweight steps and proceduresabsolute team commitmentin an iteration17
- 18. IterativedevelopmentIterative is notthe same asincremental.Incremental: addontoIterative: redo/refineA gooditerativeapproach:Deliversbasicstart-to-endfunctionalityas early as possible.And keepsrefiningituntil the end.18
- 19.
- 20. IterativedevelopmentStart-to-endfunctionalityAs early aspossibleKeep refiningKeep changing and improvingquality!Continuously…refactoringtestingintegrating20
- 21. Concept: User StoryStart-to-endfunctionality:Focuson the user/stakeholderfunctionality.Requirements as user story…As a <role>, I want <goal/desire> so that <benefit>21
- 22. Concept: Definition ofDoneWhen is somethingfinished?Traditionally: what are the acceptance criteria?The Definition Of Doneusuallyalsospecifieshow to testthat the item has been delivered.22
- 23. Concept: Test-DrivenDevelopmentFocusingon theuser story and acceptance criteria and lesson the implementation:Test-DrivendevelopmentWrite a test butnot the implementationCheck that the test failsMake the test succeedbywriting the implementation23
- 24.
- 25.
- 26. SCRUM: RolesProduct OwnerRepresentsstakeholdersand business.Prioritizes the backlog.Scrum MasterFacilitates the SCRUM process. Removesimpediments.Is not a team lead.Project TeamCross-functional.26
- 27. SCRUM: A typicalsprintSprint Planning MeetingPO giveswishlistfrom Product BacklogTeam elaboratestasks and estimatesTeam commitson the Sprint BacklogSprint Backlog is fixedduring sprint.27
- 28. SCRUM: A typicalsprintSprint Planning MeetingDaily ScrumEveryday, same time, same placeIn front of the Scrum boardMax 15 minutesOnly PO, SM or Team mayspeak!Each team membersanswers 3 questions:What have youdoneyesterday?What are you planning to do today?Do you have anyproblemspreventingyoufromaccomplishingyour goal?28
- 29. SCRUM: A typicalsprintExample Scrum board29
- 30. SCRUM: A typicalsprintExampleBurndownchart30
- 31. SCRUM: A typicalsprintSprint Planning MeetingDaily ScrumDemo (Sprint Review)Present the completedwork to the stakeholders31
- 32. SCRUM: A typicalsprintSprint Planning MeetingDaily ScrumDemo (Sprint Review)RetrospectiveTeam reflectson the past sprintWhat went wellduring the past sprint?Whatcouldbeimproved in the next sprint?Continuousprocessimprovements!32
- 33.
- 34.
- 35. Kanban is allabout…Creatingvalueas soon as possible.In software: something is typically business valueonlywhenit has been actuallydeployed!2 basicconcepts: 1. Visualize the flow of work2. Limit work in progress35
- 36.
- 37.
- 38. KanbanVisualizing the flow:VisualizebottlenecksLimit WIP in each stage:Avoidtoomuch WIP and notenoughdoneStimulatecollaborationon bottlenecksWorkflow stages betterallowspecialisation.38
- 39. A Kanban dailystandupAsa team:What is likely to go on and off the board todayWhat is likely to move on the boardWhere is trafficstuck and howcan we fixit39
- 40. RoundupMost agiledevelopmentmethodslike SCRUMand Kanbanare lightweightbut do have a clearprocess and set of rules and requirea lot of self-disciplineand maturityof all the team members40