Â
Attendees:Â Â Khalilah GambrellÂ
 Topics | Time | Presenter | Agenda/Notes |
---|
Announcements | 15 minutes | | |
Lotus Features (see dashboard) | 15 minutes | All | - New development remaining sprints: 1.5-2Â
- Please update your feature statusesÂ
- Stats
- 110 featuresÂ
- 31 features have the status In Progress that seem to represent new development/enhancements
- Any features at risk? If so, please add the label [lotus-at-risk] or move to Morning Glory (R2 2022)
- Split features as need.Â
- 28 features are not In Progress, In Review or Done
- AT RISK features: 13 of those features are new developmentÂ
- What is the impact to libraries planning to go live with Lotus release? Â
- What are challenges to addressing these features?
- Please attend Thursday 8am ET release weekly meeting if you have features at risk
|
User Acceptance Testing - Lotus > Brainstorming | 20 minutes | All | - Must start to incorporate UAT in our development. Cannot rely on Bugfest
Questions for POs - How can we make it easier to incorporate?Â
- CW: Task to include FOLIO implementers SIG or domain specific-SIGs (e.g. MM-SIG, RA-SIG, and Acquisition-SIG)
- JB/SB: When/how to take place?
-  DB: ~3 weeks before bugfest starts works. Give a week for UAT and then remaining weeks to address issues. Â
- KG: Depends - Test early and often is keyÂ
- JB/SB: What is the criteria to run a UAT?Â
- DB: New workflow/functionalityÂ
- DB: Significant change to an existing workflow/functionality
- DB: How long can I wait for UAT?
- KG: No/luke warm and fuzzies feelings
- Â
- What are the challenges?
- What functionality/workflow are you willing to commit to conducting UAT?Â
- Will a workshop to help folks with setting up UATs be helpful?Â
|