LEAD, LAG, ELAPSED TIME AND START TIME IN SCHEDULING

This blog will be a short one.

I am going to describe lead, lag, elapsed time, and start time in scheduling.
Lag is waiting time. For example, if you are pouring the concrete you have to wait 2 days
before you can start with building the walls.

After that you will get:

You can turn on Task Inspector:

And you will get:

Lead is opposite of lag. For example, if you are developing software you can start
with testing before developing is fully done. We will put 2 days of lead time:

And you will get (with Task inspector turned on):

Imagine that you have a task called “BACKUP” and that task will have duration of 3 days
and it has to start on Friday 01.04.2011. In scheduling options we have:

So,this task will start on 01.04.2011 at 08:00 and will finish on 05.04.2011 at
17:00 (see picture below):

But this is not what you want, is it? You want your task to start on 01.04.11 and
last for 3 days, but whole 3 days. How will you get that? Easy, in Duration field type 3ed instead 3d. You will get:

Backup will start on Friday at 08:00 and finish on Monday at 08:00 which means that it will last 3 days X 24 hours = 78 hours.

Now suppose that you have a meeting with your customer and it will last 3 hours. If
you put this meeting as a task in MS PROJECT and if you put 3h in duration
field you will get:

So, your meeting will start at 08:00 by default, because default start time is at 08:00 (see second picture above). But what if you will start your meeting at 10:00? You will certainly not change the default start time in scheduling options because it will cause all tasks to
reschedule and that is what you don’t plan to do.
Instead, in start field you should put 18.03.2011 10 (10 mean 10 AM):

You will get:

Now, your meeting will start at 10:00 and finish at 11:00 as you planned.

See you!

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management, Uncategorized | 2 Comments

Scheduling problems in MS PROJECT 2010 – Part 2.

Today I will write about scheduling problems when you put the start and the end date
for tasks into MS PROJECT. I WILL NOT write about constraints and limitation with this method (for example about flexible and hard constraints and why this is not the best approach). I will just show you how duration is affected when you put those dates into MS PROJECT.
In MS Project 2010 you can choose between two types of scheduling: Manually or Automatic schedule. If you choose Manually you will have the whole control over the scheduling and you will not get the whole power of MS Project 2010. For my examples I’ve choose Automatic scheduling mode and it is shown on picture below:
Next we will set up daily, weekly and monthly working time:
And then:
We have told MS Project that regular working time will be Monday – Friday from 08:00 AM until 16:00 PM, 8 hours without lunch break.
Now we will set up our standard calendar:
1. Select Project TAB
2. Click on Change Working Time
3. On The For Calendar choose: Standard (Project) Calendar
4. Click on Work Weeks
5. Select Default
6. Click on Details
7. Select days: Monday – Friday
8. Choose: Set day(s) to these specific work times
9. Type 08:00 in From field and 16:00 in To field
10. On the same form click OK button
11.
On the Change working time click OK button
Now you can enter two tasks: Task 1 with start on 22.3.11 and end on 22.03.11, and Task 2 with start on 22.3.11 and end on 23.03.11

