Introduction to Agile
•
0 likes•426 views
This document provides an introduction to agile principles and practices. It discusses that agile values responding to change, continuous delivery, collaboration between teams, and delivering working software frequently through iterative development. It outlines three common agile practices: continuous feedback through testing, test-driven development, and continuous integration. The document emphasizes failing fast and delivering minimum viable products to adapt to changing needs.
More Related Content
What's hot
What's hot (20)
Similar to Introduction to Agile
Similar to Introduction to Agile (20)
Recently uploaded
Recently uploaded (20)
Introduction to Agile
- 1. INTRO TO AGILEintro to agile charlotte chang @pushorpull @glamouracademy
- 2. this presentation will be fast-paced, use obnoxious buzzwords & jargon, and lastly, to the demise of most everyone, contain personal anecdotes.
- 3. a bit about me
- 12. It takes a village to raise a child. - African Proverb
- 13. It takes a village to raise a child. - African Proverb developer
- 14. It takes a village to raise a child. - African Proverb developerpack
- 15. Plain Dealer: Cool Spaces, Aug 2015
- 24. Change is inevitable, growth is optional.
- 26. the best developer fails often
- 31. the best developer fails fast, fails often
- 32. But that’s not how it used to be.
- 34. ● usage is well-defined & doesn’t change ● extremely detailed design ● frozen design & requirements ● 3,000 yrs experience ● failures are really public & fatal
- 35. However, in today's fast moving business environment, a frozen design does not accommodate changes in the business practices.
- 36. 1994-1995 In the United States, we spent over $250 billion each year on IT application development of approximately 175,000 projects. The average cost of a development project for a large company is $2,322,000; for a medium company, it is $1,331,000; and for a small company, it is $434,000. Standish Group, Chaos Report
- 37. Standish Group, Chaos Report The project is completed on-time and on- budget, with all features and functions as initially specified. The project is completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. The project is cancelled at some point during the development cycle.
- 38. Standish Group, Chaos Report The project is completed on-time and on- budget, with all features and functions as initially specified. The project is completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. The project is cancelled at some point during the development cycle. $81 billion
- 39. Standish Group, Chaos Report The project is completed on-time and on- budget, with all features and functions as initially specified. The project is completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. The project is cancelled at some point during the development cycle. $81 billion 189% of original cost
- 43. When we were little... “Think things through.” “Don’t make mistakes.” “Plan ahead.” “Don’t fail.” ...but,
- 50. Up-front thinking only... ● hard to incorporate new ideas ● hard to modify design ● hard to decouple code ● hard to adapt ….doesn’t mean you’re going to get what you want!
- 51. projects need to respond to change often
- 52. February 11-13, 2001 The Agile Alliance (17 people) The Agile movement is not anti-methodology, in fact, many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment.
- 55. early & continuous delivery changing requirements deliver working software frequentlybusiness people & developers work together daily be invested & trust your team face-to-face communication is best working software is how to measure progress sustainable pace technical excellence simple design, simple code continuous feedback self-organising teams
- 56. how?
- 57. 3 common agile best pratices
- 58. 3 common agile best pratices continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery collaboration pair programming three amigos stand-ups visibility story wall personas build radiators burn up/down chart
- 60. continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery
- 61. continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery Test Driven Development (TDD) == Red Green Refactor == Ping Pong
- 63. continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery Test Driven Development (TDD) == Red Green Refactor == Ping Pong User interviews Observation Data analytics Retrospectives
- 67. Went went well Not so well Puzzles us
- 68. continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery Test Driven Development (TDD) == Red Green Refactor == Ping Pong User interviews Observation Data analytics Retrospectives Prototypical data Development environments Lightweight documentation
- 69. Fail fast, fail often
- 70. Fail fast, fail often
- 71. Fail fast, fail often
- 72. continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery Test Driven Development (TDD) == Red Green Refactor == Ping Pong User interviews Observation Data analytics Retrospectives Prototypical data Development environments Lightweight documentation Minimal Viable Product Small requirements
- 73. What is the minimum viable product?
- 74. What is the minimum viable product? lovable
- 75. I have to have_________.
- 76. I have to have_________. Kill your darlings.
- 78. 3 common agile best pratices continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery collaboration pair programming three amigos stand-ups visibility story wall personas build radiators burn up/down chart
- 85. Pair Programming
- 86. Isn’t that paying two people to do one job?
- 87. </>
- 89. couple other thoughts about collaboration
- 90. Kraut, Egido, and Galegher (1990)
- 91. If you want to go fast, go alone. If you want to go far, go together. - African proverb
- 92. even with collaboration, sometimes...
- 93. 3 common agile best pratices continuous feedback Test Driven Development (TDD) Continuous Integration (CI) Feedback Working software Incremental delivery collaboration pair programming three amigos stand-ups visibility story wall personas build radiators burn up/down chart
- 94. visibility story wall personas build radiators burn up/down chart
- 98. Burn up chart Iteration Points Scope line 0 1 2 3 4 5 6 7 8 Velocity
- 99. Burn up chart Iteration Points Scope line 0 1 2 3 4 5 6 7 8 Velocity
- 102. Respond to change