Agile presentation1

1,181 views

Published on

agile presentation I gave for project management

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

  • Be the first to like this

No Downloads
Views
Total views
1,181
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile presentation1

  1. 1.
  2. 2. People in history that inspired Different methods & gave us much opportunity to build from <br />Ibn al-Haytham aka (al-Basri) born in Alhazen, 965–1039<br />I’m one of the key figures in the development of scientific method<br />I also Seek Truth <br />Frederick Winslow Taylor born in 1856<br />I Applied the scientific method to the management of workers greatly could improve productivity<br />I simplified jobs for unskilled workers<br />
  3. 3. Overview<br />
  4. 4. Introduction<br />In general, unlike traditional linear (waterfall) development, Agile methods seek to break down organizational barriers and drive toward faster incremental development and <br /> deployment, without compromising <br /> the quality of the delivered product. <br /> Agile is focused on individuals and <br /> interactions over processes and <br /> tools, yet contrary to some (widely <br /> held) beliefs, “true” Agile <br /> Development is extremely <br /> structured and disciplined, and <br /> typically will only succeed in higher <br /> maturity organizations <br />
  5. 5. History of the Agile Methodology?<br /> The modern definition of agile software development evolved in the mid-1990s as part of a reaction against "heavyweight" methods, perceived to be typified by a heavily regulated, regimented, micro-managed use of the waterfall model of development. The processes originating from this use of the waterfall model were seen as bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform effective work. Initially, agile methods were called "lightweight methods.“<br />In 2001, 17 prominent figures in the field of agile development (then called "light-weight methods") came together at the Snowbird ski resort in Utah to discuss ways of creating software in a lighter, faster, more people-centric way. They coined the terms "Agile Software Development" and "agile methods", and they created the Agile Manifesto, widely regarded as the canonical definition of agile development and accompanying agile principles. Later, some of these people formed The Agile Alliance, a non-profit organization that promotes agile development.<br />http://en.wikipedia.org/wiki/Agile_software_development<br />
  6. 6. What Is Agile Methodology?<br />Although there are many differing approaches to Agile Development, there are a number of shared characteristics that generally apply. These are:<br /><ul><li>Agile Development Methodology is an approach to software development that values early and continuous delivery of production ready software in a structured, systematic and repeatable way
  7. 7. At its core, Agile focuses on the efficiencies that are natural to small teams that have well defined roles and responsibilities. The goal is to have a process that enables the highest percentage of project effort to be spent on building quality components while avoiding all extraneous steps
  8. 8. Frequent delivery of proven production ready software is the single most important measurement of progress</li></li></ul><li>Agile Methodology, cont.<br /><ul><li>Development iterations that are most typically between 2 and 6 weeks in length
  9. 9. Strict adherence to:
  10. 10. Iteration start and end dates
  11. 11. Iteration deliverables which include (not necessarily in this order)
  12. 12. Requirements gathering and analysis
  13. 13. Planning
  14. 14. Design
  15. 15. Development/Build
  16. 16. Testing
  17. 17. Deployment
  18. 18. Documentation
  19. 19. Delivering production ready software (iteration end dates are not milestones)</li></li></ul><li>Agile Methodology, cont.<br /><ul><li> Embracing requirements changes at all times during the </li></ul> project but locking requirements once they are included in an <br /> iteration<br /><ul><li>Using each completed iteration as a mechanism to reprioritize business requirements
  20. 20. Continuous face-to-face interaction with requirements drivers whether they be clients, business partners, or subject matter experts
  21. 21. A common theme among team members, which strives for the most simplistic solution to a given problem. These typically focus on specific problems which are real today and do not attempt to address problems which may occur in the future.
  22. 22. Continuous re-evaluation of the methodology, the procedures, the code. Everything should be frequently re-evaluated for inefficiencies and updated to reflect the current team, department, company, and industry environments. </li></li></ul><li>Principles behind the Agile Manifesto<br />
  23. 23. Principles behind the Agile Manifesto continued<br />
  24. 24. Principles behind the Agile Manifesto #3<br />
  25. 25. The AgileValues<br />We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:<br />
  26. 26. What is Scrum?<br />
  27. 27. Scrum origins<br />Jeff Sutherland<br />Initial scrums at Easel Corp in 1993<br />IDX and 500+ people doing Scrum<br />Ken Schwaber<br />ADM<br />Scrum presented at OOPSLA 96 with Sutherland<br />Author of three books on Scrum<br />Mike Beedle<br />Scrum patterns in PLOPD4<br />Ken Schwaber and Mike Cohn<br />Co-founded Scrum Alliance in 2002, initially within the Agile Alliance<br />
  28. 28. Whohas used Scrum?<br />
  29. 29. Feature request from<br />Product X<br />
  30. 30. Product backlog<br />List of features<br />Master list<br />Collection<br />Allowed to grow and change<br />
  31. 31. Key people and jobs<br />tools they need<br />
  32. 32. Scrum team<br />Project Team.<br />Small but with a punch<br />Easy to manage<br />Everyone gets to know one another<br />
  33. 33. Other key people<br />Users<br />Developers and Testers<br />
  34. 34. Releaseplanning<br />Estimated guess of 500 hours ?<br />the product owner and team identify the features they want<br />Experts are not perching<br />
  35. 35. Sprints<br />Sprints are short duration milestone<br />4 or more sprints<br />Release cycles and sprints <br />have a positive correlation relationship<br />
  36. 36. Burndownchart<br />Burndown velocity <br />ON time<br />Source -http://weblogs.asp.net/jcogley/archive/2008/03.aspx<br />
  37. 37. Process<br />Product Backlog <br />The sprint backlog<br />Daily Scrum meeting<br />Potentially shippable product increment <br />
  38. 38. Typically meeting setting that don’t utilize scrum methods<br />
  39. 39. Scrum method<br />No chairs<br />15 minute rule<br />The purpose of the Daily Scrum meeting is to answer Scrum’s three questions<br />1<br />2<br />3<br />Today the world is going to Bailout another investment bank!<br />
  40. 40. Conclusion & References<br />http://www.netmba.com/mgmt/scientific/<br />http://en.wikipedia.org/wiki/Scientific_method<br />http://www.youtube.com/watch?v=Q5k7a9YEoUI&feature=PlayList&p=24532B7471176794&playnext_from=PL&index=0&playnext=1<br />http://www.scrumalliance.org/learn_about_scrum<br />www.agilemanifesto.org/<br />
  41. 41. The END<br />

×