...
Join the SIG meeting that is appropriate to the area where you are working: Community Calendars
Sign up for SIG mailing lists so you get all the emails sent to the group(s): https://ole-lists.openlibraryfoundation.org/ Please sign up for the PO distribution list: folio_pos
FOLIO Slack channels for real-time chat are available at folio-project.slack.com. Anyone may request to join the FOLIO Slack channels using an automated web form.
...
FOLIO JIRA is the project's issue (bug, story etc.) tracker. Please sign up and then ask Kelly Drake /wiki/spaces/~kgambrell/overview or Jakub Skoczen for the ability to edit issues.
...
If your team needs a project that is not on the list, please request from Kelly Drake /wiki/spaces/~kgambrell/overview or Jakub Skoczen
JIRA contains planning backlogs (epics and features) in a project called UXPROD. Development backlogs (e.g. user stories, bugs etc) are maintained in other projects (eg. mod-users and ui-users).
...
- Detailed: https://issues.folio.org/browse/UXPROD-271
- Some detail: https://issues.folio.org/browse/UXPROD-145
- No detail: Lots of features have no detailed description at all. It's better to record a feature without a description than not recorded it at all!
- Feature estimates:
- When features are created, you should ask for them to be estimated (front-end estimate and back-end estimate)
- This will allow us to stay on top of our project plans and help SMEs make informed tradeoffs regarding what should be prioritized
TO BE REVISED: UXPROD Epic and Feature Workflow/
...
Status Anchor UXPRODWorkflow UXPRODWorkflow
| UXPRODWorkflow | |
| UXPRODWorkflow |
- Open: Feature is waiting to be picked up by PO.
- Draft: Feature is being worked on by the PO. Discussions are happening with the SIGs and sub-groups, mock-ups are being created. Analysis is underway.
- Analysis Complete: PO analysis is complete. Stories are written and mockups have been created.
- In Progress: Development is underway. It is often the case that we begin development on some aspects of a feature before the PO’s analysis work has been completed. Use your judgement as to whether the feature should be Draft or In progress in these situations. If a feature still requires a lot of stories to be written, you should probably leave it in Draft. If development has begun and you are confident that dev-ready stories won't be a blocker for development, go ahead and move into In Progress.
- In Review: Most or all stories in the feature are In Review (being tested)
- Closed: All stories in the feature have passed test and are closed. Feature is complete.
...
Each story should have one and only one linked UXPROD feature.
TO BE REVISED - Story and Bug Workflow/Status
The way "status" is used in JIRA differs depending upon whether you are working with development work items (like stories and bugs) or UXPROD features and epics. See above for the workflow for UXPROD features and epics.
...
- An important part of the PO role is to meet with the SIGs to gather product requirements
- The SIG(s) you work with will depend on the epic you are managing
- You are welcome to attend any SIG meetings to familiarize yourself with how they operate. If you are new to the project you might want to ping the SIG convenor convener in advance so they can introduce you at the beginning of the call.
- You can find a list of the SIGs with links to additional info (including the contact info for the SIG convenorconvener) here
- Each SIG has a folder on Google Drive. These will contain working documents and may have meeting recordings (though these are not saved consistently).
...
Questions about the Product Owner role or processes? Contact Kelly Drake/wiki/spaces/~kgambrell/overview
To see the latest screen designs for each area go to FOLIO UX Designs.
...