Wrike Project Delay Causes Definitions

Casey Shew Updated by Casey Shew

The custom field in Wrike titled "Project Delay Causes" (shown below) is used by IDDs to capture the primary factors influencing a project being delayed, if any. The selection choices for this custom field may not be entirely intuitive, and as such the purpose of this article is to provide more thorough definitions for those selection choices.

Notes

  • Adding these delay causes should be limited. Ideally no more than three to keep them meaningful.
  • When adding a Delay Cause, the IDD should also add a dated explanatory comment. E.g., 01/02/03 Added "FAC- Unanticipated Availability Limitation" as a delay cause as the faculty has a family illness to attend.
  • Delay causes should be added at the Project Card level. However, they can also be added at the task bucket level for additional specificity.

Each selection choice starts with prefix in all caps that indicates the category of delay type it is:

  • FAC = Faculty-related cause
  • P&P = People & Process-related cause
  • OTH = Akin to miscellaneous, this is for anything that falls outside of the two above categories

Selection Choice

Definition

No significant delay

There is no significant delay from the original planned completion date

FAC - Non-responsive

Even with multiple LSG and product interventions, the faculty does not respond. This can occur multiple times throughout the project and for ranges in duration.

FAC - Unanticipated availability limitations

Faculty availability differs from what was discussed at project inception due to teaching load, illness, competing work priorities, or changing personal needs (e.g. vacations, leave, travel).

FAC - Additional Time Requested (project-wide)

Faculty agreed to original plan but did not anticipate the work effort required within a specific project. As a consequence, a conversation with faculty and product led to project plans being updated to allow more faculty more time across the project. This can relate to the faculty's initial perception of what they could accomplish (e.g., I can get that done in 5 days or I can work on two courses simultaneously) only to recognize that the work takes more time. Can also be because they need more review cycles or have deeper content revisions than average. Concerns related to more work actually being added to the project (e.g., one course now is two) would be an expansion of the work and would fall under "Product Scope Change" instead.

FAC - Faculty over-booked on eC projects

Faculty started more than one project or course at the same time, and then realized that they can't commit or don't want to work on more than one at the same time. This relates to multiple initiatives, not a single certificate of multiple short courses.

OTH - Content Complexity or Scope Change

Examples of Content Complexity or Scope Change:

1. Original outline did not work once the content was created, required restructuring of the content flow and potentially adding additional content (e.g., tools, read page, activity)

2. Identification of additional tools/activities later in course development

3. Heavier than anticipated animation or graphic support needs

4. Content requires more time to develop than originally anticipated (e.g. more graphic/illustration support; additional company profiles or data sets for activities)

5. New innovation complexities such as bringing in new software, applications, or processes (e.g., a first use of feedback fruits, Codio, an H5P application)

OTH - Vendor/External Resource Delays

Such as a delay in obtaining parts for a kit, difficulty working with a third party to source or gain access to a book, a delay in obtaining permissions for copyrighted materials, etc...

P&P - Product Priority Change

Examples of Product Priority Change:

1. Changes to priorities of other projects (by Product) affected the workflow or priority for this project

2. When a people resource (e.g., ID, IDA, GD, Ill) is pulled to help with a last minute, urgent (usually for-credit) project

P&P - Product Scope Change

Examples of Product Scope Change:

1. Additional courses were added to the development plan, or a significant revision of the audience, scope, or objectives were made

2. Masters' Programs: The unit changes the program curriculum and it disrupts previously established project plans

3. When for-credit work or new social program causes delay/hold on work already in progress

P&P - Staffing Disruption

Unknown longer-term delays due to internal staff disruptions; not vacations/sick days.

P&P - (QA) Workload /Allocation

When there is more work than QA resources have time to do. Not caused by another identified delay issue (e.g., Product Priority Change), but just demand exceeding capacity (only determined by unit manager).

P&P - (ID/IDA) Workload /Allocation

When there is more work than ID/A resources have time to do. Not caused by another identified delay issue (e.g., Product Priority Change), but just demand exceeding capacity (only determined by unit manager).

P&P - (CSG) Workload /Allocation

When there is more work than CSG resources have time to do. Not caused by another identified delay issue (e.g., Product Priority Change), but just demand exceeding capacity (only determined by unit manager).

P&P - (CSG) No Early Resource Available

When CSG work is submitted earlier than planned, but CSG cannot accommodate the early arrival and returns the due dates to the original plan.

P&P - (OD) Workload /Allocation

When there is more work than OD resources have time to do. Not caused by another identified delay issue (e.g., Product Priority Change), but just demand exceeding capacity (only determined by unit manager).

How did we do?

Importing Tasks into a Wrike Project

Setting OOO Coverage for Roles in Wrike

Contact