Dependencies/fixed dates/duration/messing it all up

[AC]

MS Project 2000 keeps messing it all up and I cannot for the life of me
figure out why. I've got a bunch of sub-tasks that are all linked
end-to-start. I'll try to explain:

A
->B
->->C
->->D
->->E
->F

C, D and E are children of B; F is a successor of B; C, D and E are all
linked end-to-start.

I keep adding into the list containing C, D and E as the project goes
on. For some reason, F is now not starting when E finishes. If I add
task G as a child of B, successor to E, I get a conflict error - "Task
G has a task constraint or is linked to a task that cannot move, and as
a result the constraint or the link cannot be set. (Cancel/continue)"
It highlights the dependency in task F.

I notice that task F's start date is set to task E's start date
(whether coincidence or not I have no idea.)

If I unlink C, D and E, I'd expect their start dates to go back to the
project start date but they don't. Maybe by setting them to complete,
I've set the end date??? How do I undo fixed dates?

Any ideas? I'm flummoxed.

Thanks for your time,
AndyC

 

[AndyC]

OK so maybe it's just as simple as "how do I unset a fixed date"? I've
tried to go back to the start by unlinking everything, removing all
child relationships, etc. But now when I get back to the point where I
link all the tasks, they all start on the project start date rather
than chaining end-to-start. I reckon if I could just remove the fixed
start date I'd be there. But I can't do it. It must be possible?????

Heeeeeeeeeelp.

AndyC

 

[Jan De Messemaeker]

Hi Andy:

Just to make sure
Select all tasks
Right-Click, select task information
On the General Tab enter 0 as percent complete
On the Advanced tab enter As Soon as possible as a constraint type
Then, unless you have been linking task dates through Paste Link, all tasks
are "free" and you will be able to see relationship logic fully

Some advice though
- Do not link summary tasks, the consequences aren't easy to oversee
-And NEVER enter data in Start or Finish fields - that creates unexpected
constraints.
HTH

 

[Jan De Messemaeker]

Hi Andy,

That's different.
In Tools, Options, Calculation, set calculation to Automatic.
HTH

 

[AndyC]

Brilliant! That's it - something to do with the fact that the tasks
were 100% complete. Presumably I'm using it wrong somehow.

Would there be any chance you could give a quick summary of how to go
about using project to manage this scenario: I'm managing a software
project that is 100% bug fixes. I've categorised them into a plan of
attack - which is what's on my plan. When Joe Bloggs starts a bug he
invariably needs to talk to whoever logged it. At this point, I mark
the task 5% complete to indicate he's started. Sometimes, the person
who logged the bug isn't available so Joe moves onto the next bug and
will come back to the first when he gets to a convenient break. When
the bug is complete and tested, I mark the task 100% complete, even
though potentially the previous task(s) is/are still only 5% complete.
Possibly, all tasks that are linked finish-to-start are linked that way
because I only have a single resource for those bugs. Should I be
linking them differently? Should I use something else to keep track of
complete'ness/completion dates and resource availablility?

I appreciate this is a fairly high level FAQ on project - maybe you
could point me at a good "how-to-use" website? Obviously I've tried
project help and msdn...

Thanks again,
AndyC

 

[Sarah]

Andy,

The only predecessor/successor links you should be using are ones that
dictate the actual flow of work. You do not seem to be using them
correctly. You should never use links just to order the work. If Joe
Bloggs could potentiall work on any one of his bugs at any point in
time, in no particular order, then you should not link them in any
particular order. Changing the % complete for a task is fine, as long
as you pay attention to the Actual Start and Actual Finish dates while
you do so. If Task A is scheduled to start on March 3 but I start it
today and mark it as 5% complete, Project will probably set the Actual
Start date to March 3, instead of today. Just always be careful that
all Actual data fields match reality, don't use links unless they are
logically necessary for the order of work to progress, and you'll have
a good start. I would, however, recommend a good 2 day course in using
Project, because most people have problems understanding the
calculations and why the software does what it does when you change
something.

SarahK

 

[Jan De Messemaeker]

Hi Andy,

1. You shouldn't link them since there is no link. Assign the resource then
do Resource Leveling.
As you have noticed, putting dummy links seriously increases the work.

2. When you work like this I would have 2 tasks for each fix... taking
notice and fixing. That wilkl better reflect that teh fiwing hasn't begun.

HTH

 

[Mike Glen]

Hi Andy,

Welcome to this Microsoft Project newsgroup

You might like to have a look at my series on Microsoft Project in the
TechTrax ezine: http://tinyurl.com/2xbhc or this:
http://pubs.logicalexpressions.com/Pub0009/LPMFrame.asp?CMD=ArticleSearch&AUTH=23
(Perhaps you'd care to rate the article before leaving the site,
Thanks.)

FAQs, companion products and other useful Project information can be seen at
this web address: <http://www.mvps.org/project/>

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP