Wrike Best Practices for Degree Program Projects

Casey Shew Updated by Casey Shew

The following are best practices for managing Wrike projects related to Degree Programs identified by Rachel Healey & Pete Garcia, based on their years of experience organizing this work in Wrike.

  • The following format should be used for project titles of degree program course development projects in Wrike: “{program acronym} - {year} - {coursecode} - {course title}”
    • Example: EMHA - 2021 - PAM5473 - Microeconomics for Managers
    • Note: If you don’t know the course code when the project is initially created, it can be omitted from the title initially and added when it is known
  • Add Wrike degree program projects to the “D2 - FC Programs” structure/hierarchy in the appropriate place as early as possible, as an additional location
  • When creating a folder that represents the entire program (i.e. “EMHA”), check if one already exists by searching in Wrike. If there is another one that already exists in Wrike, be very specific in naming your new folder so there aren’t multiple folders with the exact same name. For example, if your folder only contains courses in the program that are in planning, and others are in development, name it descriptively like “EMHA Courses in Planning”, rather than just “EMHA”.
  • Always set a task name prefix containing the relevant course code and class year for all of the tasks in the project
  • If the student access date is known, it should be populated into the “First Section Start Date” custom field in Wrike as soon as possible
  • The Term associated with the course should be indicated in a custom field, rather than the project title
  • When in doubt, look to examples of how projects have been set up in the past inside of the “D2 - FC Programs” folder structure for guidance

How did we do?

Course Maintenance Request Form Workflow

Contact