Consolidated Reporting

The holy grail of reporting is to get “one version of the truth.” Yet, it’s so difficult to get this view across an entire project when work is conducted on similar artifacts, across a myriad of tools. For example, organizations may want to use the reports in their primary defect tracking tool to get a snapshot of the status of all defects reported during a release cycle. But unless the defect tracking tool gets real-time data from the tools the developers use to manage their work (such as issue trackers), the data in the defect tracking tool is either old or incomplete.

Of course, defects are just one artifact that is often being worked on by different team members, using different tools. Any tool that provides reports can only report on the information contained in its database, on the artifacts that it manages. However, when the systems are integrated and their artifacts synchronized, the reports those systems produce are enriched by the data from other systems.

Reviewing the other integration patterns provides a broader view of how useful it is to synchronize data from various systems of engagement with the systems of record being used to provide the consolidated reports.

Artifacts typically synchronized:

  • Defect
  • Story/Requirement
  • Ticket/Problem/Incident/Feature Request
  • Request/Backlog Item
  • Portfolio Item, Initiative
  • Epic, User Story, Task, Sub-task
  • Test Case