Microsoft Project

Failure is nature’s plan to prepare you for great responsibilities. ~ Napoleon Hill (Author of the 1st Project Management Book, “Think and Grow Rich”)

napoleon-hill.jpg

In 1991 I was working for Symantec in the product group for TimeLine, the first project management software for the PC. I had recently been working on developing guides for a new product that had just come out called GuideMaker, which was a product that allowed a person to build expert templates that produced project plans for TimeLine and Microsoft Project, that were generated from how the user answered key questions. For instance, let’s say the guide was for building a new residential house, questions the user might answer could be related to square footage, number of bedrooms and baths, materials uses, and if the house was going to have a basement or built on a slab. In this example, a construction manager would run a Guide, answer the question and the product would produce a *.mpp accordingly.

One day I got a call from an editor from Success Magazine. He was a psychologist that believed that personal success was primarily a function of expert planning and deployment. Thus his interest in a product that could build expert plans for a particular purpose based on how users answer questions.

In our conversation, he stated, “Think and Grow Rich” when you take out the psycho-babble out, is essentially a project management book. One of the first self-help books, and the first project management book for the public.

“Think and Grow Rich” was written in 1937 during the Great Depression and has sold over 20 million copies. The philosophy taught in the book is based on the idea that there are tools and techniques that can help people succeed in any line of work, to do and be anything they can imagine.

The Gantt Chart came out in 1917, it was used in the public domain on the high profile Hoover Dam project. Modern project management started to emerge in the 1950s

Using Microsoft Project @project around the house.

Over the last couple of decades I have used @project to plan large capital projects in several different in industries. However, I have personally found Microsoft Project @project to be invaluable in planning repairs for homes I own. Currently I have four homes over 100 years old, and one 120 years old. At times, with careful planning and executing, I have gotten two months of work done in two weeks. This is my last one. Late start but pretty much kept to schedule. Good final product.

remodel.jpg

Critical Path Method

Likely the most important feature of Microsoft Project is the calculation of critical path, or Critical Path Method.

Critical Path

The longest path or sequence of project activities that control the earliest a project is expected to finish.

Traditionally, an activity on the critical path has no float or slack, meaning that if the activity is delayed it will delay the finish of the project.

Suppose, for example, that three people are each traveling different routes from point A to point B and would like to know the earliest they can meet together at point B. The person taking the longest path (on the critical path or the longest route) to point B determines the earliest possible time the three can meet together. If that same person takes one hour longer to get to point B than planned, the earliest meeting time is delayed by one hour.

Critical Path Method (CPM)

A simple mathematical method used to determine the duration of the project by calculating the possible paths of activities in a project schedule and identifying the longest path (critical path) in the schedule, or the earliest the project can be expected to finish given everything that must be accomplished.

The Critical Path Method also calculates the amount of float or slack for each activity and sequence or path; identifying how much an activity or sequence of activities can be delayed before delaying the finish of the project.

The Critical Path Method uses a forward pass and backward pass calculation to determine project duration and activity float or slack.

Critical-Path.jpg

Linking In Microsoft Project

There are a variety of terms used to describe linking in Microsoft Project:

  • Linking

  • Setting dependencies

  • Sequencing deliverables

  • Network diagramming

  • Setting predecessor and successor relationships, etc.

There are four different types of links that can be created between tasks:

  • Finish to Start

  • Start to Start

  • Finish to Finish

  • Start to Finish

There are three basic ways to link tasks:

  • Selecting tasks and then clicking the Link command

  • Editing any of the many predecessor or successor fields

  • In the taskbar pane of a Gantt Chart view, Network Diagram view, or a calendar view, click, hold and drag the link command

Linking.jpg

Timing Constraints in Microsoft Project

A variety of Timing Constraints are only available for Auto Scheduled tasks. All Manually Scheduled tasks are As Soon as Possible (ASAP)

The most important thing to remember is that Timing Constraints have a higher priority on schedule than do links. Unless of course, you turn off that particular scheduling rule in Project Options. (Project Options / Schedule / Scheduling Options for this project / Tasks will always honor their constraint dates)

There are 8 Timing Constraints that can be applied to detail tasks and milestones.

Flexible

  • As Soon As Possible (ASAP) - Pushed toward the project start date

  • As Late As Possible (ALAP) - Pushed toward the project finish date

Semi-Flexible

  • Start No Earlier Than (SNET) a date - The task be pushed out in time, but can not start earlier than a date you enter

  • Start No Later Than (SNLT) a date - The task can start earlier than scheduled, but can not start later than a date you enter

  • Finish No Earlier Than (FNET) a date - The task can finish later than scheduled, but can not finish earlier than a date you enter.

  • Finish No Later Than (FNLT) a date - The task can finish earlier than scheduled, but can not finish later than a date you enter.

Inflexible or Fixed

  • Must Start On (MSO) a date - The task must start on a date you enter

  • Must Finish On (MFO) a date - The task must finish on a date you enter

Three Timing Constraints are available for Summary Tasks:

  • As Soon As Possible

  • Start No Earlier Than a date

  • Finish No Later Than a date

Timing-Constraints.jpg

Scheduling Engine

Behind the scenes of your timeline are an interactive set of features, or rules, that determine how tasks are scheduled. This set of features is often referred to as the scheduling engine.

A partial list of scheduling features or rules include:

  • Project Start Date

  • Scheduling From the Project Start Date or Project Finish Date

  • Calendars

  • Schedule Selections in Options

  • Task Type (Fixed Duration, Fixed Units, Fixed Work) crossed by Effort Driven (Yes or No)

  • Resource Assignments

  • Task Mode (Manually or Auto Scheduled)

  • Task Constraints

  • Links or Dependencies

Schedule built following all of the scheduling rules.

Schedule built following all of the scheduling rules.