Introduktion til agil udvikling

507 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
507
On SlideShare
0
From Embeds
0
Number of Embeds
50
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Introduktion til agil udvikling

  1. 1. Introduktion til agil udvikling Bent Jensen BestBrains apsCopyright 2011, BestBrains
  2. 2. Hvorfor? • Agil udvikling er blevet mainstream Men • Agil udvikling er ikke let Men • Agil udvikling er svært at komme udenomCopyright 2011, BestBrains
  3. 3. Hvad kan man forvente? • Forudsigelighed • Kontrol • Tillid • Arbejdsglæde • Overskud • InnovationCopyright 2011, BestBrains
  4. 4. Copyright 2011, BestBrains
  5. 5. Copyright 2011, BestBrains
  6. 6. 3 METAFORERCopyright 2011, BestBrains
  7. 7. Copyright 2011, BestBrains
  8. 8. Copyright 2011, BestBrains
  9. 9. Copyright 2011, BestBrains
  10. 10. 7 VINKLERCopyright 2011, BestBrains
  11. 11. • Historien • Ritualer • Mennesker • Fysik • Teknisk fundament • Tillid • ForandringCopyright 2011, BestBrains
  12. 12. HISTORIENCopyright 2011, BestBrains
  13. 13. eXtreme Programming explained En vision for en radikalt anderledes måde at fremstille software Scrum Crystal Clear Certified Scrum Masters Lean Software DevelopmentCopyright 2011, BestBrains
  14. 14. The Agile Manfesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.Copyright 2011, BestBrains
  15. 15. 12 Principles • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • We Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.Copyright 2011, BestBrains
  16. 16. 12 Principles • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount. of work not done-- is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.Copyright 2011, BestBrains
  17. 17. RITUALERCopyright 2011, BestBrains
  18. 18. Artefakter: Ritualer: Produkt backlog Release planlægning Sprint backlog Sprint planlægning Burn down diagrammer Scrum Estimering Daglige møder Demoer RetrospektiverRoller: Team (Udviklere + QA + UX...) Scrum master Product ownerCopyright 2011, BestBrains
  19. 19. MENNESKERCopyright 2011, BestBrains
  20. 20. MenneskerCopyright 2011, BestBrains
  21. 21. Dannelse af teamCopyright 2011, BestBrains
  22. 22. FYSIKCopyright 2011, BestBrains
  23. 23. Projekt Start Planlagt færdiggørelse M1 M2 tidCopyright 2011, BestBrains
  24. 24. Projekt Start Planlagt levering M1 M2 TidCopyright 2011, BestBrains
  25. 25. Projekt Start Planlagt levering M1 M2 TidCopyright 2011, BestBrains
  26. 26. Projekt Start Planlagt levering M1 M2 TidCopyright 2011, BestBrains
  27. 27. Projekt Start Planlagt levering TidCopyright 2011, BestBrains
  28. 28. • Køer • Flow • Buffere • BatchesCopyright 2011, BestBrains
  29. 29. TEKNISK FUNDAMENTCopyright 2011, BestBrains
  30. 30. Teknisk fundamentDen velsmurte udviklingsmaskineContinuous integrationAutomatiske testGod udviklingspraksisCopyright 2011, BestBrains
  31. 31. TILLIDCopyright 2011, BestBrains
  32. 32. TillidCopyright 2011, BestBrains
  33. 33. FORANDRINGCopyright 2011, BestBrains
  34. 34. ForandringCopyright 2011, BestBrains
  35. 35. Juridiske udfordringer ved aftaler til agile projekter d. 18.03.13 kl. 17:00-18:30Copyright 2011, BestBrains

×