Sinopia Product Owner responsibilities

During a Development Work Cycle

1. Test new features and bug fixes as they are deployed to the Development environment.
   • To keep track of what to test:
     • Ideally, test things as soon as they are deployed by keeping an eye on PRs as they are merged, and issues as they are closed, via the issue board or subscribing to github notifications. (To see if a merged PR has been successfully deployed to DEV: https://app.circleci.com/pipelines/github/LD4P/sinopia_editor)
     • Sometimes you'll want to review all issues / PRs completed since a given date. In Github, to search closed issues updated after a certain date, use a query like: is:issue is:closed sort:updated-desc updated:>=2020-09-15
   • You may want to use a sheet like this to track tests and results: https://docs.google.com/spreadsheets/d/1A_RiSJDTF40i_SdZNcYivED2G93iuh97fH-ex0e0gnc/
   • If the fix or feature passes your test, apply the "PO UAT Passed" label.
   • Identify good examples to show in a demo while reviewing and testing features and fixes.
   • Report any bugs found.
2. For each release, write text for home page with release highlights. Tech lead will ask for home page text when completing release checklist. Or PO can do PR for this file: https://github.com/LD4P/sinopia_editor/blob/main/src/components/home/NewsItem.jsx
3. Write release notes for this wiki page including known issues. Move older release notes to the earlier releases page.
4. Plan demo. It's helpful to write a demo script.
5. Record demo using Zoom or other screen capture tool.
6. Publish demo video to Sinopia playlist on Stanford YouTube channel. Add demo video link to release notes page.
7. Tell users about the release and invite feedback, on #sinopia Slack channel (LD4 Workspace) and user email list (sinopia-users Google group).
8. When appropriate (Work Cycle end for example) send summary to internal groups.

Ongoing responsibilities

• Manage user permissions: respond to requests from users to be added to a group in order to have edit permission; respond to requests from users to add new groups and to assign users to those groups. Can also proactively add new users to the "Other" group upon receiving Cognito notification of new user registration (see Send welcome email, below)
• Keep the Help menu in the Sinopia application up to date. To edit the menu, edit this page https://github.com/LD4P/sinopia/edit/master/help_and_resources/menu_content.html and submit pull request.
• With technical lead, manage the product backlog, including creating epics and prioritizing issues. We are using ZenHub, and the most recent board is: https://app.zenhub.com/workspaces/sinopia-fall-2021-61099a83af54cc000f437879/
• Facilitate the Sinopia User Group, or act as resource for the facilitator.
• Send welcome email to new users. (Notification of user registrations comes to PO email; check if user is newly registered or just resetting password; send welcome if new.)
• Monitor Sinopia communication channels and answer questions.
  • [email protected] email (This is a shared Stanford email and the recipients are managed via Stanford's account management page)
  • #sinopia channel in LD4 Slack workspace
  • [email protected] mailing list
• Monitor Sinopia usage statistics and create reports for project stakeholders as necessary, using the Actions / Metrics feature in Sinopia. Some earlier statistics are reported here on the LD4P3 wiki.