ScrumWorks® - Features - Reports
Agile software development places an emphasis on "empirical" reporting and metrics. This means that a product's progress is judged by how much of the system is actually done.
In Scrum, "product backlog items" represent slices of functionality. Scrum reports are based on whether or not "product backlog items" are completely done. Therefore, reports based on the completion status of product backlog items are an empirical measure of the state of the product development.
ScrumWorks comes stocked with numerous reports based on the empirical progress of the product. In ScrumWorks, product backlog items can be marked "Done" to indicate the item is complete according to the Product Owner's acceptance criteria. Release forecasts are also based on the empirical progress of the product.
Reports are created in the ScrumWorks Desktop Client. Once created, a unique web address link is associated to the report and its parameters. For example, the link may look like:
http://server/scrumworks/report/A7aQiNL
This link can be passed to anyone interested in viewing the report from outside the ScrumWorks Desktop Client. Since the link itself is unique, it acts as its own password to protect sensitive data. This allows a casual observer (e.g., upper management, stakeholders, etc.) to visit a bookmark periodically and get updates to critical reports, all without having to log into ScrumWorks.
* adapted from Mike Cohn's Alternative Release Burndown Chart
"Microsoft", "Windows" and "Excel" are registered trademarks of Microsoft Corporation.
ScrumWorks comes stocked with numerous reports based on the empirical progress of the product. In ScrumWorks, product backlog items can be marked "Done" to indicate the item is complete according to the Product Owner's acceptance criteria. Release forecasts are also based on the empirical progress of the product.
Reports are created in the ScrumWorks Desktop Client. Once created, a unique web address link is associated to the report and its parameters. For example, the link may look like:
http://server/scrumworks/report/A7aQiNL
This link can be passed to anyone interested in viewing the report from outside the ScrumWorks Desktop Client. Since the link itself is unique, it acts as its own password to protect sensitive data. This allows a casual observer (e.g., upper management, stakeholders, etc.) to visit a bookmark periodically and get updates to critical reports, all without having to log into ScrumWorks.
ScrumWorks Reports
 |  |
| Product Burndown Chart -- A big picture view of where your product stands. | Enhanced Product Burndown Chart* --Distinguishes movement caused by work completion from movement caused by moving the finish line. Projects product completion date when possible. |
 |  |
| Dashboard Report -- Get busy people up to speed using this concise, one page report. Include Release status for one or many projects. Exports as a PDF for easy printing and emailing. | Sprint Change Report -- Details changes to the outstanding backlog including work completed this Sprint, work added/removed from the Product Backlog, and how re-estimation affected the Product Backlog. Exports to as an Excel spreadsheet for easy customization. |
* adapted from Mike Cohn's Alternative Release Burndown Chart
"Microsoft", "Windows" and "Excel" are registered trademarks of Microsoft Corporation.