Robin Nicklas

This is the last of four articles I’ve written recently on the topic of on tracking a project. I have outlined a four-step tracking cycle:  se

In the first two articles of this series, a four-step tracking cycle was defined. It includes setting the status date, entering actuals, rescheduli

In my recent Tracking Starts with a Status Date article, a four-step tracking cycle was defined. It includes setting the status date, entering actu

There are four steps involved in tracking a project:  setting the status date, entering actuals and schedule revisions, rescheduling incomplete wor

Different views into the same MS Project file enables us to see a schedule from multiple perspectives. Using the split view feature is one way to d

  In my recent article, Sequencing Product Backlog, I used the shortest weighted processing time (SWPT) strategy to sequence a product backlog

A colleague posed a problem recently. He recorded earned value after tracking work done in the first status period of his project. When recording w

When modeling a project as a flow process, one objective is to deliver the maximum amount of value in the shortest amount of time. Most project man

In my recent “Is MS Project’s Leveling Optimal?” article, I covered the fact that MS Project may not produce optimally leveled schedules in terms o

The objective of resource leveling is to minimize schedule length while honoring precedence relationships and resource constraints. If we know what