Introduction to agile
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
317
On Slideshare
317
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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