9 0 UG:Sharing Tasks and Schedules
 Scheduling a Project in Project.net
Project management is nothing but the discipline of planning, organizing and managing resources for successful completion of a project. As a project manager, scheduling is one of the critical tools used for completing projects on time. Project.net helps you schedule a project from the information you enter. The tasks collectively form a complete project, and if necessary, the resources (the people) needed to complete those tasks. If anything about your project changes after you create your schedule, you can update the tasks or resources and Project.net adjusts the schedule for you.
 How to Schedule a Project in Project.net
For each task, enter its duration, task dependency, and constraints. Project.net then calculates the start date and finish date for each task. You can enter resources in your project and assign tasks to them which gives a clear view of resources designated for completing an activity. After you enter resources and task schedules, they are further refined according to resource work, units and working time entered on the calendar. Other elements, such as lead and lag time, task types, resource availability and the driving resource can affect scheduling. Understanding these elements’ effects can help in maintaining and adjusting scheduling needs.
 Project Start Date and the Schedule
If you enter a start date for the project, by default, Project.net schedules tasks to begin on the project's start date and calculates the project's finish date based on the last task to finish. As you enter more information about tasks, such as task dependencies, durations, and constraints, Project.net adjusts the schedule to reflect more accurate dates for tasks.
 Deadline Dates in the Schedule
Deadline dates don't usually affect task scheduling. Deadline dates are used to indicate a target date you don't want to miss, without requiring you to set a task constraint that could affect scheduling if predecessor tasks change. A task with a deadline is scheduled just like any other task, but when a task does not meet its deadline, Project.net displays a configurable task indicator notifying you that the task missed its deadline.
 Manage Planned, Scheduled and Actual dates
After you enter all pertinent project information and are ready to begin the project, you can set a baseline and begin to track actual progress on tasks. When you enter an actual start date or an actual finish date for a task, Project.net updates the scheduled dates for that task in the Start and Finish fields. The baseline start and finish dates are not affected by the changes you make to the actual or scheduled dates.
When you update or enter progress on tasks, Project.net calculates the difference between a task's baseline start date and scheduled start date and identifies the difference in Start Variance field. The variance is also calculated between the baseline finish date and scheduled finish date, identified in the Finish Variance field. When tasks are completed, the variance is calculated between the baseline start and finish dates and the actual start and finish dates.
If you make changes to the tasks that affect their start or finish dates of those of succeeding tasks, the new dates are updated as the scheduled start and finish dates. Scheduled start and finish dates show the current status of the project according to the changes.
You can also compare baseline, scheduled dates, and actual dates to dates in an interim plan if you want to see incremental progress on your project.
 Sharing Tasks and Schedules
Single tasks or entire schedules can only be shared among workspaces. Tasks are shared as individual items. Schedules are shared as a single, "summary" task. The Schedules appear in the importing work plan as a single task with start date, end date and overall progress derived from the originating schedule.
 Actions allowed in Task Sharing
Allowed Actions while sharing are:
- Individual tasks or entire schedules can be shared read-only with other workspaces.
- Individual tasks or entire schedules can be copied to another workspace.
This copies the chosen object into the importing schedule. Thus, such imported objects will act like any regular task created in the importing schedule.
 Importing external Tasks and Schedule
Exporting (sharing) of individual tasks or an entire schedule is controlled by the exporting (independent) workspace.
- This workspace must specify which tasks (or the entire schedule) will be exportable to other workspaces.
- It must specify whether the object can only be shared ("Share objects between multiple workspaces"), copied ("Allow other workspaces to make a copy of this object") or both by the importing workplan.
- It must specify which workspaces are allowed to import or copy the shared object.
- If a task or schedule is not made sharable to a workspace, it will not appear on the list of available items to import for that workspace.
 More Help
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.