...
Contact Khalilah Gambrell for more information about these meetings/channels. If you are a Product Owner please do sign up for these.
Resources
- The FOLIO software development site is available at dev.folio.org.
- FOLIO uses discuss.folio.org for asynchronous messaging. The Discuss site is a web forum with categories, topics, and posts. Use Discuss for asking questions and recording discussions that require more than a few sentences.
- FOLIO uses wiki.folio.org to store documents with some permanence. FOLIO Special Interest Groups (SIGs), which are dedicated to specific functional areas or interests within FOLIO, have a space on the wiki.
- Join the SIG meeting that is appropriate to the area where you are working: Community Calendars
- 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.
- The FOLIO Google Drive has working documents for various project groups including most SIGs and the Product Council. There is a Product Owners sub-folder for our documents. Contact Anne L. Highsmith to gain access to the FOLIO Google Drive. Tell her you are a new FOLIO Product Owner.
- FOLIO JIRA is the project's issue (bug, story etc.) tracker. Please sign up and then ask /wiki/spaces/~kgambrell/overview or Jakub Skoczen for the ability to edit issues.
UX Design Requests
FOLIO UX designs are stored and accessible from a variety of different tools. This directory on FOLIO's google drive has more up-to-date mockups. Other mockups are found on the wiki. When working with a UX/UI designer it is suggested that the Product Owner:
...
- A feature is what an institution reviews to prioritize its needs for go-live and for tracking functionality planned in future releases. It is important that features are
- Clearly defined and written with the customer in mind.
- Describe the problem or need the features will address
- Describe the benefit(s) of implementing the feature
- Describe any risk(s) of not implementing the feature
- Describe any known dependencies
- Use the Template = UXPROD features as a guide
- Revise your features as needed so that institutions have an accurate understanding of what will be delivered for a release. A feature set to Closed are included in Release Notes. Example - Kiwi (R3 2021) Release Notes.
- Use of Labels
- Technical debt feature should have the label NFR assigned
- To allow a SIG to see which features are applicable to the SIG, consider adding the label
SIG Label Users usermanagement Resource Access resourceaccess Resource Management resourcemanagement Electronic resource management erm Metadata Management metadatamanagement Acquisitions acquisitions Data import data-import Cross Platform crossplatform
- The feature kanban board is here
- A simple list of features is here
- Example features:
- A feature is what an institution reviews to prioritize its needs for go-live and for tracking functionality planned in future releases. It is important that features are
...
The FOLIO wiki has a page in which manual testers and community members can report observations and issues which they aren't sure are actually defects. The page is Observations and Comments from Testers/Not Tickets page should be watched by all POs. If an observation has been added in relation to one of your apps, please review and follow-up as needed.
Additional Information
- For who is working on what, please see the Directory of Product Owners by Area of Focus.
- Questions about the Product Owner role or processes? Contact /wiki/spaces/~kgambrell/overview
- To see the latest screen designs for each area go to FOLIO UX Designs.
- To remain abreast of FOLIO news, visit folio.org/news. To remain abreast of FOLIO events worldwide, visit: events.folio.org.