Scribd Logo
Upload

Welcome to Scribd!

  • 04 - 02 Defintion of Done

    Uploaded by

    Nanda Christanto
    7 views1 page
    The document provides examples of what could constitute a "Definition of Done" for agile development work. It lists activities like code being peer reviewed, end-user documentation being updated, functionality being demonstrated to stakeholders for feedback, code being checked, work being documented, quality assurance testing being completed, and test scripts and automated testing suites being updated to reflect implemented changes. The definition of done examples are meant to outline criteria for determining when a user story or development task can be considered fully completed.

    Original Description:

    Original Title

    04_02 Defintion of Done

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides examples of what could constitute a "Definition of Done" for agile development work. It lists activities like code being peer reviewed, end-user documentation being updated, functionality being demonstrated to stakeholders for feedback, code being checked, work being documented, quality assurance testing being completed, and test scripts and automated testing suites being updated to reflect implemented changes. The definition of done examples are meant to outline criteria for determining when a user story or development task can be considered fully completed.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    7 views1 page

    04 - 02 Defintion of Done

    Uploaded by

    Nanda Christanto
    The document provides examples of what could constitute a "Definition of Done" for agile development work. It lists activities like code being peer reviewed, end-user documentation being updated, functionality being demonstrated to stakeholders for feedback, code being checked, work being documented, quality assurance testing being completed, and test scripts and automated testing suites being updated to reflect implemented changes. The definition of done examples are meant to outline criteria for determining when a user story or development task can be considered fully completed.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Agile Product Owner: Techniques

    with Angela Wick

    Definition of Done Examples

    The code has been peer reviewed.

    End-user training documentation and help information have been updated.

    The story functionality has been demonstrated to the product owner for feedback multiple times.

    The functionality has been demonstrated with a larger stakeholder group.

    The code has been checked.

    The team has documented what was built.

    QA has tested the user story and developed regression tests.

    Testing and automated test scripts have been completed and implemented into a test suite.

    Updated process assets, diagrams, models, and so on have been updated with what was
    implemented.

    Automated regression testing scenarios have been updated and added to the automation testing
    suite.

    Agile Product Owner: Techniques with Angela Wick

    You might also like