What do I get? Task 1 has duration of 0,5 days, and Task 2 duration of 1 day. WHY?
Well it is easy to explain. When I put the same date for start and finish date for Task 1 I said: “I want my task to last 4 working hours”. WHY? Because I put in calendar options (from 08:00 till 12:00) that they will be a 4 hour job. And I also said that duration for one day is 8 hours. WHERE? See picture below:
So MS PROJECT calculates duration in formula 4 working hours / 8 hours per day in scheduling options = 0,5 days
For Task 2 I said that it will start on 22.3.11 and it will end on 23.3.11. Working time will be from 08:00 till 12:00 (4 hours), so it will be 2 days X 4 hours = 8 hours
And because the day duration lasts 8 hours (see picture above) MS PROJECT calculates duration in formula  8 working hours / 8 hours per day in scheduling options = 1 day
Now, suppose that in my calendar I choose the working time from Monday till Friday from 08:00 – 15:00 (7 working hours) and I put the same start and end date for Task 1 and Task 2 as I put before. Duration of Task 1 and Task 2 will be:
Task 1 has duration of 0,88 days, and Task 2 duration of 1,75 day.
Now, you know the duration formula, don’t you?
Duration of one day means 8 hours. We will work 7 hours on Task 1 (because we put that in the calendar; from 08:00 till 15:00). 7 working hours / 8 hours per day in scheduling options = 0,88 days.
For Task 2 we will work 7 hours on 22.03.11 and 7 hours on 23.03.11 so it means we will spend 14 hours in total. And 14 working hours / 8 hours per day in scheduling options = 1,75 days.
Now, suppose that in my calendar I choose the working time from Monday till Friday from 08:00 – 17:00 (9 working hours). Duration of Task 1 and Task 2 will be:
Task 1 has duration of 1 day, and Task 2 duration of 2,13 day. Duration of one day means 8 hours. We will work
8 hours on Task 1 (because we put that in the calendar; from 08:00 till 17:00). Something is wrong, isn’t it? From 08:00 till 17:00 is 9 hours and not 8. Well,  yes it is. But you cannot work more than 8 hours per day if start and end date are the same because in scheduling options you said that you will have 8 hours
per day. So 8 working hours / 8 hours in scheduling options = 1 day.
For Task  2 we will work 9 hours on 22.03.11 and 8 hours on 23.03.11 so it means we will spend 17 hours in total. And 17 working hours / 8 hours in scheduling options = 2,13 days. You may ask yourself: “WHAT IS
WRONG NOW!??”.
Well, nothing is wrong. That is the way MS PROJECT works. If your start date is different from end date, MS PROJECT will respect working hours from calendar (in our example it is 9 hours / day) for first, second, third etc day EXCEPT last day (end date) which will last 8 hours (hours per day from scheduling options).
See you

So MS PROJECT calculates duration in formula 4 working hours / 8 hours per day in scheduling options = 0,5 days
For Task 2 I said that it will start on 22.3.11 and it will end on 23.3.11. Working time will be from 08:00 till 12:00 (4 hours), so it will be 2 days X 4 hours = 8 hours
And because the day duration lasts 8 hours (see picture above) MS PROJECT calculates duration in formula 8 working hours / 8 hours per day in scheduling options = 1 day
Now, suppose that in my calendar I choose the working time from Monday till Friday from 08:00 – 15:00 (7 working hours) and I put the same start and end date for Task 1 and Task 2 as I put before. Duration of Task 1 and Task 2 will be:
Task 1 has duration of 0,88 days, and Task 2 duration of 1,75 day. Now, you know the duration formula, don’t you? Duration of one day means 8 hours.
We will work 7 hours
on Task 1 (because we put that in the calendar; from 08:00 till 15:00). 7 working hours / 8 hours per day in scheduling options = 0,88 days.
For Task 2 we will work 7 hours on 22.03.11 and 7 hours on 23.03.11 so it means we will spend 14 hours in total. And 14 working hours / 8 hours per day in scheduling options = 1,75 days.
Now, suppose that in my calendar I choose the working time from Monday till Friday from 08:00 – 17:00 (9 working hours). Duration of Task 1 and Task 2 will be:

Task 1 has duration of 1 day, and Task 2 duration of 2,13 day.
Duration of one day means 8 hours. We will work 8 hours on Task 1 (because
we put that in the calendar; from 08:00 till 17:00).
Something is wrong, isn’t it? From 08:00 till 17:00 is 9 hours and not 8. Well, yes it is. But you cannot work more than 8 hours per day if start and end date are the same because in
scheduling options you said that you will have 8 hours per day. So 8 working hours / 8 hours in scheduling options = 1 day.
For Task 2 we will work 9 hours on 22.03.11 and 8 hours on 23.03.11 so it means we will spend 17 hours in total. And 17 working hours / 8 hours in scheduling options = 2,13 days. You may ask yourself: “WHAT IS WRONG NOW!??”. Well, nothing is wrong. That is the way MS PROJECT works. If your start date is different from end date, MS PROJECT will respect working hours from calendar (in our example it is 9 hours / day) for first, second, third etc day EXCEPT last day (end date) which will last 8 hours (hours per day from scheduling options).

