[Story] Bi-weekly report on platform activity

[angelcardoz]

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

• As an internal stakeholder, I want to receive a bi-weekly update on platform activity, 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 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:
  • Name of institution that visited the platform.
  • Number of times each user visited the platform.
  • Duration of each visit.
  • Whether the user has uploaded a test file.
  • Date of last visit.
• Error Handling: If there is an error generating or sending the report, an alternative email should be sent notifying the Scrum Master and Product Owner of the issue.

Technical tasks

Developers should create technical tasks and add links (below) prior to sprint planning.

Front end

• Task (link)
• Task (link)

Back end

• Task (link)
• Task (link)