Formal Communities of Practice (fCoPs)
When the the IT Leadership Community of Practice (ITLCoP) charges a new formal CoP to do work, they select a leader to bring together the community and by provide the community with a clear and specific charge and a clear point at which the community's work is complete.
Anyone at the University who wants to be a part of that community and work on that initiative can join that fCoP. The fCoP will be self governing in that it will write its own formal CoP charter and figure out how it will operate.
Fiscal Year 2016 fCoPs
- Academic Technologies: Develop processes for selecting and testing new learning tools.
- Analytics and Data Integration: Build a foundation for data and analytics sharing.
- Application Delivery: Enable access to learning tools from anywhere.
Informal CoPs (iCoPs)
When a person or a group of people has a topic or a problem that they wish to explore, they may choose to form their own informal CoP. Members of informal CoPs are also responsible for writing their own informal CoP charter, but they do not have a charge and corresponding end date from the IT Leadership CoP.
Informal CoPs may exist for any length of time and work on multiple topics or problems concurrently or sequentially as determined by their members.
Examples of UMM iCoPs
Examples of U of M iCoPs
- Academic Technology Tools
- Business Intelligence
- Code People
- Computer Management
- Course Management System
- Exam Security
- File Transfers
- Research Data Management
- Service Now
An essential component to building University-wide IT alignment is creating a vibrant and active IT community. IT@UMN is a system-wide movement to build community among IT staff towards this goal—to take the 1300+ people who work in IT across the UMN system, and help them to identify as members of the same IT team.