See you …..

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management | 4 Comments

MS Project 2010 – Let’s start

Hi,

Let’s Go! How will you start MS PROJECT 2010?

You will see this:

  1. The Quick Access toolbar is an area of the interface where you can put your favorite commands (like undo, save, redo etc.)
  2. The Tab group focus area of Project together (like file, task, resource,
    project
    etc)
  3. The Group is a collection of related commands under one tab (like schedule group under task tab where you can find commands like link tasks, unlink tasks, indent tasks etc)
  4. Command is a specific action which is performed when you choose it (like cut, copy, paste, etc)
  5. The View Label is placed along the left edge of the active view. Because MS Project has many views, it is a very helpful reminder of “where you are” i.e. what active view you are using at the moment
  6. With the View shortcuts you can easily and quickly switch between some of the views in MS project (like gant chart, task usage, team planner and resource sheet)
  7. The Zoom slider zooms the active view in or out
  8. The Status bar displays some details like the scheduling of new task, filters applied etc.)

If you are using any of the Office 2010 applications you are familiar with the term Backstage view. You can get there easily. Just click on the File tab. If you
don’t know which version of MS project you have you can find it here:

I decided to show you how the MS Project works with the example of one simple project. The project will be: “Home, sweet home” and it major goal (objective) is to build a house.

What we have to do first is write the project information in MS project. We will do it like this:

You can put the project information here:

Other informationabout the project you can put here:

You can choose between two constraints: Start date (you want your project to start at
specific date) or Finish date (you want your project to finish at specific date), but NOT BOTH.

Finally, you should save your project. You will do it like this:

Next time we will start with scheduling.

See you!

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management | 2 Comments

Project Management and MS Project 2010 – 09.02.2011

Hi,
Before I start my explanation on how MS Project 2010 works I have to tell you some more things about Project itself, as well as some things you should pay attention to in your projects. In many books and articles you can find something called “ the triple constraint” or “the project triangle”.

It says that each and every problem has tree constraints: Time, Costs (or Resources) and Features (or Scope). This is somewhat true. Every project also has other constraints like quality, communication, risks, etc. Some constraints can be fully tracked with MS Project (like time, costs, and resources), some can be partially tracked (like risks and communication), and some cannot be tracked at all (like quality, and change request approval).
So, you must have other tools and techniques besides MS Project to track and
manage Project.

Every project is undertaken for some reason, whether it is for a bigger profit,
better position in marketplace, saving the earth or just for the fun of it
(like: “I want to  build  and live in the biggest house in my town). Regardless
of why a project is undertaken, you must know that project sponsor and your
customer will have requirements and expectations. Many people think that those
two words have the same meaning. Well, it is the biggest mistake you can make
and it can cause the project failure.

Requirements are customer’s wishes which he or she  will tell you! For example: “We want a new ERP system with modules: purchase, sale, invoicing, marketing, production, human resources, fixed assets etc.” To get the requirements you have to ask: “What do you need?”. Very simple, isn’t it?

On the other hand, expectations are unstated wishes! Your customer can have a requirement like this: “I want a new ERP system with (by the others) vendor ledger!” and the expectation that one person will be able to record 10.000 vendor invoices in one hour. To get the expectations you have to ask: “We have all your requirements! What exactly do
you expect from this project? What is your measure of success?”.

When you get the customer expectation you must make a decision: “TO GO OR NOT TO GO!” also called “GO – NO GO” decision. If you know that your customer’s expectation
is unreachable no matter what you do, DO NOT START THE PROJECT. If you do, you
will get unsatisfied customer even if you fulfill all the requirements.  YOU will be the one responsible for the project failure. And after all, this is unethical Project Management because you have started the Project for which you knew that it wouldn’t be successfully
completed, and that you would end up having unsatisfied customer.

And for the end of this post one joke from the internet. Project phases:

Enthusiasm, Confusion, Loosing Illusions, Nerves breakdown, Panic, Looking for “the Pedro”, punishing the innocent team members, Looking for trade-off, Giving the reward
to the people who have never been involved in the project.

See you.

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management | 1 Comment

Project Management and MS Project 2010

