Glossary Term | Description |
Activities | An activity is a step during a project that is broken down to a specific task. It is common for simple projects to have more than 100 activities and large projects to have more than 500. An activity should be created for any job, requirement, or stage leading towards a milestone. Creating a list of activities from the Work Breakdown Structure (WBS) will help ensure that no steps are missing and they are completed in a logical manner. |
End Date | For Manual created activities the end date is the date entered by the user as the planned end date of the activity. For Automatic activities the end date is either the forecast end date from the schedule or last working day of the week if activity crosses multiple weekly periods. |
ID | The unique ID assigned to an activity. Unique IDs cannot be duplicated and have to remain exclusive to an activity. This is to ensure that all activities are logged and tracked systematically. |
Next Week Activities | The activities for the next week period that need to be completed and/or reported to ensure that the appropriate activities are completely promptly. This allows PM's to review key areas of the project such as workload, resource requirements and scheduling. Thus, risks or issues related to the project can be identified immediately. |
Notes | Any additional information about an activity should be described briefly over here. This provides other project members with visibility around the activity. Thus, project members are able to execute plans in unison and with greater efficiency. |
Participants | The key people involved with the execution of the activity. The information should always be up to date. Any changes must be documented straightaway to ensure that the information being reviewed is accurate. |
Past Week Activities | The activities for the previous week that need to be completed and/or reported to ensure that the appropriate activities are completely promptly. This allows PM's to review key areas of the project such as workload, resource requirements and scheduling. Thus, risks or issues related to the project can be identified immediately. |
Start Date | For Manual created activities the start date is the date entered by the user as the planned start date of the activity. For Automatic activities the start date is either the forecast start date from the schedule or first working day of the week if activity crosses multiple weekly periods. |
Status | The current status of an activity. PM's can refer to this field to assess the progress of an activity. The status types include: * Completed- The Activity is 100% completed * Work In progress- The task has been started, but has not been completed * Not started- The task has been planned but no action has been taken |
This Week Activities | The activities for the current week that need to be completed and/or reported to ensure that the appropriate activities are completely promptly. This allows PM's to review key areas of the project such as workload, resource requirements and scheduling. Thus, risks or issues related to the project can be identified immediately. |
Title | The title of an activity. The title should highlight the primary purpose of an activity and how it is meant to be executed. Thus, all project participants are provided with greater visibility and a better understanding of the activity. |
Type | Activity type options are Manual or Automatic. An activity can be created manually within the module (Manual) or a task marked in the schedule as an activity (Automatic). For Automatic the WBS reference is also displayed. |
1.10 Activities Glossary Print
Created by: Earl Uy
Modified on: Mon, 23 Nov, 2020 at 8:12 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.