Agile Scrum methodology does not use reports.
Do you agree with this statement?
Can Product Backlog, Sprint Backlog or Sprint Burn Down Charts be considered as reports?
The Scrum framework was designed from the start to be transparent.
There are three critical components to this:
It is also worth noting that the Product Owner is the person most interested in this information as they own the product. They are involved every day with the team and so have a deep understanding of what is going on.
The issues that occur in Scrum reporting tend to happen due to flaws in the way the Scrum framework has been implemented. For example, if not all interested stakeholders are attending the sprint reviews then there can be misunderstandings. Also, if the Scrum Team is not allowed to be self-organising then there may be some concerns over communication with the technical managers.
Having said that, many teams use reports to supplement the Scrum transparency.
The two most common reports are:
Mike Cohn talks about the sprint summary here.
Product updates have many formats. The most successful ones I have seen are clear and consise summaries of work in progress and planned work that are targetted at people of all levels of technical knowledge (including business users that are non-technical). I have worked with Product Owners that write visually attractive product updates that effectively market the Scrum Team to those that do not regularly attend sprint reviews.