Agile For Harel 4 08 V1

396
-1

Published on

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

  • Be the first to like this

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

No notes for slide
  • Agile For Harel 4 08 V1

    1. 1. The Agile Development Concept Pini Cohen EVP & Senior Analyst Architecture & Infrastructure Strategies [email_address]
    2. 2. Dealing with Real Software… <ul><ul><li>I’m pretty sure I have fixed that bug. Why is it back? </li></ul></ul><ul><ul><li>Oops! The latest version got overwritten by an older version… </li></ul></ul><ul><ul><li>How can I go back to the previous version, the one that was stable? </li></ul></ul><ul><ul><li>The design document is out of sync with programs… </li></ul></ul><ul><ul><li>I don’t know if all the changes that were suggested have been incorporated! </li></ul></ul><ul><ul><li>Which version is the right one? We have so many! </li></ul></ul><ul><ul><li>For this customer, I’d like to use this special component instead of the regular one… </li></ul></ul>Source: www.site.uottawa.ca/~damyot/csi5112/notes/ConfigurationManagement.ppt
    3. 3. Software Development Is Limited By Constraints Quality Scope Schedule Cost Source: Borland
    4. 4. Software Development Is Limited By Constraints Quality Scope Schedule Cost Source: The Standish Group 2003 Source: Borland
    5. 5. Software Development Is Limited By Constraints Quality Scope Schedule Cost Source: The Standish Group 2003 Source: Borland
    6. 6. Software Development Is Limited By Constraints Quality Scope Schedule Cost Source: The Standish Group 2003 Source: Borland
    7. 7. Software Development Is Limited By Constraints Quality Scope Schedule Cost Source: Borland
    8. 8. Software Development <ul><li>The traditional development focus is to engineer out defects </li></ul><ul><ul><li>Good principle </li></ul></ul><ul><ul><li>Hammer out defects early </li></ul></ul><ul><li>Defects arise because requirements change </li></ul><ul><li>Too many communication gaps </li></ul>Isolated Process Design Code Test Deploy
    9. 9. What is Agility? The ability to… <ul><li>Move quickly </li></ul><ul><li>Travel light </li></ul><ul><li>Commit late </li></ul><ul><li>Act soon </li></ul><ul><li>Keep aware </li></ul><ul><li>Respond to change </li></ul><ul><li>Be good at following a moving target </li></ul><ul><li>Evolve and adapt to the local environment </li></ul>
    10. 10. Agile Project Management - Overview Analysis Code Test Implement Analysis Code Test Time in Months Work Effort 3 6 9 12 3 6 9 12
    11. 11. Agile Development Lifecycle
    12. 12. Why are businesses moving to Agile? <ul><li>95% Reduced cost (or no cost increase) </li></ul><ul><li>93% Productivity better or significantly better </li></ul><ul><li>88% Quality better or significantly better </li></ul><ul><li>83% Business satisfaction better or significantly better </li></ul>Source: Shine Tech , 2003
    13. 13. The Agile Philosophy <ul><li>Embrace Change </li></ul><ul><ul><li>Fundamental mindset change—responding to change is more important than following a plan </li></ul></ul><ul><li>Focus on Customer Value </li></ul><ul><ul><li>Deploy value early and often </li></ul></ul><ul><ul><li>Apply lean techniques </li></ul></ul><ul><li>Deliver Chunks of Functionality Incrementally </li></ul><ul><ul><li>Capabilities and Stories </li></ul></ul><ul><ul><li>Stories always shippable </li></ul></ul><ul><li>Collaborate </li></ul><ul><ul><li>Cross-functional teams </li></ul></ul><ul><ul><li>Constant interaction with Customers </li></ul></ul><ul><li>Reflect and Learn Continuously </li></ul>
    14. 14. Agile Development * A software development philosophy that values: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan *www.agilemanifesto.org
    15. 15. Agile Techniques - Collaborative Planning
    16. 16. Agile Techniques - Collaborative Development Picture courtesy of Joshua Kerievsky
    17. 17. Agile Development Adoption: Cutter <ul><li>When did your organization deliver its first project via Agile? </li></ul>
    18. 18. Agile Development Adoption: Cutter <ul><li>What has kept your organization from transitioning to an Agile process? (Please select all that apply.) </li></ul>
    19. 19. Agile Development Adoption: Cutter <ul><li>What business goals is your organization trying to achieve by transitioning to Agile?(Respondents who have already delivered an Agile project.) </li></ul>
    20. 20. Cutter Agile Survey : Demographics July 07 <ul><li>Close to half (41%) of the 121 responding organizations have more than 1,000 employees, 27% have between 100 and 1,000 employees, and the remainder have 100 or fewer employees. </li></ul><ul><li>Twenty-three percent of responding organizations have annual revenues of over US $1 billion, 19% have annual revenues between $100 million and $1 billion, another 22% have annual revenues between $10 million and $100 million, and the remaining 36% have annual revenues of under $10 million. </li></ul><ul><li>Financial services account for the largest single industry sector (with 22% of respondents); </li></ul>
    21. 21. Thank you Happy Passover ! Pini Cohen EVP & Senior Analyst Architecture & Infrastructure Strategies [email_address]

    ×