Skip to end of metadata
Go to start of metadata

Purpose

The Application Roadmap Committee is responsible for goal-setting, and prioritizing high-level application architecture for integration of Kuali application projects, and for an evolving roadmap for the future. This group defines overall ownership of shared services among the Kuali projects. The group defines work and priorities for Rice and cross application projects. This group works with the projects to coordinate working teams.

Guiding Principles

1. The primary function of Rice is to support application projects. The Application Roadmap Committee will be the primary body for prioritizing and deciding new projects, ownership of shared projects, specification development efforts, etc.

2. Kuali projects solicit investing partners to fulfill its primary and secondary functions. There are three types of partners: participants in single projects, participants in multiple projects, and participants in shared projects, such as Rice.

3. Kuali must remain up to date on its technology infrastructure over time, but technology changes that affect the application areas must be coordinated and prioritized through the application area Functional Councils in conjunction with consultation from technical architects. The functional needs of Kuali shall drive the technology direction.

Committee Structure

Membership

Membership shall consist of project managers, FC chairpersons, and an application architect appointed by the PM/FC chairperson for each project. The chairperson of the Kuali Application Integration Working Group shall be considered an ex-officio member.

Roles

Name

Voting Status

Number

Description

Chairperson

Voting or Non-voting

1

Manages meetings

Vice Chairperson

Voting or Non-voting

1

Manages meetings

Project Managers

Non-Voting

4

Committee members

FC Chairpersons

Voting

4

Committee members

FC Architects

Non-Voting

4

Committee members

KAI-WG

Non-Voting

1

Chairperson

Rice Lead Architect

Voting

1

Committee members

Special Topics Presenter

Non-voting

tbd

Provide expert input

One vote per project. Voting may be delegated to a representative of that project.
Rice will have one vote on the committee. Voting will be conducted using the Apache Foundation voting rules.

Commitment

Members of this committee are expected to participate in all calls and meetings. Each project is expected to have at least one representative on every call. Calls are expected to be twice per month, though more may be required. Calls typically last 1 hour. In addition, members may be called upon for additional work between calls and meetings typically on the order of 2-5 hours. Work above this level may require formation of a working group.

Process

Generally, this committee considers issues related to Kuali applications and to plan high level architecture and projects needed to further existing and new Kuali applications. These discussions are initiated by email by the ARC committee or Kuali projects and decided in committee meetings. Action items pertaining to issues and committee operation are kept and tracked. The committee may, at it's discretion create and dissolve groups focused on long term or on-going aspects of Kuali applications. Decisions will be made on a voting membership basis. Votes require a simple majority to pass. Tie votes do not pass.

Issue Management

The chairperson will be responsible for managing issues, tracking them and their resolutions. Jira will be used where appropriate to submit and track issues related to this committee. All decisions shall be recorded in meeting minutes.

Action Items

The chairperson will collect action items which include a name, a description, a due date, and a status. Items will be tracked from meeting to meeting. Jira will be used where appropriate.

Working Groups

Working groups may be created to accomplish specific goals and tasks or to handle on-going committee projects. These groups may be a single person or multiple persons. Work deliverables are either a report or a recommendation.  See ARC strategy work group, efforts in progress here.

The ARC Communications working group is to be led by the Vice Chairperson and focused on outward communication.

Communication and Transparency

Transparency

Kuali and it's related projects are all part of a dynamic open community approach to application development. As such, it is important that business conducted by the Application Roadmap Committee be conducted in a free and open manner, accessible to all. Specifically, this means:

  1. Minutes of all calls and meetings will be kept and published in a public place (Google Docs).
  2. Final documentation produced by the committee.

Communication

Communication out of the Application Roadmap Committee is primarily to the following:

  1. Technology Roadmap Committee
  2. Kuali Rice Board
  3. Kuali Executive Director
  4. All functional councils and boards

Outgoing communication shall be:

  1. A response to a request
  2. Reports (to be determined)
  3. Internally generated questions or requests.

Incoming communication shall be:

  1. Requests from other Kuali committees or boards.
  2. Inputs can come from working groups.