Description and Objectives

The project description should offer a broad overview of the project you propose. It should answer: what is the program or common thread? What students will the program or common thread serve? How is this program positioned within the College(s) it will serve? How will the College(s) benefit? 


The outcomes, by contrast, lay out a more specific vision of what success will look like for the project. Where the description provides a chance to articulate the big-picture change that your project will seek, objectives - according to the Project Management Institute - articulate " targeted changes in the organization the project is expected to achieve." The scoring rubric for the proposals will want proposals to show that the description and the objectives are in alignment, an important destination as well as a thought-out journey.

SMART Outcomes

This is one useful way to articulate outcomes for the application.
S = Specific: state what you will do using active verbs. For example, "redesign six courses for online delivery"
M = Measurable: how will you know that the objective has been met? For example, "redesign courses and assess with verified quality rubric."
A = Achievable: Is the project doable given the available resources?
R = Relevant: Does the outcome align with the mission of the University and the College(s) it serves?
T =  Time-bound: Can the team finish the project within the time allotted (one fiscal year)?