Functional User Group (FUG): Difference between revisions

From CAPipedia
m (DavidDlugiewicz moved page FUG Meetings to Functional User Group (FUG) without leaving a redirect)
No edit summary
Line 6: Line 6:
* Each request will be evaluated by at least 2 FUG members and discussed during the bi-weekly FUG meeting.  
* Each request will be evaluated by at least 2 FUG members and discussed during the bi-weekly FUG meeting.  
* Recommendations regarding viable project proposals will be provided to the ITSC for scoring and prioritization.
* Recommendations regarding viable project proposals will be provided to the ITSC for scoring and prioritization.
[[:Category:FUG Meeting Notes]]

Revision as of 15:18, 23 February 2021

Functional User Group (FUG)

The FUG consists of a Chairman and a Representative from each Region

How it works

  • The primary responsibility of the FUG to identify, evaluate and assist in the prioritization of field generated requirements based on their functional expertise and broad experience with eServices.
  • Help desk tickets for IT enhancements and fixes with viable workarounds are automatically routed to the FUG Chair who will coordinate the group’s evaluation.
  • Each request will be evaluated by at least 2 FUG members and discussed during the bi-weekly FUG meeting.
  • Recommendations regarding viable project proposals will be provided to the ITSC for scoring and prioritization.

Category:FUG Meeting Notes