Introduktion til agil udvikling

• 1. Introduktion til agil udvikling Bent JensenBestBrains apsCopyright 2011, BestBrains

2. Hvorfor? Agil udvikling er blevet mainstreamMen Agil udvikling er ikke letMen Agil udvikling er svrt at komme udenomCopyright 2011, BestBrains 3. Hvad kan man forvente?ForudsigelighedKontrolTillidArbejdsgldeOverskudInnovationCopyright 2011, BestBrains 4. Copyright 2011, BestBrains 5. Copyright 2011, BestBrains 6. 3 METAFORERCopyright 2011, BestBrains 7. Copyright 2011, BestBrains 8. Copyright 2011, BestBrains 9. Copyright 2011, BestBrains 10. 7 VINKLERCopyright 2011, BestBrains 11. Historien Ritualer Mennesker Fysik Teknisk fundament Tillid ForandringCopyright 2011, BestBrains 12. HISTORIENCopyright 2011, BestBrains 13. eXtreme Programming explained En vision for en radikalt anderledes mde at fremstille software Scrum Crystal Clear Certified Scrum MastersLean Software DevelopmentCopyright 2011, BestBrains 14. The Agile ManfestoWe are uncovering better ways of developing software bydoing 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 planThat is, while there is value in the items on the right, wevalue the items on the left more.Copyright 2011, BestBrains 15. 12 Principles Our highest priority is to satisfy the customer through early andcontinuous delivery of valuable software. We Welcome changing requirements, even late in development. Agileprocesses harness change for the customers competitive advantage. Deliver working software frequently, from a couple of weeks to a coupleof months, with a preference to the shorter timescale. Business people and developers must work together daily throughoutthe project. Build projects around motivated individuals. Give them the environmentand support they need, and trust them to get the job done. The most efficient and effective method of conveying information to andwithin a development team is face-to-face conversation.Copyright 2011, BestBrains 16. 12 Principles Working software is the primary measure of progress. Agile processes promote sustainable development. Thesponsors, developers, and users should be able to maintain aconstant pace indefinitely. Continuous attention to technical excellence and good designenhances agility. Simplicity--the art of maximizing the amount. of work not done--is essential. The best architectures, requirements, and designs emerge fromself-organizing teams. At regular intervals, the team reflects on how to become moreeffective, then tunes and adjusts its behavior accordingly.Copyright 2011, BestBrains 17. RITUALERCopyright 2011, BestBrains 18. Artefakter:Ritualer:Produkt backlogRelease planlgningSprint backlog Sprint planlgningBurn downdiagrammer Scrum Estimering Daglige mder Demoer RetrospektiverRoller: Team (Udviklere + QA + UX...) Scrum master Product ownerCopyright 2011, BestBrains 19. MENNESKERCopyright 2011, BestBrains 20. MenneskerCopyright 2011, BestBrains 21. Dannelse af teamCopyright 2011, BestBrains 22. FYSIKCopyright 2011, BestBrains 23. Projekt StartPlanlagt frdiggrelse M1 M2tidCopyright 2011, BestBrains 24. Projekt Start Planlagt levering M1 M2TidCopyright 2011, BestBrains 25. Projekt Start Planlagt levering M1 M2TidCopyright 2011, BestBrains 26. Projekt Start Planlagt levering M1 M2TidCopyright 2011, BestBrains 27. Projekt Start Planlagt levering TidCopyright 2011, BestBrains 28. KerFlowBuffereBatchesCopyright 2011, BestBrains 29. TEKNISK FUNDAMENTCopyright 2011, BestBrains 30. Teknisk fundamentDen velsmurte udviklingsmaskineContinuous integrationAutomatiske testGod udviklingspraksisCopyright 2011, BestBrains 31. TILLIDCopyright 2011, BestBrains 32. TillidCopyright 2011, BestBrains 33. FORANDRINGCopyright 2011, BestBrains 34. ForandringCopyright 2011, BestBrains 35. Juridiske udfordringer vedaftaler til agile projekterd. 18.03.13 kl. 17:00-18:30Copyright 2011, BestBrains