Hi,
I decided to write a blog about Microsoft Project 2010. What is the purpose of this blog?
Simply, to explain how the MS Project 2010 really works in conjunction with Project Management.
What is Microsoft Project? Dumb question, isn’t it? In many books and articles you can read that MS Project is: “Project Management Software!”
Well, it is NOT.
There is no such a thing like “Project Management Software!”
Project Management is: “The application of knowledge, skills, tools, and techniques to project activities to meet project requirements.”
Well, MS Project is a strong and powerful tool and if you use it properly you can save a lot of time with less effort in your project.

If you want to get the most out of MS Project you have to be excellent at two things.
You have to know what the possibilities of MS Project are and how to use them, and you also have to know how to manage projects (Project Management).
OK. What is a Project? “Project is temporary endeavor undertaken to create a unique product, service or result” (PMBOK. 4th edition).

It is temporary (so it must end or it must be terminated) and it is unique. That means that there are no two same projects.
Well, there are a lot of similar projects but not the same. Some of the pieces that can be different are a project team, customer, budget, scope, or something else.
What can you do with MS project? You can put your tasks in it, your schedule, resources, costs (also known as triple constraint), and you can track the progress of your project.
How far will you go with MS Project? Well, it depends. For example, if you do not have access to cost information (about pay rates for your project team) then you will not be able to track costs of your project.

