Error message

  • Strict warning: Only variables should be passed by reference in eval() (line 40 of /var/www/project.net/public_html/modules/php/php.module(80) : eval()'d code).
  • Strict warning: Only variables should be passed by reference in eval() (line 40 of /var/www/project.net/public_html/modules/php/php.module(80) : eval()'d code).
  • Strict warning: Only variables should be passed by reference in eval() (line 40 of /var/www/project.net/public_html/modules/php/php.module(80) : eval()'d code).
  • Strict warning: Only variables should be passed by reference in eval() (line 40 of /var/www/project.net/public_html/modules/php/php.module(80) : eval()'d code).

No front page content has been created yet.

Articles

Each task has a scheduled start date and a scheduled finish date (usually just called the task's start date and finish date)  The way that they are used and set depends on whether the task is manual or automatic.

In this article, we'll talk about how scheduled start and finish dates are set, how to choose between manual or automatic scheduling (also known as calculated scheduling), and the role of constraints, dependencies, deadlines and milestones.

The Project.net project management system contains a scheduling engine that can automatically schedule the tasks in a project, determining the start and finish times of each task based on its work, duration, assigned resources, dependencies on other tasks, and other constraints.  To understand how the scheduling engine works, it's helpful to start out with a much broader perspective, and look at

  • schedule-related problems in general (which include project scheduling problems)
  • the various kinds of algorithms used to generate solutions for those problems

This article aims to provide an introductory overview of the terminology and approaches used in applying these algorithms to a wide range of classical schedule-related problems.

Both Project.net and Microsoft Project allow the scheduled dates of a task to be constrained so its starts or finishes no later than, no earlier than, or on a specific date.

Tasks in Project.net have constraints that require that the start and/or finish date of a task be no later than, no earlier than, or on a specific date.  Constraints are not enforced at all for manual tasks, and for automatic tasks, they are only enforced when the workplan is rescheduled.  This article talks about how constraints can be set, and how they can be visually identified in a workplan.

Project.net has two kinds of leaf tasks – manual and automatic
Manual tasks are manually scheduled.  They should be used when you want to explicitly set a task's start and finish dates and not allow it to be changed automatically by the scheduler based on changes to other tasks.

In this article, we're going to talk about how the duration and scheduled start and finish dates are tied to one another, and how changing any one of them affects the others.

News

Introduces Advanced Scheduling Engine, Business Intelligence Capabilities and Drag & Drop Workplans

Bedford, MA–December 10, 2013–Project.net Inc., the leader in Open Source collaborative Project Management and Project Portfolio Management (PPM) today released Version 9.4 of Project.net™.

1st Open Source Project Portfolio Management (PPM) Solution Included in Market Scope

Bedford, Ma. — May 14, 2013 — Project.net Inc., the leader in collaborative Project Management and Portfolio Management (PPM), has been included by Gartner, Inc. in its "MarketScope for IT Project and Portfolio Management Software Applications" research report. Project.net provides organizations with an enterprise-grade, customizable and robust alternative to expensive and proprietary monolithic applications.