Avoid Chaos in Agile Development by Defining When a Story Is 'Done'


Published: 07 April 2017 ID: G00326411

Analyst(s):

Purchase this Document

Price: $195.00 USD (PAGES: 8)

To purchase this document, you will need to register or sign in above.

Summary

A strong definition of "done" improves quality, tracking and sustainability. Application leaders should work with agile teams to ensure a thorough and consistent understanding of what is needed to complete a story.

Table of Contents

  • Introduction
    • A Cautionary Tale
  • Analysis
    • Define What It Means for a Story to Be Done
      • How to Define "Done"
    • Track Releases by Tracking Complete Stories
      • Avoid Delaying Work to the End of a Sprint
    • Keep the Definition of Done as Light as Possible
      • Continuously Streamline
      • Simplify by Changing Artifacts
      • Simplify by Removing Artifacts
  • Gartner Recommended Reading
© 2017 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction and distribution of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartners research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.

Why Gartner

Gartner delivers the technology-related insight you need to make the right decisions, every day.

Find out more