How do I create a project without actual dates? (where every mont.

C

cn_public

I want to develop a proposed project plan and I don't know the actual
starting date. So the dates must be Month 1, 2... or Week1, 2.... Also, I
would prefer to define the duration of tasks in months. Therefore when a task
start at the middle of Month 1 and has a duration of 12 months, it has to
finish in the middle of Month 13. To do this I have to define that month=30
days but also that every month has 30 days.
Any idea is welcome.
 
S

Steve House

The calendar in Project is the same calendar as in the real world - it has
12 months, 365 days, 24 hours per day, etc and you can't change it. The
Project settings for the Base Calenders in the ChangeWorkingTime allow you
to designate which hours and days on the calendar are working time (since
that's all that Project schedules usually care about) and which hours
aren't. The calendar options page in the Tools Options menu allows you to
designate the conversion factors Project uses to calculate the number of
work hours you mean when you input duration in days, weeks, or months since
it stores all its duration information in working minutes. Using the
default settings, when you say a task has 12 month's duration, that means it
has 12 months * 20 WorkDay/month * 8 WorkHr/day * 60 WorkMin/hr minutes of
duration (115200 working minutes). If you say the task begins 8am 15 Jan
2005, Project looks at the Project calendar and sets the finish date/time to
whenever that 115200 working minutes, as defined as working time in the
calendar, have elapsed. Depending on what your calendar says are working
minutes, holidays, work days, that finish might or might not be Jan 15 2006,
indeed, probably won't be.

Another option for such broad date ranges is to use elapsed time months,
entered "emon," rather than duration months. Normally this is a very bad
idea but at this apparently early stage of planning it might work for you.
An elapsed month ignores working time calendars, has a constant 30 days, and
so the year has 360 days. A task starting Jan 15th with a duration of 12
emon will end Jan 10th the following year.

FYI, the general rule of thumb is to try to have the WBS broken down to
where individual task fall somewhere between 8 and 80 hours duration. Tasks
measured in months usually are summary or phases that involve many discrete
activities or work packages. Managing the project means managing all of
those individual work packages, a specific observable physical activity
performed by an individual resource. It's not enough to say "erect
factory" - you need to break that summary down to the level of all of the
hundreds or thousands of individual pieces of work that goes into building a
factory so you can tell the electrician to show up on the 10th of March with
the tools and parts necessary to wire switch panel 3-A located on the west
wall of the south equipment bay and you estimate he'll be done by the 12th
so you can tell the crew installing the widget stripper they can do a first
power-up test on that date.

You do have to have a definite start date for your plan but it doesn't have
to be engraved in granite. Just arbitrarily pick a convenient date, plan
based on it, then change it later when you have a better idea of when it
will actually might be. It's easily done with the "Change Starting Date"
tool, just takes a couple of mouse clicks. You can choose a time format for
your Gantt chart timescale that shows relative months and weeks from the
Project start if you like.

Hope this gives you some ideas ...
 
C

chrisnik

Thanks Steve,
you are right about the need for brake down in small tasks.
However, if you are in the phase of proposal for a 3 years project , you
cannot and probably you don't want, to define the work in detail. It's very
common in project proposals to say that Task X start at T0, has a duration of
3.5 months and finish at T0 + 3.5 months.
It would be nice to be able to define an hypothetical callendar with 12
months and 30 days per month. However this cannot be done in MSP.
It seems that I have to use a simpler tool just for presentation and not
for actual project management.
However, I appreciate your prompt and detailed answer.
Christos
 
G

Gary L. Chefetz \(MVP\)

Chris:

This certainly can be done in project. Try modeling your task durations
based on e-days (elapsed days). You should consider a basic course in
Microsoft Project. Many people like to use Project as Gantt chart drawing
tool, but fail to realize that the Gantt chart is a by-product of the
schedule you create in Project. Learning to create good schedules requires
more finesse than simply drawing bars across a calendar representation.
Perhaps Visio would be a better tool for you if you're only trying to draw
a Gantt chart.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
 
S

Steve House

Using elapsed time will allow you to specify your task durations themselves
in terms of equal length 30 day months. The Gantt chart time scale though
is a real civil or fiscal calendar so its months are their actual lengths
even when you display the labels as months from start. If month 1 begins 1
Sep, month 2 starts 1 Oct and month 3 starts 1 Nov and the labels read Month
1, Month 2, Month 3. Since this is a proposal and the durations you list
are going to be very very rough order-of-magnitude approximations until you
develop the actual WBS anyway, does it really matter if the timescale months
are slightly unequal? Would using weeks instead of months in the timescale
solve the problem if it is?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top