Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
As an internal stakeholder, I want to receive an update on platform activity during sprint reviews, so that I can stay apprised of user engagement.
Acceptance criteria
Report Frequency: A report should be automatically generated and delivered every two weeks.
Report Delivery: The report should be sent via email to the Scrum Master and Product Owner's email address. A summary of the data provided will be published in the sprint review PowerPoint presentation.
Report Format: The report should be provided in clear and readable format, such as Excel, PDF and/or body of an email.
Cumulative Data Set: The data set should build upon itself over time, incorporating all previous data up to the current point.
Content Detail: The report should include the following details about platform activity:
Excel Sheet
Name and LEI of institution that visited the platform.
Whether the institution has uploaded a test file.
Date of last visit.
Summary for PowerPoint presentation
Number of people who hit unauthenticated homepage (Google Analytics data)
How many users reach the authenticated homepage (Not Started)
How many users have uploaded at least one file? (Submitted or beyond)
How many users have made it to the end of the process, sign and submitted. (Point of contact submitted, per institution at least one successful)
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
Acceptance criteria
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Front end
Back end