Project Management Best Practices

Supporting Strategic and Service Excellence Across Campus

Explore:

Introduction

Strategic projects drive continuous improvement and service excellence across the university.

The University of Illinois is committed to administrative effectiveness, service quality, and resource stewardship across the university. To achieve these goals, colleges, departments, and units across campus will need to undertake a number of projects and initiatives to introduce greater efficiencies in how we do our work.

Whether you’re launching a new initiative or advancing an ongoing project, the resources below outline best practices to guide your team through every stage — from project definition to completion and reflection. As part of this ongoing effort, the Service Excellence Team for Best Practices has identified a set of practices that have been found to be key contributors to success.

The guidance on this page provides recommendations for structuring a team, completing milestones, communicating with stakeholders, sharing information, and project management, with links to helpful resources and templates.

Please note that the guidance and instructions provided are not mandatory but are intended to assist you and your team.

1. Getting Started with Your Project

Successful projects begin with a clear understanding of goals, scope, and responsibilities.

Key steps to begin:

  • Engage your sponsor: Establish regular check-ins and clear communication expectations.
  • Define your project: Identify goals, expected outcomes, and how success will be measured.
  • Build your team: Select members with the right expertise and clarify roles early.
  • Develop your charter: Document scope, objectives, timeline, and key deliverables.
  • Plan the budget. Estimate staffing, technology, and any expected expenses during project scoping. Expenses should be included in your project proposal and are the responsibility of the sponsoring unit. See the full Budget & Resources section for details.

Project Phases

Standard project management methodologies organize a project into five phases: Initiating, Planning, Executing, Monitoring and Controlling, and Closing.

  1. Initiating Initiating is the phase in project management where the project’s purpose and feasibility are defined. During this phase, key stakeholders identify the project’s objectives, scope, and deliverables, culminating in the approval of the project charter and the authorization to proceed to the planning stage. Key step:
    • Outline project goals:
      • Review the project’s proposal, objectives, and deliverables. This phase involves outlining the project at a high level and obtaining approval.
  2. Planning Planning is the phase in which detailed strategies are developed to achieve the project goals, including defining the scope, objectives, deliverables, and timelines. This information is captured in the project charter and is agreed upon by the project team before work can begin. Key step:
    • Current-State Review
      • Understand the current state by identifying pain points, gaps, and root causes within the current process. Categorize and prioritize issues to ensure agreement on the project’s needs.
      • During this phase, it is also important to make a decision about which project methodology will be used (agile, waterfall, or hybrid), as this will influence the cadence of communication in the executing phase.
    • Validate and confirm goals and objectives
      • Conduct detailed planning to validate and confirm the project’s scope, objectives, and deliverables. Outlining the requirements for the project.
    • Project Plan
      • Create a plan to complete the project within a specific time frame, with clearly defined phases, milestones, and designated resources.
  3. Executing This phase focuses on implementing the project plan, coordinating resources, and carrying out planned activities. Key steps:
    • Resource allocation and task coordination
      • Distribute resources according to the project plan and coordinate team members’ activities, ensuring that tasks are completed in sequence and interdependencies are managed smoothly.
    • Communication
      • Maintain clear and consistent communication channels among project stakeholders to ensure everyone is informed about progress and any issues.
  4. Monitoring and Controlling Determine if the project meets the requirements outlined in the action plan, including quality, performance standards, and progress. Addressing risks and making necessary project adjustments to achieve project objectives. Key step:
    • Monitor and track project progress, quality, risk, and performance
      • Track project progress against the plan and milestones to ensure timely completion.
      • Monitor resource utilization and adjust allocation as needed to optimize efficiency.
      • Implement change control processes to manage and document any changes in project scope, schedule, or resources.
  5. Closing Confirm that objectives have been met, complete the final report, and formally meet with the team and sponsor to close the project. All project activities are finalized, deliverables are handed over, and the project is officially closed.

Team Roles and Responsibilities

Project Team Composition

