1 / 9

Fundamentals of operational reporting

Fundamentals of operational reporting. Process. Requirements gathering. Requests open to everyone Justification of the request Which process is affected and how How did we live up until today What Why When. Spec. Written Signed off Defining Input Logic Output Users Frequency

barth
Télécharger la présentation

Fundamentals of operational reporting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fundamentals of operational reporting

  2. Process

  3. Requirements gathering • Requests open to everyone • Justification of the request • Which process is affected and how • How did we live up until today • What Why When

  4. Spec • Written • Signed off • Defining • Input • Logic • Output • Users • Frequency • Commitment for User Acceptance Test • Acceptance criteria • Define criteria for issues(bugs) classiffication • What is a no-go (for example report runs for over an hour, or number is wrong) • What needs to be fixed after go-live • What is options • These criteria need to be accepted by requestor.

  5. Test plan • Written before test starts • Accepted by the customer • Same for Func test and UAT (in terms of key go-no go test cases). • That helps to fall back if UAT shows different results than Func Test. • Data prepared before test starts • Ideally data can be re-built over and over

  6. Test • Functional test • Performed by developer and filed to show compliance with the spec • User Acceptance Test • Performed by requestor and signifies acceptance • Issues • Need to be classified according to the definition above • Prioritized (when) • Closure of issues needs to be tested and signed by the customer.

  7. Test execution • Users need independent test scripts with data • Every test result need to be filed • PM has to monitor progress to make sure all tests are done before users fly back to their offices • Issues need to be reviewed with users and developers together and triaged • Fixes has to be tested the same day.

  8. Landscape

  9. Tools to build reports • SAP • Winshuttle allows automation and interfaces Excel to SAP • Talend Open Studio • TOS allows a very casual user export and import data to SAP/SFDC and other systems • And also Excel

More Related