Agile Scrum


Published on

Agile Scrum

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Building a software product would cost a lot of extra money when the management is poor, therefore many software management methods were invented to aid managing the process of building software product.
  • Agile Scrum

    1. 1. Agile Method - Scrum Present by Gloria Law April 7, 2008
    2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Waterfall Life Cycle </li></ul><ul><li>Agile Method </li></ul><ul><li>Scrum </li></ul><ul><li>Sprints </li></ul><ul><li>Potentially Shippable Product Increment </li></ul><ul><li>Product Owner </li></ul><ul><li>Product Backlog </li></ul><ul><li>ScrumMaster </li></ul><ul><li>Daily Scrum Meeting </li></ul><ul><li>Scrum of Scrums </li></ul><ul><li>Sprint Planning </li></ul><ul><li>Release Planning </li></ul><ul><li>Sprint Review </li></ul><ul><li>Risk Management </li></ul><ul><li>System Representation </li></ul><ul><li>Advantage & Disadvantage </li></ul>
    3. 3. Introduction <ul><li>Need software management methods to decrease the cost </li></ul><ul><li>28% completed on time and budget </li></ul><ul><li>23% failed </li></ul><ul><li>49% challenged </li></ul><ul><li>72% not meeting original goals </li></ul>
    4. 4. Waterfall Life Cycle X
    5. 5. Agile Method <ul><li>Continuous attention to technical excellence and good design </li></ul><ul><li>Self-organizing teams </li></ul><ul><li>Customer satisfaction by rapid, continuous delivery of useful software </li></ul><ul><li>Working software is the principal measure of progress </li></ul><ul><li>Delivered frequently </li></ul>
    6. 6. Agile Method (cont) <ul><li>Late changes in requirements </li></ul><ul><li>Close, daily cooperation between business people and developers </li></ul><ul><li>Face-to-face conversation is the best form of communication </li></ul><ul><li>Time is a fixed variable </li></ul>
    7. 7. Agile Manifesto <ul><li>“ We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: </li></ul><ul><li>Individuals and interactions over processes and tools </li></ul><ul><li>Working software over comprehensive documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan </li></ul><ul><li>That is, while there is value in the items on the right, we value the items on the left more.” </li></ul>
    8. 8. Scrum <ul><li>Rugby </li></ul><ul><li>Eight individual </li></ul><ul><li>Move the ball down the field </li></ul><ul><li>One Goal </li></ul>
    9. 9. Sprints <ul><li>Scrum project make progress in a series of Sprints </li></ul><ul><li>Timeboxed Period (2 – 4 weeks) </li></ul><ul><li>During Sprint, team does: </li></ul><ul><ul><li>Analysis </li></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Code </li></ul></ul><ul><ul><li>Test </li></ul></ul><ul><li>Product is potentially releasable after every Sprint </li></ul>
    10. 10. Potentially Shippable Product Increment <ul><li>At the end of each Sprint, the Team must produce a potentially shippable product increment (commit by the Team) </li></ul><ul><ul><li>High Quality </li></ul></ul><ul><ul><li>Tested </li></ul></ul><ul><ul><li>Complete </li></ul></ul><ul><ul><li>Done </li></ul></ul>
    11. 11. Product Owner <ul><li>Represents (or is) the user or customer for the project </li></ul><ul><li>Knowing what to build and in what sequence </li></ul><ul><li>Defines goals for overall project </li></ul>
    12. 12. Product Backlog <ul><li>The requirements </li></ul><ul><li>A dynamic list of all desired work on the project </li></ul><ul><li>Prioritized by the Product Owner </li></ul><ul><li>Reprioritized at the start of each Sprint </li></ul>
    13. 13. ScrumMaster <ul><li>Responsible for enforcing the values and practices of the framework and the Team </li></ul><ul><li>Remove impediments </li></ul><ul><li>Educate outside groups about how the Teams is working </li></ul><ul><li>Improve productivity in any way possible </li></ul><ul><li>Facilitate Team meetings </li></ul><ul><li>Servant Leader </li></ul>
    14. 14. Daily Scrum Meeting <ul><li>Tasks that is completed </li></ul><ul><li>Obstacles to complete specific task </li></ul><ul><li>Plan to accomplish between now and the next Scrum meeting </li></ul>
    15. 15. Scrum of Scrum <ul><li>Synchronize inter-team work </li></ul><ul><ul><li>Issue list is up-to-date </li></ul></ul><ul><ul><li>Discuss impediments </li></ul></ul>
    16. 16. Sprint Planning <ul><li>Happens on the 1 st day of the Sprint </li></ul><ul><li>Scrum Team takes the Sprint Goal and decides what Product Backlog are necessary </li></ul><ul><li>Team self-organizes around how they’ll meet the Sprint Goal </li></ul><ul><li>Sprint Backlog is created </li></ul>
    17. 17. Release Planning <ul><li>Several Days before Sprint Planning </li></ul><ul><li>What will be built </li></ul><ul><li>Identify top level priorities </li></ul><ul><li>Select more than what the Team can likely do in one Sprint </li></ul>
    18. 18. Sprint Review <ul><li>Updates to Product Owner </li></ul><ul><li>Plans for next Sprint </li></ul><ul><ul><li>Change in Requirements </li></ul></ul><ul><li>Demonstration </li></ul>
    19. 19. Risk Management <ul><li>Risk is low </li></ul><ul><li>Continue testing </li></ul><ul><li>Problem is notified during Daily Scrum Meeting </li></ul>
    20. 20. System Representation Release Planning Sprint Planning Ideas Programming Daily Scrum Sprint Review Release Review Working Code Error Error Product Backlog Release Backlog Sprint Backlog
    21. 21. Advantage & Disadvantage + Continuous testing and communication can find issues rapidly - Might not find bugs until later stage Risk Management - Knowledge is stored mentally - Code is the documentation + Highly emphasize + Requires in every stage Documentation + Good internal communication + Higher quality - Lack of communication with the customer and team members Communication + Micro Planning + Avoid Requirement cramming - Might be headed toward wrong direction + Able to see the overall project Planning + No delays on important features + Less important features might scaled back or dropped + Support for long-term plans Prioritization Agile Method Traditional Management
    22. 22. Work Breakdown Schedule <ul><li>Requirement Analysis </li></ul><ul><ul><li>Proposal (February) </li></ul></ul><ul><li>Research </li></ul><ul><ul><li>Review Case Study (March) </li></ul></ul><ul><ul><li>Paper Analysis (March-April) </li></ul></ul><ul><ul><ul><li>Writing the Paper </li></ul></ul></ul><ul><ul><ul><li>Proof Read </li></ul></ul></ul>
    23. 23. Reference <ul><li>Pressman, Roger S. “Software Engineering.” Software Engineering Project Management. Pp. 30-47. IEEE. 2000. </li></ul><ul><li>Highsmith, Jim & Cockburn, Alistair. “Agile Software Development: The Business of Innovation.” IEEE Computer. September 2001. </li></ul><ul><li>&quot;Agile software development.&quot; Wikipedia, The Free Encyclopedia . 19 Apr 2007, 10:26 UTC. Wikimedia Foundation, Inc. 19 Apr 2007 < http:// = Agile_software_development&oldid =124050398 >. </li></ul><ul><li>Rising, Linda & Janoff, Norman. “The Scrum Software Development Process for Small Teams.” IEEE Software. July/August 2000. </li></ul><ul><li>Brooks, Frederick. The Mythical Man-Month: Essays on Software Engineering. MA: Addison-Wesley Professional 1975. </li></ul><ul><li>Sutherland, Jeff. “Agile Development: Lessons Learned From the First Scrum.” Cutter Agile Project Management Advisory Service. Executive Update, Vol. 5, No. 20. October 2004. </li></ul><ul><li>Anderson, David. Agile Management for Software Engineering . New Jersey: Prentice Hall, 2004. </li></ul><ul><li>KarlstrÖm, Daniel & Runeson, Per. “Combining Agile Methods with Stage-Gate Project Managment.” IEEE Software. May/June 2005. </li></ul><ul><li>“ Agile Manifesto.” 19 Apr 2007, 10:26 UTC. < > </li></ul>