Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

A detailed schedule of project activities can always be found in the Project Calendar on U-KNOW.

Project Assumptions

The successful completion of the Drew 360 project within the established time line and budget is based on adherence to the following assumptions. Any deviation from the project assumptions due to critical institutional need would affect the project budget and timeline and therefore must be approved by the Executive Steering Committee and would involve budget and timing contingencies.

  • The Banner implementation will be 'vanilla' – no modifications of the program source code will be made.
  • The project will be limited in scope as described under Project Scope, which will include replacement functionality and other enhancements specifically indicated; Other approved initiatives will be included in not-phase-one planning. Given the necessity of meeting the implementation time-line in order to conduct the University's business, replacement functionality will receive the highest priority.
  • Replacement functionality refers to the ability to achieve required business objectives, but not necessarily to replicate current procedures. Assessment and improvement of practices and policies is expected.
  • No development, modification, or report development will be done on AIMS except as required to comply with federal and state regulatory requirements.
  • Given the necessity of meeting implementation goals to support the University's mission, the Drew 360 project and its associated components will be University Technology's highest priority.  New projects that compromise the resources of the project, or major upgrades to enterprise applications supported by University Technology and not identified in the project scope, with the exception of security patches or upgrades mandated by vendor support policies, will not be undertaken. 
  • Interfaces will be written as needed to achieve continuity and maintain functionality through the implementation cycle.
  • Printing of reports and forms will be done locally in user offices using a laser printing strategy.
  • Ad hoc reporting capabilities will be available to end-users.
  • Training will be conducted using a "train the trainer" model. Functional consulting will include training for the project teams. End-user training will be conducted by University staff in functional offices with the assistance of ETC training resources.
  • The Data Standards team will be responsible for establishing policies and relevant standards for data entry, including the use of shared codes.
  • Project documents will be posted on U-KNOW.

...