Skip to end of metadata
Go to start of metadata

Mission

The mission of the Kuali Student (KS) Implementation User Group (IUG) is to provide a forum for both internal and external members of the KS project to engage and support one another in their existing and upcoming KS implementations. To this end, the group is designed to include existing partners, Kuali Commercial Affiliates (KCAs) as well as non-participating parties interested in the exploring KS. Members of the IUG can be from implementation teams on each of the KS partner institutions, KCAs, as well as from non-member institutions seeking more information. The goal is to collectively formulate implementation strategies and approaches, help each other with functional and technical how-to’s, share resources, lessons learned, and best practices. The group is intended to address day-to-day issues and concerns with implementation of Kuali Student as opposed to strategic functional and technical direction of KS Development which should be addressed by KS Functional Council (FC) or Project Advisory Group (PAG). Generally if the IUG finds, collectively, that KS Development has not adequately addressed an issue, concern or request they should be taken up with KS Functional Council (FC) or Project Advisory Group (PAG).

The group’s second mission is to provide a method to reach out to potentially interested universities and provide them with information on the capabilities, requirements, and available implementation methods for KS. The IUG would also be the appropriate forum to develop, maintain, and direct functional capabilities demonstrations, test-drives, and other outreach and demo tools. Fulfilling the mission will include the development of lessons learned, project sizing templates, and information on CSA offerings and capabilities.

Responsibility

  • Educate: Provide information and lessons learned from existing KS implementations
  • Advice: Offer guidance to institutes interested in KS
  • Outreach: Coordinate outreach efforts and answer questions from potentially interested parties
  • Test-Drive: Oversee the development and maintenance of “test-drive” sites. This includes simulation of appropriate aspects of implementation for others to learn from
  • Feedback: Advocate for functional and technical issues encountered by implementation teams.

Membership

Each institution that is part of the Kuali Student consortium should put forward a representative for the IUG. Institutions are allowed and encouraged to have more than one representative at any meeting of an IUG. KCAs are welcome and encouraged to attend. Members from outside the consortium are welcome and encouraged to participate.

To find out more about how to sign-up for the mailing list, see our membership page.

Monthly Meeting

The IUG will formally meeting once per month, with each meeting being focused on a preset topic based on feedback from the community. Members wishing to participate will be asked to submit questions, comments two weeks ahead of time in order to have answers available at the meeting. At the meeting, as appropriate, a demo, presentation, and/or Q&A session will be held on the topic. If time permits, general conversation can take place. As a secondary purpose, the meetings can serve to update members on the progress and status of individual implementations and/or the national project efforts.

Desired Product Development

Besides the monthly meeting, the members of the IUG should be engaged in a number of related projects which, while at times related to monthly topics, are developed outside the monthly meeting cycle. The expected work-products, in order of priority are:

  1. Functional Lessons Learned – Develop and maintain a document listing functional lessons learned to be available for future implementing institutes. Topics include, but are not limited to, data analysis, course rules design, workflow strategies, etc…
  2. Technical Lessons Learned – Develop technical lessons learned to assist implementing universities understand and plan for some of the technical challenges they may face. This document would also advice the development team of potential issues with easy of implementation in future products.
  3. Project Sizing and Roadmap Plan – Develop a set of baseline documents to assist universities interested in implementation with planning and sizing the effort. The documents would provide resource needs, timelines, and variables that impact the implementation effort.
  4. Test-Drive Site – Coordinate the development site for demonstration and test driving the KS Curriculum Management and, eventually, Enrollment software. It is expected that implementing institutions will contribute resources and time towards hands-on sessions in a lab like setting for institutions and KCAs     

Potential Upcoming Topics

  • Lessons learned from implementers
  • How to deal with the data mountain
  • Configuring KS
  • Where to go for information
  • Addressing special courses (soft number, dissertations, internships, year-long courses, etc…)
  • Using CM to print your catalog
  • Sigma (Student Accounts)
  • Enrollment Status
  • Walkthroughs of specific aspects of CM implementation by implementing institutions, including data mapping processes and artifacts, data dictionaries, UI customizations, etc