In the traditional project management, organizations spend big amounts on project reporting and have dedicated people to monitor them. The efforts spent in accommodating and maintaining the fine-grained details of tasks to have minimum risk on the success of the project have lead to the rigorous nature of the project reporting.
In Agile, the concept of just enough or barely sufficient documentation also applies to the project reporting part. Different Agile methodologies may have different standards and artifacts to report the status of an Agile project. In Scrum, commonly we need reporting for following things:
Product backlog describes how the whole product backlog is progressing across Sprints, how much backlog has been completed, and how much backlog is still remaining to be completed. Looking at the remaining and completed backlog items, we know how many feature requirements are still to be completed by the team and the road map to complete the same. To map to...