RoleResponsibility
SponsorA sponsor is a senior manager or leader who is responsible for setting the strategic direction of a project, overseeing progress, and ensuring achievement of objectives. The Sponsor assumes responsibility for decision-making and active championing while serving as a link between the project manager/team and other stakeholders.
Project ManagerThe project manager oversees the day-to-day operations of a project team and is responsible for defining the project’s scope, objectives, and deliverables. The project manager supports the planning and monitoring of a project, ensuring the timely completion of all deliverables and assessing/ managing risks and changes.
Team MemberA team member is responsible for executing and completing tasks and collaborating with other team members. A team member should maintain consistent communication with the project manager to provide progress updates and potential risks. Depending on the type of project, team members may include professionals such as business analysts, developers, communications specialists, and others with specialized skills needed to accomplish the project’s goals.
StakeholderA stakeholder is an individual or group that has an interest or influence in your project. A stakeholder can impact or be impacted by the outcomes of your project.
Ad Hoc Team MemberA person with expertise or knowledge in a particular area who is brought in throughout the duration of your project to provide additional guidance or support.

Team size can have a significant impact on the success of a project. This will vary depending on the project’s scope and the number of tasks. When deciding who should be on the project team, consider the number of tasks to be completed, how information will be communicated to team members, and the level of accountability needed to ensure project success.

RACI Charts

RACI charts are created in a grid or matrix format and can be easily made in Excel. An example of a RACI chart can be found here.

RACI charts are a useful tool for clarifying roles and responsibilities within a team by identifying who is Responsible, Accountable, Consulted, and Informed for any given task or phase of the project.

  • R (Responsible): This is the person(s) who completes the work or task.
  • A (Accountable): This person is the owner who delegates the work and has the ultimate authority to sign off on the final result. Note: There should only be one Accountable person on a project team.
  • C (Consulted): These are team members who are subject-matter experts or stakeholders who provide input before the work is finalized.
  • I (Informed): This person or group is those who need to be kept in the loop on project progress or updates, but aren’t actively involved in the work.

Having a RACI chart is helpful in many ways:

  • Clarifying Roles: RACI charts will clearly identify everyone’s level of involvement and accountability for tasks and phases throughout the project. Having a RACI chart will be especially helpful for anyone who joins a project after it has already begun, helping them quickly understand their role and those of others involved in the project.
  • Understanding Time Commitments: Each team member will be able to clearly see their level of involvement as the project moves through different phases. This will help team members to manage time expectations and commitments better.
  • Identifying Points of Contact: Establishing who is responsible and accountable for each task makes it easier to know who to contact when questions arise.
  • Meeting Efficiency: Team members will be better prepared for meetings as everyone will have a better understanding of who is responsible for what and know what they will need to have ready for any given meeting.

Templates and Resources

  • Project Charter Template
  • Project Proposal Template
  • Sample Charge Letter

Tip: A kickoff meeting with your full team and sponsor helps align expectations and confirm priorities before work begins.

2. Core Best Practices

Project management is more than tracking tasks — it’s about aligning people, processes, and goals.

Keep these best practices in mind throughout the project lifecycle:

Set Clear Priorities

Establish the project’s scope, desired deliverables, and definition of completion. Gain agreement across all stakeholders to prevent scope drift. The project charter is the best resource for this practice.

Define Roles and Responsibilities

Clarify each team member’s role and level of involvement (Responsible, Accountable, Consulted, Informed). Use a RACI Chart Template to document this early.

Prioritize for Impact

Evaluate opportunities using factors such as importance, risk, impact, and cost to focus resources effectively. Identify “quick wins” to build momentum.

Communicate Consistently

Share updates regularly, engage stakeholders at key points, and document decisions. A Communication Plan Template can help structure this effort.

Engage the Campus Community

Include diverse perspectives to ensure your project reflects campus-wide needs. Invite feedback during review or testing phases.

3. Tools & Templates

Resources for each stage of your project

Project PhaseTools & TemplatesDescription
Initiation & PlanningProject Charter / Proposal / Charge LetterDefine purpose, scope, and governance.
Execution & MonitoringRACI Chart / Meeting Management Guide / RAID-C LogClarify roles, manage risks, and track progress.
CommunicationStakeholder Analysis Template / Communication Plan TemplatePlan engagement and communication cadence.
Closure & ReflectionClosing Report / Lessons Learned TemplateSummarize outcomes, impacts, and improvement opportunities.

