9 0 UG:Create Define Workplan

From Pnet-Community

Jump to: navigation, search

Contents

[edit] Work Plan Overview

The workplan module is only available in project workspaces and shows all current tasks and milestones by which projects are tracked.

A workplan is defined when the tasks and milestones within the workplan are created and added into it.

For more information on creating a Task, refer Creating a Task or Milestone

[edit] What are the filter options to view a Workplan?

The contents in a Workplan can be viewed based on the filter options that are provided. The filter options are grouped to lists tasks based on the following:

1. Status of Completion

2. Start dates and End dates of the Task

3. Task Name

4. Percentage of work complete

5. Type of task (Milestone/Task)

6. Phase to which the task is grouped

[edit] What are the views available for a workplan?

Furthermore, it is possible to change the workplan view between:

1. Flat

2. Gantt

When using the Gantt view, there are different symbols representing the different types of tasks. A diamond before the tasks name represents a milestone. There is also a symbol for a task summary.

[edit] Can I Import a MS Project into a Workplan?

Tasks can also be created using project planning software from vendors such as Microsoft Project software.

As many companies work with the MS Project software, we support the import of projects from Microsoft Project versions 2000 through 2002. The project to be imported should be saved as "MPP" format. Project.net does not support import directly from "MPP" format. To import the created MPP file to a Project.net project, simply use the following procedure:

All tasks, milestones, resources, and assignments may be imported. During the Import Wizard, resources are mapped to members of the project space.

For more information on importing tasks to the workplan, refer Importing tasks to a Workplan

[edit] How are tasks created?

Participants have the ability to define their status on tasks assigned to them, therefore allowing the task owner to determine the effective status of the task. To make it possible to track a detailed task as well as project status, a task must include:

1. planned work hours or duration

2. actual work hours or duration

3. planned start date

4. planned end date

5. calculated percentage of actual work completed to total planned work

6. task dependencies

7. constraints

[edit] Do I have the rights to modify a Task?

By default, a team member cannot modify a task assigned to him or her. If you want the owner of a task to indicate progress on that task, you will need to change the permissions for that task.

When a task is assigned to a team member, it will appear on his or her New Items channel in his or her Personal Workspace. The task must be accepted or declined by the team member. When it is accepted, the task will move to the individual’s Assignment channel. The Assignment channel displays all of a team member’s tasks that are in progress or scheduled to begin within two days.

[edit] What is effort driven for a task?

Effort-driven means that when you assign or remove people from a task, Project.net lengthens or shortens the duration of the task based on the amount of resource units assigned to it, but it doesn't change the total amount of work for the task.

For example, you know (or have solid estimates of) the square footage of the walls to be painted or how much software code needs to be written for a particular set of features. So when planning a project, you often have a pretty good idea of the "work" that needs to be done. To complete your project schedule, you then adjust the anticipated times to complete this work (duration) and the number of resources (resource units) you can assign to it to complete the work. With this idea in mind, the effort-driven scheduling feature is turned on by default in Project.net. You can turn the effort driven setting off, however, if your project tasks have different requirements.

[edit] How does effort driven scheduling help?

Now that you know more about how effort-driven scheduling works, it helps to understand how to apply it to tasks and how it affects the calculations the scheduling formula makes. Task types determine what happens to the other two variables in the scheduling formula. Effort-driven scheduling determines what happens to the duration or resource units for a task when you add or remove resources.

[edit] What types of Tasks can be created?

When creating a task in Project.net you have the choice of

1. Fixed units

2. Fixed duration

3. Fixed work.

[edit] Fixed Unit

Fixed Unit tasks are used when the % work assigned (units) to a resource needs to always be the same regardless of the duration and work required. If the assigned task type is Fixed Units / Effort Driven, assigning additional resources shortens the duration of the task.

[edit] Fixed Work

Fixed Work tasks are used when the work required for the task is constant and the duration and resources (hence units) assigned to the task are flexible. If the assigned task type is Fixed Work, assigning additional resources shortens the duration of the task. Fixed work by default means it is effort driven so that option has not been made available when a task is assigned to be FW.

[edit] Fixed Duration

Fixed duration type is assigned when the duration of the task needs to be constant regardless of the units and work. If the assigned task type is Fixed Duration, assigning additional resources should decrease the amount of work for each individual.

