Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

This presentation provides a valued information about scrum , its rules and how to apply it.

Published in: Technology
  • Be the first to comment

  • Be the first to like this


  1. 1. Scrum Method Created By : Hala Mehana – Business Analyst
  2. 2. Agenda  What is Agile  The Agile Manifesto [Values]  Agile Principles  Agile Methodologies  Common Misconceptions about Agile  What is Scrum  How to apply Scrum  Build the team  Team Characteristics  Scrum Process  Definition of done  Release Planning  Iteration Planning  Inside Sprint  Meetings  Stabilization Iterations
  3. 3. What is Agile  “Agile is a mind-set defined by values guided by principles and manifested through many different practices”  Ahmed Sidky, ICAgile Executive Director
  4. 4. The Agile Manifesto [Values]  We are uncovering better ways of developing software by doing it and helping others doing 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.
  5. 5. Agile Principles  12 principles are a set of guiding concepts that support project teams in implementing agile projects, To achieve agile values.  Here are some of them:  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.  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 for the shorter timescale.  Business people and developers must work together daily throughout the project.  Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.  To read all principles, click the following link
  6. 6. Agile Methodologies  Scrum  Xtreme Programming (XP)  Agile Unified Process (AUP)  Feature Driven Development (FDD)  Dynamic System Development Method (DSDM)  Crystal Methods
  7. 7. Common Misconceptions about Agile  Agile is a Process.  Agile is a Silver Bullet that will solve organization’s problems.  Agile implementations are document-less.  Agile teams don’t design, plan or take upfront decisions.  Agile teams are constantly under pressure, as they should deliver something after each sprint.
  8. 8. What is Scrum  Scrum is a lightweight agile software development framework for managing product and application development
  9. 9. How to apply Scrum Follow the following steps
  10. 10. Build the team  Stockholders  are parties with an interest in the product. They might include suppliers, customers, the business owner.  Business Owner  is a key stakeholder who supplies resources for the project.  Product Owner  is responsible for understanding what stakeholders require, interpreting these requirements for the team, and providing clear prioritized direction.  Scrum master  is responsible for the health of the process, reporting the progress of the team, and removing impediments to progress.  Team  is composed of those people actively engaged in building the product.
  11. 11. Build the team-Team Characteristics  Development Team Characteristics  Small (typically 5-9 people)  Preferably co-located  Cross-functional  Self-organizing  Accountable & committed  Focused, preferably fulltime  Preferably long-lived
  12. 12. Build the team-Team Characteristics Product Owner  Responsibilities  Formulate the product vision and roadmap  Represents the business side; responsible for ROI  Represents the Customer/users community  Owns the product backlog  Prioritizes features according to business value  Defines acceptance criteria and accepts or rejects results  Characteristics  Available & committed  Knowledgeable (Business side)  Good communicator and motivator  Decisive  Empowered
  13. 13. Build the team-Team Characteristics Scrum Master  Responsibilities  Coach the team to perform at its best  Facilitates the team’s activities and decisions  Servant leader to the team  Enable and deploy agile practices  Protects the team from external interferences  Impediment remover  Characteristics  Responsible  Humble  Collaborative  Committed  Influential  Knowledgeable
  14. 14. Scrum Process
  15. 15. Scrum Process - Definition of done  Teams establish their Definition of Done.  Tasks are done, when it 100% finished.  Things are “Done” only when they meet the DoD.  The Three Levels of the Done Definition  the team is done with a story?  the team is done with a sprint?  the team is done with a release?
  16. 16. Scrum Process – Release Planning  Backlog Sizing  Estimate user stories in story points  Backlog Prioritization  Prioritize the user stories in the backlog  Iteration Length selection  Select an appropriate iteration length for the rest of the release  Velocity Estimation  Estimate the team’s velocity “Number of size units covered by the team during an iteration“  Release Plan  Finalize the Release Plan
  17. 17. Scrum Process – Iteration Planning  Selecting the amount of work needed to completed by the team  Capacity and resource planning  Estimating the amount of work needed to be finished during the iteration  Techniques:  Velocity Driven Planning  Commitment Driven Planning
  18. 18. Inside Sprint
  19. 19. Scrum Process - Meetings  Iteration Planning Meeting  Time-boxed (Typically 4 hours for biweekly iterations)  The whole team participates  The team creates Sprint Backlog  The team estimates Sprint Backlog in hours  The team commits to delivering a set of features valuable to the customer
  20. 20. Scrum Process - Meetings  Daily Stand-up Meetings  Short (15 minutes)  Frequent (Daily)  Stand-up meetings!  Discuss status, only report it  Focus on finding solutions  Meeting questions:  Relative to the Backlog (list of incomplete tasks), what have you completed since the last meeting?  What obstacles got in the way of your completing this work?  Relative to the Backlog, what specific things do you plan to accomplish between now and the next meeting?
  21. 21. Scrum Process - Meetings  Iteration Review Meeting  Time-boxed (Typically 2 hours for biweekly iterations)  Team presents what was accomplished during the iteration (often as a demo)  Whole team participates  Customers are invited  Informal (no slides)
  22. 22. Scrum Process - Meetings  Iteration Retrospective  Time-boxed (typically 1-2 hours for biweekly iterations)  Done after the iteration ends  The whole team participates  The team discusses lessons learnt during the iteration in the form of 3 questions:  What should we start doing?  What should we stop doing?  What should we keep doing?
  23. 23. Stabilization Iterations  Also called “Release Iteration”  When: before release  Why:  Bug Fixing  System/Integration Testing  Regression Testing  Refactoring  More Technical Debt > Longer Stabilization periods
  24. 24. Thank You