Pro Tip: Keep your project documentation organized in Microsoft Teams using consistent folder structures (e.g., “Planning,” “Execution,” “Final Reports”).

4. Budget & Resources

Plan for people, time, and costs early — it improves feasibility and reduces surprises.
Budget or funding requests for project-related expenses should be discussed with your unit’s budget office.

Common resource categories

  • Resource Hours: Volunteer contributors or dedicated staff time.
  • Financial: Meeting/venue fees, supplies, vendor contracts, software licenses.
  • Technology: Tools, software, integrations, or development support.
  • Information: Data access, reports, or subject-matter expertise.

Compliance & Data Management

Ensure accessibility, privacy, and security at every step.

Often times, data accessibility, privacy and cybersecurity are overlooked in the early planning stages of projects, however it is a crucial piece and legal requirement to ensure the success and applicability of projects on campus.

Accessibility

Information and technology must be accessible to individuals with disabilities and project teams should keep accessibility requirements in mind during their planning and development. To learn more about accessibility requirements at the University of Illinois, please see the Digital Accessibility Policy, contact the ADA Coordinator Office with any compliance questions, and refer to the following university resources:

Privacy

All technology services and information must be developed, collected and managed in compliance with university policies to ensure that individuals’ and groups’ privacy is respected. Reach out to the privacy team (privacy@illinois.edu) with any questions. To learn more about privacy at the University of Illinois, please refer to the below resources:

Cybersecurity

All information technology must adhere to the cybersecurity standards, controls and policies. The cybersecurity team (securitysupport@illinois.edu) is available to consult on any questions related to implementing these controls and best practices.

Visit cybersecurity.illinois.edu for services and tools. Resources include:

Data Management Plan

  • Initiate & Manage: Have one point person primarily responsible to organize project files within Teams and manage access for other members/contributors. This is usually the project lead or project manager but can be a designated team member.
  • Define: Determine what data will be acquired or generated and establish a structure early in the project to facilitate team effectiveness. It is recommended data be organized by phases of the project.
  • Security: If you will be collecting or viewing high risk or sensitive data, consult with experts to confirm your data storage and access plan is acceptable.
  • Timeliness: Though it may be challenging, post templates, drafts and final documents throughout the project as work progresses.
  • Other Best Practices:
    • When possible, use common file formats such as Word (.docx) for documents, PowerPoint (.pptx) and Excel (.xlsx).
    • For other file types, such as Visio flow diagrams, Project files, etc., consider saving both the original and a PDF copy for those that may need to view without that software.
    • The project team may have access to drafts, in-process and revisions of files, but consider having a separate folder for “final” or “official” reports that will be shared or for easy future reference after project completion.
    • Long term management, archiving and final repository of Operational Excellence projects will be the responsibility of the SPMO.
    • The following resources are focused on research data management but may be a useful reference:

Reference: Data Management Planning

6. Continuous Improvement

Capture insights for future success.
Closing your project isn’t just about finishing tasks — it’s about reflecting, learning, and applying insights to strengthen future work.

Lessons Learned

Document what worked well, what challenges arose, and what could be improved.

  • Use the Lessons Learned Template
  • Schedule a post-project check-in with your team and sponsor
  • Share learnings with the SPMO to support institutional improvement

Closing Report

Summarize achievements, scope changes, and measurable outcomes.

  • Use the Closing Report Template
  • Include key deliverables, results, and recommendations
  • Note follow-up opportunities or next-phase projects

Connect with the SPMO

Need support with project setup, templates, or facilitation? The Strategic Project Management Office is available for consultation and guidance.

Contact: spmo@illinois.edu
Learn more: Strategic Project Management Office Home

Strategic Project Management Office
505 E. Green Street, 2nd Floor
Champaign, IL 61820
Email: ovcas-spmo@illinois.edu
Log In