At my company, I develop and maintain all the operational reporting used by management to run the business. There is no reporting position on the application development team. I've taken it upon myself to step in and attend design review meetings to give input to the development team on how changes will impact reporting, consult on how modify designs to avoid impacting existing reports and what I will need in new development to be able to report on the data. It's been my experience that reporting is a key functional position on an enterprise application development team. I'm hoping to find some documentation that supports that concept as an industry standard or Best Practice. Can anyone help me there?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
I don't see why you are treating "reporting" differently from any other application.
It has users, it has requirements, it has interfaces to other systems.
So treat it like any other system. Identify the stakeholders, lock down the requirements and establish formal interfaces with your data providers.
Perhaps, more importantly, define it as a proper "project/application" within your company bureaucracy so the other teams must take into account the impact of their changes on your system. You need some sort of official status to force the other teams to comply with your interface definitions, and, go through the formal procedures when they want to change them.
If you're describing reporting functionality that generates reports on the basis of data that the systems generate, then it sounds like you're describing BAM or "Business Activity Monitoring".
Searching the web provided these two links, although I'm sure you can find many more by searching for some combination of "best practices", "BAM" and "Business Activity Monitoring."
BAM is often used together with a BPM engine, but that's only because BPM engines generate precisely the type of information that's meant for BAM.