Activities Overview

Since projects can vary considerably, there are few hard-and-fast rules about the contents of activities or how long they can last. Activities in a production line, for example, might last a day or two, while activities in a large development project might have durations of many months or even years.

In general, most activities share the following characteristics:

It is a good idea to keep these characteristics in mind when defining activities. By breaking a project down into a set of discrete activities with relatively limited durations, it is possible to establish more objective, and thus more accurate, estimates of progress.

When you insert activities on the change details form, a unique activity ID is created automatically and cannot be changed. The ID will start with the letters ACT and will be a parent ID.

Many Open Plan Schedules Linked to One Control Account

When a change request has Change Details included on the form and allows creating, editing, and deleting of activities, the change can only be associated with a single project.  

Before you begin, learn about...

Rules for editing change details data

Change management

How activities relate to one another

Constraint dates

How change request data is stored

Different date sets

What do you want to do?

Insert an activity

Edit an activity

Delete an activity

Add a relationships to an activity

Edit an activity relationship

Delay the start of an activity

Add a resource to an activity

Change the EVT for an activity

Add a predecessor or successor relationship to define when an activity occurs

View external predecessors and successors

Enter a code assignment on an activity

Set a 1:1 relation between a work package and activity


Learn more about...