Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The Submitter presents at the schedule time to the Product Council.

    1. This presentation is a time for Product Council members to become familiar with the new functionality, understand how it works, and how it impacts current functionality. Product Council members can also review the recording and materials asynchronously.

    2. The Product Council members will strive to see how this new functionality fits into FOLIO as a whole and as an international product.

  2. The Product Council decides, using its standard protocols, to accept, accept with a follow-up, or reject the new functionality under review within 2 weeks after the presentation. The following statuses can be assigned:

    1. An evaluation where all criteria are met will typically result in the Product Council’s Endorsement of the new functionality.

      1. The JIRA issue transitions from UNDER REVIEW to APPROVED.

    2. An evaluation where some criteria are met will typically result in an accept with a follow-up:

      1. Because Product Council reviews should occur early in the development process, not all intersections might have been seen before the review. A follow-up allows the Product Council to reach out to additional stakeholders and work collaboratively with the Submitter on questions that arose during the review.

      2. The JIRA issue transitions from UNDER REVIEW to APPROVED WITH FOLLOW-UP

    3. An evaluation where none of the criteria even after the presentation are met will typically result in a status of rejectedcancelled or resubmission. The Product Council will work with the Submitter to understand how to ensure all criteria are met.

      1. The JIRA issue transitions from UNDER REVIEW to REJECTEDCANCELLED or SUBMITTED.

  3. Timeline: JIRA issues needs to pass to the next step within two weeks after submission. If that deadline falls on a holiday or weekend, then the week deadline is the next business day.

...

  • If there is a follow-up, the Evaluator will contact the Submitter, and a mutually suitable time for the follow-up will be scheduled.

    • For a follow-up, the Jira Issue is transitioned from APPROVED WITH FOLLOW-UP to REVIEW.

  • Timeline: JIRA issues needs to pass to the next step within two weeks after submission. If that deadline falls on a holiday or weekend, then the week deadline is the next business day.

Resubmission or

...

Cancelled Status

  • If none of the criteria are met even after the presentation, the Product Council will work with the Submitter to understand what is needed for a re-evaluation. The Submitter can also elect to withdraw cancel the submission.

    • The comments section of the JIRA may be used for this purpose.

    • If a meeting is required or desired, it's the responsibility of the Point of Contact to find a time that works and set the meeting up with the Product Council.

  • If the Submitter resubmits, then all issues are resolved and the Submitter requests a re-review.

    • JIRA workflow: the ticket is transitioned from REJECTED REVIEW to SUBMITTED

  • The Submitted can also elect to withdraw their submission.

    • JIRA workflow: the ticket is transitioned from REVIEW to CANCELLED

  • Timeline: JIRA issues needs to pass to the next step within two weeks after submission. If that deadline falls on a holiday or weekend, then the week deadline is the next business day.

...