1 of the 4 values of Agile is
Working Software Over Comprehensive Documentation
Reporting of any kind - physical or electronic - is a form of project documentation. It was observed that enormous amounts of time were spent on documenting the product for development. The list of such documents for example Technical specifications, technical requirements, technical prospectus, interface design documents, test plans, documentation plans was extensive and was a cause for the long delays in development.
Hence Agile Manifesto values documentation, but it values working software more. Agile does not eliminate documentation, but it streamlines it in a form that gives the developer what is needed to do the work.
As stated by others there is nothing specified in scrum guide to clearly tell who is supposed to do project reporting & hence its very important to know the whole context behind the need of Reporting - following are some key questions to consider
- what exactly are you reporting?
- Who is asking for such reporting?
- Are they not part of SCRUM team?
During any of your scrum retrospective meeting - you as a SM can bring this topic to brainstorm above points, uncover the need of such reporting, see if any gaps in team collaboration & communication etc.
And then as a SCRUM team you should be able to define who is supposed to reporting if needed after retrospection.