|
Team Interactions
Team Activities
A pilot is a development project and an implementation project at the same time. Both Campus Management and ProSAM are pilot projects, i.e., UM will be the first institution to "go live" with these products. Being a pilot site for these products presents certain benefits as well as challenges. The implementation schedule for each product will be dependent upon the corresponding development schedule; specifically, if the development schedule slips, then the implementation schedule may require adjusting. No ASAP template is available for Campus Management (CM), but where appropriate the ASAP methodology will be used as a guideline.
Each CM Core Team sub-area will identify areas for change, processes and issues that require investigation, e.g., how to handle the routing of applications for admission, and will appoint ad hoc teams as needed to examine these, identify options and propose solutions. These teams will consist of CM Core team members and pertinent CM/ProSAM Resource Team members. Teams will document their work using an agreed-upon standardized format. Teams will reach resolution in the time frame provided.
The accurate and timely delivery of financial aid depends upon careful coordination between the Financial Aid Office and a number of other departments on campus, such as the Bursar, the Registrar, and the Graduate School. Therefore, in addition to the project team members, other project stakeholders (part of the CM/ProSAM Resource Team) will be involved in discussions and decisions affecting the financial aid process.
Issue Resolution
Issues that are not resolved at the level of the ad hoc teams due to either a lack of consensus or the inability to decide in the time frame provided will be forwarded on the CM Core team that initiated the investigation. The CM Core team will decide whether the issue needs to be forwarded on to the Steering Committee for resolution or whether it can be resolved at the CM Core team level. While the ProSAM project team will make every effort to resolve issues which arise during the ProSAM implementation, any issues that cannot be addressed to the team's satisfaction will be forwarded to the Steering Committee. The Executive Committee will have final authority on all issues. Generally, the 48-hour rule will be used, i.e., critical issues that remain unresolved after 48 hours will be forwarded on to the next higher level.
Assumptions
- The UM academic community will be given the opportunity for adequate involvement in the Campus Management project, particularly with regard to all issues surrounding academic structure and curricular issues.
- A project portal will be established to provide timely information on project progress to the campus community. The project portal will include links to the organizational structure, the project charter and plan, and ongoing development documents.
- UM resources will perform most of the work, i.e., configure, test, and develop CM and ProSAM application modules. The use of consulting will be minimal.
- The Steering Committee will enforce a moratorium on legacy changes. Only externally-mandated work will be done.
- Current IT resources responsible for the support of the legacy system should be involved from the start to facilitate transition and conversion and to provide a good basis for future support, spread the workload, and foster good morale. IT resources will serve part-time on the CM Core and ProSAM teams with the exception of team leads.
- All team members, functional and technical, will receive appropriate SAP and Sigma training.
- Conversion methods will vary depending on the data, i.e., manual or automated.
|
