EIS Project Managment Principles & Priorities

Project Management Principles

2023-2027

As the College undertakes three large strategic projects over the next four years, Enterprise Information Systems (EIS) needs to allocate the vast majority of team resources to these efforts. To that end, EIS has established the following principles to guide and prioritize our work.

1. Don’t break the College and keep Hamilton operational. If a system or process is broken, EIS needs to respond and resolve it quickly. We must also maintain and protect our servers and processes keeping them stable and supportable by vendors.

2. Execute the strategic plan. Dedicate team resources to the Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and Identity and Access Management (IAM) campus priority projects.

3. Manage the project backlog. Continue to accept and prioritize project requests. This means that we can’t guarantee that we’ll be able to develop new projects and features. While it will be difficult to commit to specific timelines over the next few years, projects will be selected for development based on priority, size/effort, and available team resources. 

EIS Backlog Management Methodology

1. Projects will be selected for development based on priority, size/effort, and available team resources. 

2. Broken processes will be prioritized over clunky processes.

   1. A broken process doesn’t work. The product can’t be delivered on time and/or accurately and/or at all.

   2. A clunky process exists but stinks. Ultimately, a product can be delivered accurately and on time, despite inefficiencies, bugs, or process quirks.

3. Stop-gap solutions may be delivered in order to temporarily alleviate problems that may be solved in the ERP, CRM, and/or IAM solutions.