Ευέλικτη ανάπτυξη λογισμικού

Click here to load reader

  • date post

    30-Jul-2015
  • Category

    Technology

  • view

    206
  • download

    2

Embed Size (px)

Transcript of Ευέλικτη ανάπτυξη λογισμικού

1. Agile Software Development / 17 2014 2. 1.Agile 2.Scrum 3. 4. 3. 3 1. (transparency) 2. (inspection) 3. (adaptation) 4. Waterfall 1. 2. (requirements) 3. 5. Agile manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 6. Agile manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive documentation 3.Customer collaboration over contract negotiation 4.Responding to change over following a plan 7. Agile manifesto That is, while there is value in the items on the right, we value the items on the left more. 8. Agile principles 1. 2. 3. business 9. Agile principles 1. . 2. ' 10. Agile principles 1. 2. . 3. 4. , 11. Agile principles 1. , - 2. 12. Project contraints 13. Scrum 1.A wrapper for existing engineering practises 2.A way to maximise productivity 3.A way to improve communications and maximise co-operation 4. 1998, 2001 5. : The new new product development game, Takeuchi & Nonaka, 1986. 14. 1.XP - 5 values / 14 principles / 12 primary practises / 11 corollary practises 2.Lean - 7 principles / 22 thinking tools 3.Scrum - 5 values / 3 roles / 5 activities / 3 essential artifacts 4.Agile Unified Process - 6 principles / 7 disciplines / 4 lifecycle phases / 14 roles / 8 minimum deliverables / 4 guidance pieces 5.DSDM - 8 principles / 5 lifecycle phases / 12 roles / 17 work products / 5 key techniques 15. Scrum , 1. how-to 2. 3. 4. 5. 16. Scrum 1.Activities -Sprint planning meeting -Daily scrum meeting (daily standup) / Sprint review (sprint demo) / Sprint retrospective -Product backlog refinement 2.Essential artefacts -Product backlog / sprint backlog / product increment 3.Scrum roles -Product owner / scrum master / developer team 17. Product backlog 1. PO stakeholders 2. PO 3. 4. Product backlog refinement 18. Sprint planning 1. (workshop) Sprint 2. product backlog 3. PO 4. Sprint 5.H Sprint 6. Sprint backlog 19. Sprint backlog 1. Sprint (the level of understanding) 2. , 3. 4. 20. Sprint 1. Sprints - sprint 2. - 3. potential shippable product - 4. 2 4 21. Stories 1. (, ) 2. ( ) 3. 4. 5. - - - , sprint 6. PO 22. Stories vs use cases 1. 2.Use case ( ) 3. 4. -Functional requirements ( use cases) -Non-functional requirements -Non-software features (documentation, development environment set-up, ) 5. use cases . 23. Multi-level planning Release plan Sprint Plan Daily Plan 3 to 6 months 2 to 4 weeks Daily 24. Planning pyramid 1.Sprint - - sprint (1-5 ) - (estimate) (effort) 2.Release - 3.Project - (epics - ) 25. Product backlog 1. 2. 3. 4. PO 5. 6. 26. Product backlog refinement 1. - product backlog - - - - - 27. Development Team 1.-, , 2.7 2 ( ) 3. (face to face) 4. 5. 6. demo PO stakeholders 7. , , Sprint Goal 28. - ScrumMaster 1. Scrum 2. , , 3. 4. 5. Scrum -Daily scrum meetings / sprint reviews / planning meetings 29. Product Owner 1. 2. product backlog 3. Sprint 4. 5. , , 6. product backlog 7. 30. Estimating () 1.Ideal days - - -50% 80% - - 2.Story points - 2 - 2 - - Sprint - - 31. Velocity () 1. Sprint 2. , 3. Sprint 4. ( ) 32. 1. 33. Daily Scrum 1. 2. standup 3. 4. 5.O PO , SM DT 34. Burndown chart 35. Sprint review 1.1 sprint. 2. 3. PO, SM, DT stakeholders 4. 5. shippable product. 36. Sprint retrospective 1.2 sprint. 2. , 3. scrum 4. SM 37. 1.Scrum but 2.Scrum for development / Waterfall for management 3.Inconsistent scrum implementations 38. 1. 2. scrum 3. 4. 39. Agile Software Development / 17 2014