[edit] Summary of Task Types

Task Types can be classified into-

1. Fixed Unit, Effort Driven

2. Fixed Unit, Non-Effort Driven

3. Fixed Duration, Effort Driven

4. Fixed Duration, Non-Effort Driven

5. Fixed Work

[edit] Fixed Unit, Effort Driven

  • Assignments are never changed.
  • Changing duration changes task work.
  • Changing work or changing, adding or removing assignments changes duration.

[edit] Fixed Unit, Non-Effort Driven

  • Assignments are never changed.
  • Changing duration or adding or removing assignments changes task work.
  • Changing work or changing assignments changes duration.

[edit] Fixed Duration, Effort Driven

  • Duration is never changed.
  • Changing duration or assignments changes task work.
  • Changing work or adding or removing assignments changes the amount of time resources spend working.

[edit] Fixed Duration, Non-Effort Driven

  • Duration is never changed.
  • Changing duration or changing, adding or removing assignments changes task work.
  • Changing work changes the amount of time resources spend working.

[edit] Fixed Work

  • Work is never changed.
  • Changing duration changes the amount of time resources spend working.
  • Changing work or changing, adding or removing assignments changes duration.

[edit] What are the other task functions offered in a Workplan?

The definition of dependencies between tasks as well as the specification of constraints is supported within the task functionality. However, Project.net does not currently calculate start and end dates based on dependency definitions.

[edit] Dependencies

A dependency will define all those tasks which must be completed before the current task can be started or finished. Each of these tasks is linked to the task by a relationship (dependency type) and a positive or negative lag time. Each task may have several dependencies. Currently, Project.net supports the definition of dependencies between tasks without any calculation. You are able to define as many dependencies as you need. A dependency will be determined by:

1. a task

2. a relationship

3. a lag time

You can choose the task by a selection menu that shows you all available tasks. The dependency relationship may be one of the following dependency types:

1. Finish-to-Start

2. Start-to-Start

3. Finish-to-Finish

4. Start-to-Finish

For the lag time, you can choose one of three units (hours, days, weeks) from a selection menu.

[edit] Constraints

Each task may be defined by a constraint. Some constraints need additional information. In this case, you have to determine the constraint date; otherwise, you are not able to complete the creation of the task.

You should use these options only if it is necessary for the completion of the task, or is of importance for the execution of the project that the task should be started or finished at a determined date. If you want to define a date without any constraints, you should use the field Deadline. The Deadline is a target date on which the task should be finished. However, the assignment of a Deadline has no effects on the time scheduling.

The available types of constraints are:

1. As Soon As Possible

2. As Late As Possible

3. Finish No Later Than

4. Finish No Earlier Than

5. Must Start On

6. Must Finish On

7. Start No Earlier Than

8. Start No Later Than

To create a task in a project quickly, use the Quick Add feature of Project.net. Note that a task created with the Quick Add function is not assigned to a project phase. In addition, it has ’normal’ priority, a status of ’not started’, and no dependencies or constraints.

If you enter zero work and an equal start date and finish date, a milestone will be created.

A task can only be created in a project (workspace). Once a task is created, it must be assigned. Tasks can only be assigned to project participants.

[edit] Baseline in a Project Workplan

A Baseline is an initially planned imaginary line which helps to measure the progress of the project. In other words, baseline is an original project plan or reference point used to track progress of the project. Baseline includes start date, finish date, duration and work of project.

When you build and refine your project to the point where you are prepared to start, you have a good beginning point or baseline. Project.net enables you to create many baselines for the project at different stages so that you can compare your current progress against your initial baseline.

If there are multiple baselines, then the baseline which you want to use to track progress needs to be set as default.

When you save a baseline, the four key pieces of information: work, duration, start date and finish date are saved for each task in the project.

The baseline information is used to calculate variances against scheduled information. If the baseline continuously differs from actual date then the initial plan is not accurate.

[edit] More Help

[edit] Project.net User Guide

[edit] On-line Help

[edit] Project.net FAQ

[edit] Project.net User Forum


It is our belief that Project.net users know what they want in their Project.net documentation, therefore, we encourage you to edit this Wiki page and contribute your corrections and additions. If you read something that is not clear make a note of it on the Discussion tab.

Personal tools