2022-03-28 BPL Governance meeting notes

Owned by Denise Kidd, created
Last updated: May 10, 2023
2 min read

 

 Participants

  • @Denise Kidd

  • @Colette Raphel

  • @Archibald, Jennifer (Unlicensed)

  • @Stephanie Davis

  • @Shawn Ryder (Unlicensed)

 Goals

A kick-off meeting to decide how we review articles in the business process library (BPL).

  • Do we want to collect a wish list? Where should it be located?

  • Design flows for reviewing new articles and reviewing articles after revision

  • Identify how we will collect feedback (in meetings, via comments, direct edits)

  • Establish submission deadlines to get articles produced/reviewed so that they can be reviewed prior to the next meeting.

  • Do we want to build in time each meeting to prioritize new articles for production?

 Items for follow-up

 

 Discussion topics

Item

Notes

Decisions

Item

Notes

Decisions

Wish List

Colette’s wish list - front desk guide (ask Olivia)

Stephanie - Calendar, Term config

  1. Denise will create a wishlist; submitters will put on list in Confluence. Done

New article review



  1. 5 is a reasonable number of articles.

Revised article review

 

  1. Substantive changes - different order, new policy/requirements, etc. We are ok with reviewing multiple times.

Feedback collection

 

  1. We will collect feedback via comments on articles (do not use inline comments, as they are not as visible as article comments).

Submission deadline for review

 

  1. Denise will submit articles for review 2 days after the previous meeting for review at the next meeting.

Review wish list for prioritization

 

  1. Twice per month review

Other notes

When we get to the point of allowing all staff to create articles, what’s the process by which articles will be reviewed? Process owner/article developer > Associate Registrar/immediate supervisor reviews

There’s a lot of Appworx/Ellucian documentation that needs expansion/review - need a mechanism to flag and workflow

Pull in S. Bautsch for these

When are we planning on rolling this out to the whole staff? Stephanie recommends we roll out based on role (lol). She suggested starting with catalog/curriculum and scheduling and roll out to RSS later.