Scheduling software helps in project schedule management. It is software that contains features, algorithms to manipulate activities with dependencies and resources to create schedule model and schedule presentations.

The scheduling software also allows to adjust various schedule parameters (e.g. duration, relationship, dates, resources, constraints, etc.) Further:

  • It lets you create baseline and record actual progress.

  • It lets you analyze project progress against baseline and trends over periods.

  • You can compare different schedule with each other.

  • You can analyze resource allocation and level resources.

  • You can optimize project plan to meet the end date, the budget and other constraints.

The two most widely and commonly used scheduling software are described here.

In order to define a schedule development approach, multiple sources can referred to for assistance, such as:

  • Enterprise Environmental Factors (EEF): E.g. EEF states people are resistant of using scheduling software or people prefers predictive approach in their projects.

  • Organizational Process Assets (OPA): E.g. OPA explains available resource capacity, resource calendar, internal/external dependencies, scheduling methodology to use etc.

  • Stakeholder register: E.g. it will tell what key stakeholders want out from schedule. Some might like Gantt Charts, some might want only a basic schedule, some wants reports created in MS Project. 

  • Any other project requirement that may influence schedule development approach must also be considered.

Scheduling methodology is set of rules and methods used to develop schedule. Various scheduling methodologies that exists include:

  • Critical Path Method (CPM): Schedule is created by looking at activity duration and activity relationship.

  • Critical Chain Method: It is CPM, with effect of assigning resources to activities.

  • Location-based scheduling (LBS): It develops a schedule that shows:

    • Location and time of the activity,
    • Movement of the crews through time and location.
    • LBS focuses on optimizing resource utilization and their production rates.
    • LBS is also known as vertical production method, linear scheduling, repetitive scheduling method, flow production and flow-line scheduling.

  • On-Demand Scheduling:

    • Activities are defined with duration and dependencies. 
    • Each activity is pulled for execution when the resource is available. 
    • The purpose of on-demand scheduling is to limit a team's work-in-progress (WIP) in order to balance the demand against a team's delivery throughput. 
      It is usually used in adaptive life cycle.

  • Lean Scheduling:

    • It is same as On-Demand Scheduling, with focus on minimizing waste (lags, delays, extra time) in order to maximize value. The project team collaborates in pull planning sessions and performs these steps:

      • Master scheduling:  Identifies key milestones, key activities, and phases. 
      • Phase scheduling. Identifies phases from master schedule:

        • Determines duration, sequences, constraints for each phase.
        • Phase schedule is used to generate look-ahead schedules (work to be done in next periods)

      • Look-ahead planning: By considering resource capacity, detailed plans for work to be done in next weeks are established.

  • Intelligent Systems:

    In software, assumptions and activity requirements, such as constraints, hard logic (mandatory dependency), resources, and conditions (IF-THEN-ELSE) are entered.
    Schedule model learns from progress made and proposes a new sequence of relationships for remaining work. Another option is that the software learns from other projects’ schedule models and based on that, it reserves materials, equipment and workers.

  • Line of balance:

    It focuses on production rates over time for repetitive activities. The main objective is to find the required resources for each activity. It calculates productivity along with time in an easy graphical representation.

There are different schedule life cycle types (often called project life cycle). The project manager will choose the best that suits the project requirements. The life cycles are explained below:

Predictive: The entire work is planned and scheduled in the beginning of the project.


Iterative/agile: One or more specific task is planned to be done in periods (iterations) e.g. Three one-week periods. When done, another activity is planned/worked on. This cycle continues.


Adaptive: Same as iterative/agile. However, work is planned in many more and smaller iterations. Hence, there are frequent outcomes coming out from iterations. Adaptive is used in complicated/complex projects.


Rolling Wave Planning: It is iterative planning in which near term work is planned in detail, while the work in future is also planned but at a lower level of detail.


Incremental: Portion of entire work is planned and completed. Then next portion of entire work is planned/completed and this cycle continues.


Hybrid: A combination of approaches for different projects or sub-projects.

Page 2 of 3