Institutional File Space Stakeholder Group Charter

With the Institutional File Space (IFS) deliverables driving the focus of the goals and direction of the group, the IFS Stakeholder group is lead by the Department providing the service. Tom Laughner of OIT's Central Computing Resources will be the Group Leader. Members in the IFS Stakeholder group should include:

· All service providers whose data are affected by the deliverable

· A representative sample of administrative and academic end users of the final deliverable

· A facilitator (could be the group leader or another committee selected facilitator)

Members of the IFS Stakeholder group can expect to provide feedback to the OIT on:

· Does the deliverable do what you think it should do in other words, the functionality of the deliverable. In the case of a prototype, does it look like needed functions have been included in the design. If not, please explain.

· How easy the deliverable is to use. In the case of a prototype, does it look like it will be easy to use? If not, please explain

· The ripples created by the development cycle of the deliverable. Do you think there are other processes or programs that haven't been taken into consideration by this project?

As members of the IFS Stakeholder group, members must agree to:

· Reach consensus, so that the recommendations and feedback carried forth from the IFS Stakeholder group are made by the group, for the group.

The Group Leader (Tom Laughner) will:

· Hold regular meetings and document the proceedings

· Document recommendations made by the group

· Have a published agenda for each meeting

· Document all decisions made by the group, including rationale

· Makes final decisions using recommendations and input

· Sign-off at predetermined project milestones, tasks, etc.