Scribd Logo
Upload

Welcome to Scribd!

  • 40 views

    Scrum Agile Software Development: Presented by Thuc Nguyen Canh TPG IT Department

    Uploaded by

    Thuc Nguyen Canh
    Scrum is an agile framework for managing product development. It defines common roles, ceremonies, and artifacts. The roles are Product Owner, Scrum Master, and self-organizing Team. Ceremonies include Sprint Planning, Daily Scrum, Sprint Review and Retrospective. Artifacts are Product Backlog, Sprint Backlog and Burndown Charts. The process involves prioritizing Product Backlog, creating Sprints, daily stand-ups and reviewing progress each Sprint.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Scrum Agile Software Development: Presented by Thuc Nguyen Canh TPG IT Department

    Uploaded by

    Thuc Nguyen Canh
    40 views23 pages
    Scrum is an agile framework for managing product development. It defines common roles, ceremonies, and artifacts. The roles are Product Owner, Scrum Master, and self-organizing Team. Ceremonies include Sprint Planning, Daily Scrum, Sprint Review and Retrospective. Artifacts are Product Backlog, Sprint Backlog and Burndown Charts. The process involves prioritizing Product Backlog, creating Sprints, daily stand-ups and reviewing progress each Sprint.

    Original Title

    An Introduction to Scrum

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Scrum is an agile framework for managing product development. It defines common roles, ceremonies, and artifacts. The roles are Product Owner, Scrum Master, and self-organizing Team. Ceremonies include Sprint Planning, Daily Scrum, Sprint Review and Retrospective. Artifacts are Product Backlog, Sprint Backlog and Burndown Charts. The process involves prioritizing Product Backlog, creating Sprints, daily stand-ups and reviewing progress each Sprint.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    40 views23 pages

    Scrum Agile Software Development: Presented by Thuc Nguyen Canh TPG IT Department

    Uploaded by

    Thuc Nguyen Canh
    Scrum is an agile framework for managing product development. It defines common roles, ceremonies, and artifacts. The roles are Product Owner, Scrum Master, and self-organizing Team. Ceremonies include Sprint Planning, Daily Scrum, Sprint Review and Retrospective. Artifacts are Product Backlog, Sprint Backlog and Burndown Charts. The process involves prioritizing Product Backlog, creating Sprints, daily stand-ups and reviewing progress each Sprint.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 23

    Scrum

    Agile Software Development

    Presented by Thuc Nguyen Canh


    TPG IT Department
    Scrum framework
    Roles

    •Product owner
    •ScrumMaster
    •Team Ceremonies

    •Sprint planning
    •Sprint review
    •Sprint retrospective
    •Daily scrum meeting
    Artifacts

    •Product backlog
    •Sprint backlog
    •Burndown charts
    Scrum Step by Step

    Sprint Planning
    Scrum framework
    Roles

    •Product owner
    •ScrumMaster
    •Team Ceremonies

    •Sprint planning
    •Sprint review
    •Sprint retrospective
    •Daily scrum meeting
    Artifacts

    •Product backlog
    •Sprint backlog
    •Burndown charts
    Product owner
    • Define the features of the product
    • Decide on release date and content
    • Be responsible for the profitability of the
    product (ROI)
    • Prioritize features according to market value
    • Adjust features and priority every iteration, as
    needed 
    • Accept or reject work results
    The ScrumMaster
    • Represents management to the project
    • Responsible for enacting Scrum values and
    practices
    • Removes impediments
    • Ensure that the team is fully functional and
    productive
    • Enable close cooperation across all roles and
    functions
    • Shield the team from external interferences
    The team
    • Typically 5-9 people
    • Cross-functional:
    – Programmers, testers, user experience 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
    Roles
    Scrum framework
    •Product owner
    •ScrumMaster
    •Team Ceremonies

    •Sprint planning
    •Sprint review
    •Sprint retrospective
    •Daily scrum meeting
    Artifacts

    •Product backlog
    •Sprint backlog
    •Burndown charts
    Sprint planning meeting
    Team
    Team
    capacity
    capacity
    Sprint prioritization
    Product
    Product • Analyze and evaluate product Sprint
    Sprint
    backlog backlog goal
    goal
    backlog
    • Select sprint goal
    Business
    Business
    conditions
    conditions
    Sprint planning
    • Decide how to achieve sprint goal
    Current
    Current (design)
    Sprint
    Sprint
    product
    product • Create sprint backlog (tasks) from backlog
    backlog
    product backlog items (user
    stories / features)
    Techno-
    Techno- • Estimate sprint backlog in hours
    logy
    logy
    Sprint planning
    • Team selects items from the product backlog they
    can commit to completing
    • Sprint backlog is created
    – Tasks are identified and each is estimated (1-16 hours)
    – Collaboratively, not done alone by the ScrumMaster
    • High-level design is considered

    As
    Asaavacation
    vacationplanner,
    planner,IIwant
    want
    to
    tosee
    seephotos
    photosof
    ofthe
    thehotels.
    hotels.
    Code the middle tier (8 hours)
    Code the user interface (4)
    Write test fixtures (4)
    Code the foo class (6)
    Update performance tests (4)
    Sprint Planning Meeting
    • Stories to Sprint
    • Estimate Length
    Sprint Definition
    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
    Everyone answers 3 questions
    1
    What
    What did
    did you
    you do
    do yesterday?
    yesterday?

    2
    What
    What will
    will you
    you do
    do today?
    today?

    3
    Is
    Is anything
    anything in
    in your
    your way?
    way?
    • These are not status for the ScrumMaster
    – They are commitments in front of peers
    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 15–30 minutes
    • Done after every sprint
    • Whole team participates
    – ScrumMaster
    – Product owner
    – Team
    – Possibly customers and others
    Start / Stop / Continue
    • Whole team gathers and discusses what
    they’d like to:
    Start
    Start doing
    doing

    Stop doing
    This is just one
    of many ways to Continue
    Continue doing
    doing
    do a sprint
    retrospective.
    Roles
    Scrum framework
    •Product owner
    •ScrumMaster
    •Team Ceremonies

    •Sprint planning
    •Sprint review
    •Sprint retrospective
    •Daily scrum meeting
    Artifacts

    •Product backlog
    •Sprint backlog
    •Burndown charts
    Scrum in real

    Product Backlog
    -Done by Product Owner
    -In Excel format
    Scrum in real
    Sprint Backlog
    Sprint Backlog in real
    Reference
    • [An Introduction to Scrum] Slides of Mountain
    Goat Software
    • [Scrum and XP from the Trenches] Free ebook
    from InfoQ

    You might also like