0
Introduction to Agile<br />2011-07-15<br />Delivering Customer Value with Speed, Economy & Quality<br />2011-07-15<br />
Please mute <br />Your cell!<br />
Agenda<br />1<br />2<br />3<br />F&A  Discussion<br />Why  Agile<br />What  IsAgile<br />
hy<br />w<br />Agile<br />
Increased Consumer Expectations<br />As consumers today we want and expect innovative products: faster, cheaper and with b...
Increased Work Pressure<br />As knowledge workers, our business tools have improved our capability to be productive, raisi...
Misaligned Expectations<br />However,<br />Instead of this…<br />Productivity driving Customer value<br />Consumer Expecta...
Let’s try Agile!<br />
hat<br />w<br />Is Agile<br />
History of Agile & Lean<br />History & Influences<br />Early 1900s<br /><ul><li>Walter Shewhart: Plan-Do-Study-Act, SPC</l...
Toyota: Toyota Production System (TPS)
Peter Drucker: Knowledge Worker</li></ul>Late 1900s<br /><ul><li>Womack and Jones: Lean Thinking
Eli Goldratt: Theory of Constraints
Tom Gilb: Evo
The Toyota Way</li></ul>Evolution<br />Early 1990s<br /><ul><li>Crystal Methods
Lean Software Development
Dynamic Software Development Method (DSDM)</li></ul>Mid 1990s<br /><ul><li>Feature Driven Development (FDD)
eXtreme Programming (XP)
Adaptive Software Development</li></ul>2001: Manifesto for Agile Software Development <br /><ul><li>http://www.agilemanife...
http://agilemanifesto.org/iso/zhchs/principles.html</li></li></ul><li>Manifesto Values<br />We are uncovering better ways ...
individuals<br />interactions<br />and<br />Individuals and interactions <br />over processes and tools <br />processes<br...
working<br />software<br />Working software <br />over comprehensive documentation<br />comprehensive<br />documentation<b...
customer<br />collaboration<br />Customer collaboration over contract negotiation<br />contract<br />negotiation<br />
responding<br />change<br />to<br />Responding to change<br />over following a plan<br />following<br />plan<br />a<br />
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuab...
Upcoming SlideShare
Loading in...5
×

Introduction to agile

258

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
258
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Introduction to agile"

  1. 1. Introduction to Agile<br />2011-07-15<br />Delivering Customer Value with Speed, Economy & Quality<br />2011-07-15<br />
  2. 2. Please mute <br />Your cell!<br />
  3. 3.
  4. 4.
  5. 5. Agenda<br />1<br />2<br />3<br />F&A Discussion<br />Why Agile<br />What IsAgile<br />
  6. 6. hy<br />w<br />Agile<br />
  7. 7. Increased Consumer Expectations<br />As consumers today we want and expect innovative products: faster, cheaper and with better quality than those we’ve seen in the past.<br />Consumer Expectations<br />
  8. 8. Increased Work Pressure<br />As knowledge workers, our business tools have improved our capability to be productive, raising work expectations.<br />BusinessExpectations<br />
  9. 9. Misaligned Expectations<br />However,<br />Instead of this…<br />Productivity driving Customer value<br />Consumer Expectations<br />Business Expectations<br />Consumer Expectations<br />Business Expectations<br />We usually get this…<br />Misalignment of Value definitions<br />Consumer Expectations<br />Or all too often, this.<br />Orthogonal opposition to Customer Value<br />Business Expectations<br />
  10. 10. Let’s try Agile!<br />
  11. 11. hat<br />w<br />Is Agile<br />
  12. 12.
  13. 13. History of Agile & Lean<br />History & Influences<br />Early 1900s<br /><ul><li>Walter Shewhart: Plan-Do-Study-Act, SPC</li></ul>Mid 1900s<br /><ul><li>Edward Deming: SPC, TQM
  14. 14. Toyota: Toyota Production System (TPS)
  15. 15. Peter Drucker: Knowledge Worker</li></ul>Late 1900s<br /><ul><li>Womack and Jones: Lean Thinking
  16. 16. Eli Goldratt: Theory of Constraints
  17. 17. Tom Gilb: Evo
  18. 18. The Toyota Way</li></ul>Evolution<br />Early 1990s<br /><ul><li>Crystal Methods
  19. 19. Lean Software Development
  20. 20. Dynamic Software Development Method (DSDM)</li></ul>Mid 1990s<br /><ul><li>Feature Driven Development (FDD)
  21. 21. eXtreme Programming (XP)
  22. 22. Adaptive Software Development</li></ul>2001: Manifesto for Agile Software Development <br /><ul><li>http://www.agilemanifesto.org</li></ul>2005: Declaration of Interdependence <br /><ul><li>http://www.pmdoi.org/</li></ul>2011: Agile Manifesto (Simplified Chinese)<br /><ul><li>http://agilemanifesto.org/iso/zhchs/
  23. 23. http://agilemanifesto.org/iso/zhchs/principles.html</li></li></ul><li>Manifesto Values<br />We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value<br />Individuals and interactions over processes and tools <br />Working software over comprehensive documentation <br />Customer collaboration over contract negotiation <br />Responding to change over following a plan<br /> That is, while there is value in the items on the right, we value the items on the left more.<br />
  24. 24. individuals<br />interactions<br />and<br />Individuals and interactions <br />over processes and tools <br />processes<br />and tools<br />
  25. 25. working<br />software<br />Working software <br />over comprehensive documentation<br />comprehensive<br />documentation<br />
  26. 26. customer<br />collaboration<br />Customer collaboration over contract negotiation<br />contract<br />negotiation<br />
  27. 27. responding<br />change<br />to<br />Responding to change<br />over following a plan<br />following<br />plan<br />a<br />
  28. 28. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  29. 29. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  30. 30. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  31. 31. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Business people and developers must work together daily throughout the project.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  32. 32. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  33. 33. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  34. 34. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Working software is the primary measure of progress.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  35. 35. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  36. 36. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Continuous attention to technical excellence and good design enhances agility.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  37. 37. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  38. 38. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  39. 39. Manifesto Principles <br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<br />Working software is the primary measure of progress.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.<br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.<br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.<br />Continuous attention to technical excellence and good design enhances agility.<br />Business people and developers must work together daily throughout the project.<br />Simplicity--the art of maximizing the amount of work not done--is essential.<br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.<br />The best architectures, requirements, and designs emerge from self-organizing teams.<br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.<br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.<br />
  40. 40.
  41. 41.
  42. 42. ASD<br />DSDM<br />XP<br />Scrum<br />Crystal<br />TNet<br />FDD<br />
  43. 43. &a<br />F<br />Discussion<br />
  44. 44.
  45. 45.
  46. 46. Reference<br /><ul><li>http://www.agilemanifesto.org
  47. 47. http://www.pmdoi.org
  48. 48. http://agilemanifesto.org/iso/zhchs/
  49. 49. http://agilemanifesto.org/iso/zhchs/principles.html
  50. 50. http://agilemanifesto.org/history.html
  51. 51. http://www.infoq.com/resource/news/2008/01/lean-2008-beijing/zh/resources/LeanThinkingwitheExamples.pdf
  52. 52. http:// www.scrumalliance.org
  53. 53. http:// www.controlchaos.com
  54. 54. http:// www.ambysoft.com</li></li></ul><li>Thanks A lot!Hoh~<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×