Scribd Logo
Upload

Welcome to Scribd!

  • Scrum: Test-Driven Development

    Uploaded by

    polters
    225 views31 pages
    The document discusses test-driven development approaches like extreme programming, Scrum, feature-driven development, and lean software development. It focuses on explaining Scrum, describing the daily scrum meetings, sprint cycles, product and sprint backlogs, Scrum team roles, and tools like task boards and burn down charts. Benefits of adopting Scrum are highlighted through a case study showing reduced costs, defects, and overhead and a happier development team.

    Original Description:

    Original Title

    Scrum the Basics 4549

    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?

    Report this Document
    The document discusses test-driven development approaches like extreme programming, Scrum, feature-driven development, and lean software development. It focuses on explaining Scrum, describing the daily scrum meetings, sprint cycles, product and sprint backlogs, Scrum team roles, and tools like task boards and burn down charts. Benefits of adopting Scrum are highlighted through a case study showing reduced costs, defects, and overhead and a happier development team.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    225 views31 pages

    Scrum: Test-Driven Development

    Uploaded by

    polters
    The document discusses test-driven development approaches like extreme programming, Scrum, feature-driven development, and lean software development. It focuses on explaining Scrum, describing the daily scrum meetings, sprint cycles, product and sprint backlogs, Scrum team roles, and tools like task boards and burn down charts. Benefits of adopting Scrum are highlighted through a case study showing reduced costs, defects, and overhead and a happier development team.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    of 31

    Test-driven Development

    Extreme programming

    Scrum
    Crystal
    Lean software development

    Feature-Driven Development
    What is “Scrum”?
    Who invented it?
    改善
    Continuous improvement

    Kaizen
    Why is it called “Scrum”?
    Who is using Scrum?
    How does it work?
    Every day a 15-
    Scrum sprint cycle minute meeting is
    held and the
    Scrum Master asks
    three questions:
    1) What did you do
    yesterday?
    2) What will you do
    Workday today?
    Product backlog One day 3) Is there anything
    Prioritised list of features in your way?
    required by the customer.

    Sprint backlog New functionality

    Features to be done this Is demonstrated at


    Sprint the end of each
    sprint. Features are
    expanded into smaller sprint.
    One month
    tasks.
    What does a Scrum team look like?
    Show me some of the tools…
    The project task board
    The burndown chart
    Case study 1: Systematic Software Engineering
    • Planning costs cut by 80%
    • Defects cut by 40%
    • Process overhead cut by half
    • Happier development team

    Now 100% Scrum. They charge


    double for waterfall, if asked.
    Learn more

    You might also like