Product Owners
Getting Started for Product Owners
Scope of engagement
Product Owners are supplied to the project by various vendors and academic institutions, however, Product Owners support the entire community. This means:
- Listening to all perspectives and working with the SIGs to design common solutions that meet all needs
- Capturing backlog items proposed by community members as UXPROD features so they can be ranked and prioritized for developmentÂ
- Verifying with the broader community before making changes requested by a single institution
- Monitoring support issues and working to support all production customers with critical bug fixes
- Working with other Product Owners and SIGs to support the needs of adjacent domains and workflows
A current directory of product owners can be found here: Directory of Product Owners by Area of Focus
Product Owner Meetings
- There is a group meeting for Product Owners every two weeks. Â
- There is also a private #product_owners Slack channel
(Note: Contact Khalilah Gambrell for more information about these meetings/channels.)
FOLIO is looking for Product Owners
Joining FOLIO as a product owner is a great way to make a big impact on the project. You will:
- Get involved in the FOLIO community
- Build your network
- Develop new skills
 Interested? Please review the below list of long-term and one-time opportunities. If you would like more information, please contact, Lead FOLIO PO, Khalilah Gambrell
Long-term Projects and Opportunities: Product Owners NeededÂ
We are always looking for good POs for the following areas. Time commitment is a minimum of 6 months.Â
Priority | Need | Description | Required skills | Minimum - Time frame |
---|---|---|---|---|
Course Reserves app |
|
| 5-8 hours a week | |
Service points and Locations |
|
| 5-8 hours a week (depends on if a feature is being developed) | |
Circulation: Loans, Circulation rules and loan policies, Check-in, Check-out, Loan information on Item Details |
|
| 10-15 hours a week | |
Circulation: Fees/Fines | Current product owner will be leaving the project and we are looking for a person who wants to continue to support FOLIO's fees/fines capabilities.
|
| 10-15 hours a week | |
Item States |
|
| 5-8 hours per week | |
Circulation: Requests app | Looking for a person to manage the requests app and workflows.Â
|
| 10-15 hours a week | |
Circulation: Lost items | We are looking for a product owner who canÂ
|
| 5-8 hours a week | |
Circulation: Patron/Item blocks | Current product owner will be leaving the project and we are looking for a person who wants to continue to support FOLIO's fees/fines capabilities.
|
| 10-15 hours a week | |
Accessibility | Need a product owner who can lead efforts for POs/development team to
|
| 5-8 hours per week | |
Inventory Search Enhancements | Need a product owner who can define inventory search requirements now that the app's search is powered by Elastic Search.Â
|
| 10-12 hours a week | |
Patron APIs for discovery systems | Need a person to
|
| 8-10 hours a week |
Micro-volunteer (one-time commitments) Projects and Opportunities
This list represents one-time commitments projects and opportunities. Commitment: provide project completion due date.Â
Project/Opportunity | Description | Skills | Can be done by a group? |
---|---|---|---|
Acceptance Testing: Lead/conduct Business Acceptance Testing per feature/workflow | FOLIO is committed to delivering quality features that are well received by the community. We need people who can lead business acceptance testing (BAT) at least once at the mid-point of a release to ensure that development is on the right path well before bugfest. Lead/conduct BAT responsibilities
|
| Yes |
User research: Organize/conduct FOLIO Usability survey | Current FOLIO UX has been in place for over five years, there is a need to reassess UX and understand if the UX supports users' expected workflow. A FOLIO Usability survey will help POs and developers understand what changes are needed at the platform level and why. Anyone interested in organizing and conducting a surveyÂ
|
| Yes |
User research: Conduct usability testing per feature/app/workflow |
| Yes | |
Market Analysis: Conduct market intelligence per feature/app/workflow | For FOLIO to continue to increase it's reach, it needs to compete with existing library management solutions. Analysis should cover multiple areas:
Note that comparing all of FOLIO to existing solutions is a large task, community members should just focus on areas of expertise. Doing so will make the time and effort manageable while encouraging many to take part. |
| Yes |
Requirements Analysis: Define shortcut keys requirements |
| Yes | |
Requirements Analysis: Peer review requirements per feature | Product Owners gather requirements in a SIG and / or a working group. Product Owners then create requirements with enough details for developers to create the functionality during an upcoming sprint. Prior to developers building the features, it would be ideal if an SME were able to review | Yes | |
Support: Triage (feature/workflow) bugs per feature/app/workflow | Review logged defects at a regular interval (weekly) to help verify and document steps to verify if the issue is reproducible, If it's a bug or a feature enhancement as well as prioritize severity of issue and provide explanation for the expectations of correctness |
| Yes |
Product Analysis: Document/share workarounds per feature/app/workflow |
| Yes | |
Product Analysis: Document (feature/workflow) gaps per feature/app/workflow | Yes | ||
QA: Write/Revise tests cases for specific area/workflow | Create manual test cases that can be run during bugfest prior to each release |
| Yes |
Documentation: Update User Design online documentation | Yes | ||
Documentation for FOLIO applications. | Detailed documentation about application features that cover usage as well as how the app works and what data is updated within the system. | Yes | |
Use cases | An SME to create thorough documentation that present the details workflows and situational needs of daily work needed to support daily operations in FOLIO. These are expected to be focused but exhaustive. The can for as guidance in detailed requirements gathering as well as automated test cases and UAT. |
| Yes |
Automated testing - test case creation | Cypress and Karate test run nightly generating lists of issues found for developers to review and fix. FOLIO has several thousand that need to be maintained by improving existing cases for better coverage as well as the creation of new test cases. These allow FOLIO to catch defects early in the development process well in advance of bugfest.  |
| Yes |
Automated testing - existing test case review | Cypress and Karate test run nightly generating lists of issues found for developers to review and fix. FOLIO has several thousand that need to be maintained by improving existing cases for better coverage as well as the creation of new test cases. These allow FOLIO to catch defects early in the development process well in advance of bugfest. The goal here is to review and flag existing cases for completeness and correctness. |
| Yes |
Test Data Set Generation | Test data is needed to fully exercise the FOLIO code and test cases. Current data isn't updated and old. Test cases may not be catching issues due to this. |
| Yes |