Scrum summary

  • Created by: Shar shar
  • Created on: 11-06-19 11:42
View mindmap
  • Scrum
    • What is Scrum?
      • Framework for addressing complex and adaptive problems to deliver a valuable product.
        • Framework is used               - productively - creatively
        • - Lightweight  - Simple to understand    - Difficult to master
        • Used to manage work on complex products. Different processes and techniques can be employed.
        • The framework made up of: 1. Scrum teams           2. Events     3. Artifacts  4. Rules
      • A small team of people that is flexible and adaptive.
    • Why are there rules?
      • They bind together roles, events and artifacts. Rules cover interactions and relationship between them.
    • Uses of Scrum
      • - Identify viable markets, technologies and product capabilities.
      • - Develop products and enhancements
      • - Frequently release products and enhancements
      • - Develop and maintain operational environments e.g. cloud
    • Benefits of Scrum
      • There is iterative and incremental knowledge transfer
      • Can deal with complexities in technology, the market and the environment.
      • Suitable for products, services and the organisation of parent organizations.
      • Team model designed to optimise flexibility, creativity and productivity.
    • Formal events
      • Four events for inspection & adaptation are: 1. Sprint planning 2. Daily Scrum 3. Sprint review 4. Sprint retrospective
        • SPRINT PLANNING Who? Entire Scrum team How long? 8 hours max What is forecast? Functionality developed. What resources are used? product backlog, latest increment, projected capacity, past performance of the dev team Invites too? Other experts who have domain or technical advice
        • DAILY SCRUM    How long? Always 15 minutes     Key questions: yesterday, today impediments
        • SPRINT REVIEW Aim? Inspect increment and adapt product backlog  Who? Scrum team and stakeholders Time-box? 4 hours (monthly sprint)
          • What does the Product Owner discuss? What has been done and not done from the product backlog, Projects likely targets and delivery dates.
          • What? collaboration about what was done Conclusion: Decide on next things that could be done to optimise value  Review: timeline, budgets, potential capabilities and market place
          • What does the dev team discuss? What went well, problems and solutions used
        • SPRINT RETROSPECTIVE How long? 3 hours max. Aim? Scrum team inspects itself Who? Scrum team & Scrum Master  What? plans ways to increase product quality by improving work processes or adapting the definition of "Done"
        • THE SPRINT (a) a goal of the build      (b) a design (c) flexible plan            (d) the resultant product increment
    • Values
      • - Courage to do the right thing and work on tough problems.      - Respect each other to be capable, independent people.


No comments have yet been made

Similar All resources:

See all All resources »See all Other resources »