PROGRESS

The following summary comes from Rick Freedman, writing in Tech Decision Maker, 19 July 2010: Using Scrum as an example, the reporting expectations are clearly defined; different agile methods have different standards. In Scrum, we typically create four reports at the end of each iteration: the Prod...

Full description

Saved in:
Bibliographic Details
Published inAdaptable Project Management - a Combination of Agile and Project Management for All (PM4A) p. 116
Main Author Bentley, Colin
Format Book Chapter
LanguageEnglish
Published United Kingdom IT Governance Publishing 25.08.2020
IT Governance Ltd
Online AccessGet full text

Cover

Loading…
More Information
Summary:The following summary comes from Rick Freedman, writing in Tech Decision Maker, 19 July 2010: Using Scrum as an example, the reporting expectations are clearly defined; different agile methods have different standards. In Scrum, we typically create four reports at the end of each iteration: the Product Backlog, which lists all the features that make up the entire product the Sprint Backlog, which include the features we’ve committed to deliver in the next iteration the Changes report, which details the differences between the Product Backlog and the Sprint Backlog the Burndown report or chart, which illustrates (usually in the form
ISBN:9781787782310
178778231X
DOI:10.2307/j.ctv143mds3.12