Page Comparison

Present the page that shows the budget and its history: FOLIO AWS Budget

Notes:

Elastic Search will impact costs and may have an effect on the budget (i.e. may need to request an amendment to the budget)

Also need to follow up on the Performance Environments that Martin presented on (i.e. what's the cost implication and do we need to request more budget) 

We'll schedule a conversation about how to establish and manage a policy around changes that might impact our budget.

Craig met with the implementers group last week. He'll walk us through his write-up.

Discussion:

• "Pain level" overall for implementers in the 6-8 range
• Discussed the value of having a PO to drive progress (but the challenge of PO bandwidth)
• Discussed the problem with diku_admin as a crutch - teams should be creating their own users with the minimal necessary permissions. 
• The call to build out Karate tests aligns with Anton's drive to increase integration/Karate test coverage
• Zak wrote the script that pulls out all necessary permissions mapped to personas that can be reviewed/relied upon to make sure the right permissions exist for the proper functions

Next Steps:

1. Ask POs to refer to/use the central repository with different permissions that need to be considered when testing (first section of Craig's doc) and abide by the "users granted only the minimal set of permissions" approach and stop using diku_admin for testing. 
2. Ask POs to address ambiguous terminology through documentation (likely new docs)
3. Craig will give the same presentation to the POs at a future PO meeting, and will ask the POs for the PO who will take the lead

We didn't get to this:

The TC needs to develop a set of criteria/checklist to be reviewed when new technologies are suggested/requested... so that we can make consistent and transparent decisions. Our brainstorming ideas include: