Scribd Logo
Upload

Welcome to Scribd!

  • 45 views

    Agile Scrum

    Uploaded by

    Parth Patel
    The document discusses the Agile Scrum framework. It is an iterative and incremental framework for managing product development. Key aspects include self-organizing cross-functional teams, a product owner who prioritizes a backlog of features, sprints where work is planned and reviewed daily, and retrospectives after each sprint to improve. The goal is lightweight, people-focused development of valuable products.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Agile Scrum

    Uploaded by

    Parth Patel
    45 views13 pages
    The document discusses the Agile Scrum framework. It is an iterative and incremental framework for managing product development. Key aspects include self-organizing cross-functional teams, a product owner who prioritizes a backlog of features, sprints where work is planned and reviewed daily, and retrospectives after each sprint to improve. The goal is lightweight, people-focused development of valuable products.

    Original Description:

    Agile Scrum Framework

    Original Title

    Agile_Scrum

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the Agile Scrum framework. It is an iterative and incremental framework for managing product development. Key aspects include self-organizing cross-functional teams, a product owner who prioritizes a backlog of features, sprints where work is planned and reviewed daily, and retrospectives after each sprint to improve. The goal is lightweight, people-focused development of valuable products.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    45 views13 pages

    Agile Scrum

    Uploaded by

    Parth Patel
    The document discusses the Agile Scrum framework. It is an iterative and incremental framework for managing product development. Key aspects include self-organizing cross-functional teams, a product owner who prioritizes a backlog of features, sprints where work is planned and reviewed daily, and retrospectives after each sprint to improve. The goal is lightweight, people-focused development of valuable products.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 13

    Agile Scrum

    Framework
    • Agile software development refers to a group of
    software development methodologies based on
    iterative development, where requirements and
    solutions evolve through collaboration between
    self-organizing cross-functional teams.
    • Current software processes are too heavyweight
    or cumbersome.
    What is Agile ? • Too many things are done that are not directly
    related to software product being produced.
    • Current Software development is too rigid.
    • Agile methods are considered:
    • Lightweight.
    • People based rather than Plan based.
    Scrum - Introduction
    • Scrum is a lightweight, iterative and
    incremental framework for managing
    product development.
    • Scrum defines “a flexible, holistic
    product development strategy where a
    development team works as a unit to
    reach a common goal.”
    • Scrum, in a simple term, is a framework
    within which people can address
    complex adaptive problems, while
    productively and creatively delivering
    products of the highest possible value.
    The Agile
    Scrum
    Framework
    Product Owner

    • Define the features of the product


    • Makes scope vs. schedule decisions
    • Responsible for achieving financial goals of the project
    • Prioritize the product backlog
    • Adjust features and priority every sprint, as needed
    • Accept or reject work results
    The Scrum Master

    Responsible for Coaches the team


    enacting Scrum Removes to their best
    values and impediments possible
    practices performance

    Enable close
    Helps improve Shield the team
    cooperation across
    team productivity from external
    all roles and
    in any way possible interference
    functions
    The Team
    • Typically 5-9 people
    • Cross-functional:
    - Programmers, testers, UI/UX designers,
    etc.
    • Members should be full-time
    • May be exceptions (e.g., database
    administrator)
    • Teams are self-organizing
    • Ideally, no titles but rarely a possibility
    • Membership should change only between
    sprints
    • The requirements.
    • A list of all desired work on the project.
    The Product • Ideally expressed such that each item has value
    to the users or customers of the product.
    Backlog • Prioritized by the product owner.
    • Reprioritized at the start of each sprint.
    Sprint Planning Meeting
    Who ?
    • Team, ScrumMaster, & Product Owner

    Agenda ?
    • Discuss top priority product backlog items
    • Team selects which to do

    Why ?
    • Know what will be worked on
    • Understand it enough to do it
    The Daily Scrum
    Parameters
    • Daily
    • 15-minutes
    • Stand-up

    Not for problem solving


    • Whole world is invited
    • Only team members, ScrumMaster, product
    owner, can talk

    Helps avoid other unnecessary meetings


    The Sprint Review
    • Team presents what it accomplished during
    the sprint
    • Typically takes the form of a demo of new
    features or underlying architecture
    • Informal
    • 2-hour prep time rule
    • No slides
    • Whole team participates
    • Invite the world
    Sprint retrospective
    • Periodically take a look at what is and is not
    working
    • Typically around 30 minutes
    • Done after every sprint
    • Whole team participates
    - ScrumMaster
    - Product owner
    - Team
    - Possibly customers and others
    Thank You

    You might also like