Agile Injection Varberg 2011-04-01
This work by Fredrik Wendt is licensed under a  Creative Commons  Attribution-NonCommercial-ShareAlike  3.0 Unported Licen...
Outline <ul><li>Agile Manifesto
Scrum
Extreme Programming
Software Craftmanship </li></ul><ul><li>Parprogrammering
Testdriven utveckling
Retrospective
Systemförvaltning </li></ul>
Fredrik & Janne
Agile
Mythical Man Month <ul><li>”Adding manpower to a late project makes it later.”
Surgical Team
The Architect
Implementers
Growing software – not building?
One always has, at every stage ... a working system </li></ul>
Waterfail
Pragmatic Programmer <ul><li>Fight software rot
Test ruthlessly
Broken Window
Reflect and practice
Automation </li></ul>
Ken Schwaber <ul><li>1990s + Jeff Sutherland
Appendix A
Återkom </li></ul>
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come ...
Agile Manifesto Individuals and interactions Working software Customer collaboration Responding to change
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Continuous Delivery Our highest priority is  to satisfy the customer through  early and continuous delivery of  valuable  ...
Changing Requirements <ul>Welcome changing requirements ,  even late in development.  Agile processes harness change  for ...
Working Software <ul>Deliver working software frequently ,  from a couple of weeks  to a couple of months,  with a prefere...
Upcoming SlideShare
Loading in …5
×

Agile Injection, Varberg

463 views
383 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • out of reach: * too hard to setup * Singletons * Interfaces without proper classes
  • Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
  • XP: Customer ON SITE
  • Stubb with verification method
  • Stubb with verification method
  • Agile Injection, Varberg

    1. 1. Agile Injection Varberg 2011-04-01
    2. 2. This work by Fredrik Wendt is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License http://creativecommons.org/licenses/by-nc-sa/3.0/
    3. 3. Outline <ul><li>Agile Manifesto
    4. 4. Scrum
    5. 5. Extreme Programming
    6. 6. Software Craftmanship </li></ul><ul><li>Parprogrammering
    7. 7. Testdriven utveckling
    8. 8. Retrospective
    9. 9. Systemförvaltning </li></ul>
    10. 10. Fredrik & Janne
    11. 11. Agile
    12. 12. Mythical Man Month <ul><li>”Adding manpower to a late project makes it later.”
    13. 13. Surgical Team
    14. 14. The Architect
    15. 15. Implementers
    16. 16. Growing software – not building?
    17. 17. One always has, at every stage ... a working system </li></ul>
    18. 18. Waterfail
    19. 19. Pragmatic Programmer <ul><li>Fight software rot
    20. 20. Test ruthlessly
    21. 21. Broken Window
    22. 22. Reflect and practice
    23. 23. Automation </li></ul>
    24. 24. Ken Schwaber <ul><li>1990s + Jeff Sutherland
    25. 25. Appendix A
    26. 26. Återkom </li></ul>
    27. 27. We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
    28. 28. Agile Manifesto Individuals and interactions Working software Customer collaboration Responding to change
    29. 29. Individuals and interactions over processes and tools
    30. 30. Working software over comprehensive documentation
    31. 31. Customer collaboration over contract negotiation
    32. 32. Responding to change over following a plan
    33. 33. Continuous Delivery Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
    34. 34. Changing Requirements <ul>Welcome changing requirements , even late in development. Agile processes harness change for the customer's competitive advantage. </ul>
    35. 35. Working Software <ul>Deliver working software frequently , from a couple of weeks to a couple of months, with a preference to the shorter timescale. </ul>
    36. 36. Biz & Dev Interaction <ul>Business people and developers must work together daily throughout the project. </ul>
    37. 37. Motivated Individuals <ul>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. </ul>
    38. 38. Efficient Communication <ul>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. </ul>
    39. 39. What is Progress? <ul>Working software is the primary measure of progress . </ul>
    40. 40. Sustainable Development <ul>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. </ul>
    41. 41. No Technical Debt <ul>Continuous attention to technical excellence and good design enhances agility. </ul>
    42. 42. Do The Right Things, Only <ul>Simplicity – the art of maximizing the amount of work not done – is essential. </ul>
    43. 43. Self-organizing Teams The best architectures, requirements, and designs emerge from self-organizing teams.
    44. 44. Self-organizing Teams At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
    45. 45. Vad hände sen?
    46. 46. Scrum <ul><li>Product Owner
    47. 47. Team
    48. 48. Scrum Master
    49. 49. Product Backlog, Items
    50. 50. Sprint Backlog, Tasks </li></ul><ul><li>Sprint planning
    51. 51. Daily Standup
    52. 52. Sprint Review (demo)
    53. 53. Sprint Retrospective
    54. 54. Definition of Done
    55. 55. Impediments
    56. 56. Backlog grooming </li></ul>
    57. 58. XP <ul><li>Rules on Planning, Managing, Designing, Coding, Testing
    58. 59. Customer always available
    59. 60. Write code to standards
    60. 61. Code the unit test first
    61. 62. Pair program prod.code
    62. 63. Integrate often
    63. 64. Collective ownership </li></ul>
    64. 66. Vad hände sen?
    65. 68. TDD & Coding Dojo <ul><li>ttd-introduction-alt.odp </li></ul>

    ×