PAY OCM - API vendor change communications plan
Open
OCM
Pay
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Create a change communications and engagement plan for API Vendor Changes.
Determine communications plan for each interested party - lawfirms, API vendors and eventually internal staff BCROS support teams.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.