If you don’t have enough information about your resources then you will not be able to track your tasks by assigned resources etc., etc.
Some project managers are “software averse” which means that they hate any kind of software and they prefer using “paper and pencil” during the project.
This method is slow, it makes project communication hard, and you have to use great effort of “writing things down”.
This is a waste of time even if your Project is “on track”. On the other hand, there are “software freaks”.
They are using MS project every day, every hour, every minute and they put everything in it, no matter if it is a part of project or not.
(A friend of mine is a “software freak”, and he even writes a daily weather report in MS project, and MS word. I asked him: “Why are you doing this? Is the weather report important for your project?” The answer was: “Not at all, but, you know, just in case!” “How much time do you spend every day on collecting weather report, and putting that information in MS project?” He says: “Not much. About an hour!!”
What is he doing? He is wasting at least 20 hours per month on collecting and tracking useless information.

So, how far do you go with MS project in your particular project? As far as you get the right results with less effort.
For example, if you don’t know the cost per person (it might be 100$ per hour or 200$, or 500$) don’t put that information in MS project. You will be misguided. Track any information that is important and accurate (reliable).
Next time I’m going to start with MS project from the scratch.

See you.

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management | 4 Comments

About work and cost type of resources and problems when assigning them to the task – PART 2.

In this post I will continue with work and cost type of resources and problems when assigning them to the task.

As I mentioned in my previous blog, there are three types of resources:

  1. Work resource. This type of resource
    includes people and equipment needed to complete the task in a project
  2. Cost resource. This type of resource includes financial cost which does not depend on the duration of task, for example airplane ticket
  3. Material resource. This type of resource, also called consumable, is the resource you need to complete the task in a project, for example bricks, concrete etc.

First I will define resources needed for my task.

John the Trainer is Work resource and his standard rate is $100 per hour.
Airplane ticket is Cost resource and it does not have the defined price yet.

Now I will define task called Training

In the first example I will assign only cost resource to the task.

I assign Airplane ticket to the task and I told the MS project that it costs $1000.

I will now assign John the Trainer to the task.

And I got:

Duration, Start and Finish date are the same, so everything seems O.K

Here is another example. Suppose that I assigned only cost resource (Airplane ticket) to the Task (as it is shown in 3rd picture above). Now I will mark the task as 100% completed.

Everything looks fine! But, suppose that you forgot to assign John the Trainer to the task AFTER you marked the task 100% completed. I will assign John now:

Now look what happens:

Duration is now 0 days (milestone???) with unchanged Start and End date?
It seems like a bug. And you will get the same thing if you assign both resources (Airplane
ticket and John the Trainer) to the task and then, after you mark the task as
100% completed, you remove John the Trainer.

What will happen if you do not have cost resource (airplane ticket) assigned with
the task, and you assign Work resource (John the Trainer) with the task AFTER you
mark the task 100% completed? I will assign John now:

and I will get:

So, obviously the problem is with the cost resource type (in our example the Airplane ticket).

What is the solution? If you have to add or remove work resource to the task after it is completed (25%, 50%, 75%, or 100%) first mark the task as 0% completed, then add or remove the resource to the task and after that mark task as completed again.

I will show to you what happens if I add Work resource (John the Trainer) with the task AFTER I marked it as 50% completed and I already have work resource assigned to the Task. I will assign John now:

and I will get:

Duration is only 50% of expected (1,5 day instead of 3 days) and this is bug.

So, once again, first mark the task as 0% completed, and then add or remove the resource to the task and after that mark task as completed again.

See you,

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management | 2 Comments

About work and cost type of resources and problems when assigning them to the task.

In this post I will write about work and cost type of resources and problems when assigning them to the task.

There are three types of resources:

  1. Work resource. This type of resource includes people and equipment needed to complete the task in a project
  2. Cost resource. This type of resource includes financial cost which does not depend on the duration of task, for example airplane ticket
  3. Material resource. This type of resource, also called consumable, is the resource you need to complete the task in a project, for example bricks, concrete etc.

First I will define resources needed for my task.

John the Trainer is Work resource and his standard rate is $100 per hour.
Airplane ticket is Cost resource and it does not have the defined price yet.

Now I will define task called Training

In the first example I will assign only cost resource to the task.

I assigned Airplane ticket to the task and I told MS project that it costs $1000.

Now I will switch the table to the Cost table:

and I get:

You can see that Total cost for The Training task is $1000, Baseline is $0 (since we did not create the baseline), Variance is $1000 (since we did not create the baseline), Actual cost (e.g. spent cost for the task) is $0 (because we did not start with the task) and Remaining cost is $1000.

Now I will tell the MS Project that the task is 100% completed:

You can see that Actual cost (e.g. spent cost for the task) is $1000 (because we have completed the task) and Remaining cost is $0.

O.K. everything works fine. Now let’s see another example. What happens if we assign cost and work resource on the same task?

I assign Airplane ticket to the task and I told the MS PROJECT that it costs $1000, and John the Trainer, and MS PROJECT calculate the amount of $2.400 (which is 3 days * 8 hours * $100 per hour = $2.400). So the total cost for the task should be $3.400.

Now I will switch the table to the Cost table again:

and I get:

You can see that Total cost for The Training task is $3.400, Baseline is $0 (since we did not create the baseline), Variance is $3.400 (since we did not create the baseline), Actual cost (e.g. spent cost for the task) is $0 (because we did not start with the task) and Remaining cost is $3.400. Everything looks fine.

Now I will tell the MS Project that the task is 100% completed:

You can see that Actual cost (e.g. spent cost for the task) is $2.400 and Remaining cost is $1.000. What does it mean? It means that MS project left cost resource unspent even though the task is 100% completed. It only spent work resource ($2.400 for John the Trainer) and not cost resource ($1.000 for the airplane ticket). And this (from my point of view) is BUG.

What can you do? Well, in our example, do not define or assign cost resource to the task. Instead of that assign only John the Trainer (Work resource to the task):

Then switch to the cost table and in Fixed cost field type $1.000. Fixed cost works the same as cost resources but with cost resources you can have “rollout” and analyze all (for example) airplane tickets.

You can see that Total cost for The Training task is $3.400, Baseline is $0 (since we did not create the baseline), Variance is $3.400 (since we did not create the baseline), Actual cost (e.g. spent cost for the task) is $0 (because we did not start with the task) and Remaining cost is $3.400.

Now I will tell the MS Project that the task is 100% completed, again:

You can see that Actual cost (e.g. spent cost for the task) is $3.400 (because we have completed the task) and Remaining cost is $0. So, if you use fixed Cost instead of Cost Resource you will get the expected result.

And If you want to know where this $1.000 Fixed cost came from you can write it on task note:

See you..

Posted in Microsoft PRoject 2010, MS PROJECT 2010, PMI, PRoject Management, Uncategorized | 2 Comments