Task start date doesn't change after completed predecessor

[Konstantin]

Hi,

I've got a little problem.
In WBS I have 11 similar tasks (programming). All of them goes one
after another.
Task number 10 has start date (calculated) at 05.08.09 (DD.MM.YY) and
finish date 08.08.09.
But responsible user completed that task much earlier (at 17.07.09). I
approved his timesheet and after publication task number 10 marked as
100% completed.
But the problem is that task 11 still has same start date as before
(09.09.09). What did I wrong and is there any way to make tasks start
moving towards the date of predecessor's end?

Thank you

 

[Rod Gill]

Have to ask, the second task is linked to the first, has no progress and has
no date constraint?

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[Konstantin]

Yes, task 10 linked to task 11 using finish-start link. Task 11 has no
date constraints. Planning from start of project.
By the way, for all predecessoss that were completed before planned
time (tasks from 4 to 10), time of finish didn't change either. They
marked 100% complete, date of finish shows, for instance, 05.08.09,
day long ahead of today .

 

[Dytham]

Sounds like you need to correct the date that the completed tasks finish, not
just mark them as 100% at a date in the future ?

 

[Konstantin]

Well, sounds like it may work, but I'm looking for solution, not for
just a corective action.
I think, that source of problem here based on user's action (he did
not put time which he spent on tasks in actual dates in timesheet
(instead of this he just click Send button). Of course that fault was
totally my, not his.

 

[Gary Chefetz]

Konstantin:

It sounds as though you are using percent complete tracking method. The
problem here is that if you do not collect an actual finish date from the
user, or the project manager does not change the actual finish date, the
system will assume that everything happened as planned whether or not the
current date is earlier or later than the planned start or finish. You
should add the actual start field and actual finish field to the My Tasks
view, and have your resources report this information along with percent
complete. Only then, will the system reschedule the successor tasks to begin
earlier or later as the case may be.

 

[Konstantin]

Konstantin:

It sounds as though you are using percent complete tracking method. The
problem here is that if you do not collect an actual finish date from the
user, or the project manager does not change the actual finish date, the
system will assume that everything happened as planned whether or not the
current date is earlier or later than the planned start or finish. You
should add the actual start field and actual finish field to the My Tasks
view, and have your resources report this information along with percent
complete. Only then, will the system reschedule the successor tasks to begin
earlier or later as the case may be.

--
Gary L Chefetz, MVP, MCT, MCITP
msProjectExpertshttp://www.msprojectexperts.com
FAQs and Referencehttp://www.projectserverexperts.com
BLOG:http://projectserverhelp.com







- Показать цитируемый текÑÑ‚ -

I'll do it that way. Thank you, Gary and all who paid attention.

 

[Reid McTaggart]

Alternatively, you could set Tools > Options > Calculation so that at least
the first two boxes are checked in the section called Calculation options for
'[project name]' and properly set the Status Date under Project > Project
Information

 

[Gary Chefetz]

Reid:

I don't believe that deals with the actual start and finish date issue.
These cannot be accurately represented without capturing them explicitly
when you use percent complete tracking, with the possible exception of
processing updates on a daily basis.

Alternatively, you could set Tools > Options > Calculation so that at
least
the first two boxes are checked in the section called Calculation options
for
'[project name]' and properly set the Status Date under Project > Project
Information
--
Reid McTaggart
bluebadges.com

Konstantin:

It sounds as though you are using percent complete tracking method. The
problem here is that if you do not collect an actual finish date from the
user, or the project manager does not change the actual finish date, the
system will assume that everything happened as planned whether or not the
current date is earlier or later than the planned start or finish. You
should add the actual start field and actual finish field to the My Tasks
view, and have your resources report this information along with percent
complete. Only then, will the system reschedule the successor tasks to
begin
earlier or later as the case may be.

 

[Reid McTaggart]

No argument there, Gary. Your good advice goes beyond the original question,
into "best practices" territory, whereas my input was more narrowly focused
on just what Konstantin said he wanted to achieve.

Depending on how much authority Konstantin has to re-configure Project
Server, either answer could be useful... I think. ;-)

Thanks!

--
Reid McTaggart
Blue Badges LLC
bluebadges.com

Reid:

I don't believe that deals with the actual start and finish date issue.
These cannot be accurately represented without capturing them explicitly
when you use percent complete tracking, with the possible exception of
processing updates on a daily basis.

Alternatively, you could set Tools > Options > Calculation so that at
least
the first two boxes are checked in the section called Calculation options
for
'[project name]' and properly set the Status Date under Project > Project
Information
--
Reid McTaggart
bluebadges.com

Konstantin:

It sounds as though you are using percent complete tracking method. The
problem here is that if you do not collect an actual finish date from the
user, or the project manager does not change the actual finish date, the
system will assume that everything happened as planned whether or not the
current date is earlier or later than the planned start or finish. You
should add the actual start field and actual finish field to the My Tasks
view, and have your resources report this information along with percent
complete. Only then, will the system reschedule the successor tasks to
begin
earlier or later as the case may be.



Yes, task 10 linked to task 11 using finish-start link. Task 11 has no
date constraints. Planning from start of project.
By the way, for all predecessoss that were completed before planned
time (tasks from 4 to 10), time of finish didn't change either. They
marked 100% complete, date of finish shows, for instance, 05.08.09,
day long ahead of today .

On 20 июл, 13:54, "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote:
Have to ask, the second task is linked to the first, has no progress
and
has
no date constraint?

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA,
see:http://www.projectvbabook.com



Hi,

I've got a little problem.
In WBS I have 11 similar tasks (programming). All of them goes one
after another.
Task number 10 has start date (calculated) at 05.08.09 (DD.MM.YY)
and
finish date 08.08.09.
But responsible user completed that task much earlier (at 17.07.09).
I
approved his timesheet and after publication task number 10 marked
as
100% completed.
But the problem is that task 11 still has same start date as before
(09.09.09). What did I wrong and is there any way to make tasks
start
moving towards the date of predecessor's end?

Thank you

 

[Gary Chefetz]

IMO, this is fundamental knowledge. I see many organizations believe that
using percent complete is an "easy" way to track a project, but completely
misunderstand the consequences to tracking accuracy. All organizations need
to determine the importance of an accurate execution record as this is much
more difficult to maintain when using percent-complete, and adds more data
entry burden than using hours by day. Konstantin's query is a frequently
asked question and changing configuration settings is always a possible
solution component in reconciling system behavior with desired results.

No argument there, Gary. Your good advice goes beyond the original
question,
into "best practices" territory, whereas my input was more narrowly
focused
on just what Konstantin said he wanted to achieve.

Depending on how much authority Konstantin has to re-configure Project
Server, either answer could be useful... I think. ;-)

Thanks!

--
Reid McTaggart
Blue Badges LLC
bluebadges.com

Reid:

I don't believe that deals with the actual start and finish date issue.
These cannot be accurately represented without capturing them explicitly
when you use percent complete tracking, with the possible exception of
processing updates on a daily basis.

Alternatively, you could set Tools > Options > Calculation so that at
least
the first two boxes are checked in the section called Calculation
options
for
'[project name]' and properly set the Status Date under Project >
Project
Information
--
Reid McTaggart
bluebadges.com


:

Konstantin:

It sounds as though you are using percent complete tracking method.
The
problem here is that if you do not collect an actual finish date from
the
user, or the project manager does not change the actual finish date,
the
system will assume that everything happened as planned whether or not
the
current date is earlier or later than the planned start or finish. You
should add the actual start field and actual finish field to the My
Tasks
view, and have your resources report this information along with
percent
complete. Only then, will the system reschedule the successor tasks to
begin
earlier or later as the case may be.



Yes, task 10 linked to task 11 using finish-start link. Task 11 has
no
date constraints. Planning from start of project.
By the way, for all predecessoss that were completed before planned
time (tasks from 4 to 10), time of finish didn't change either. They
marked 100% complete, date of finish shows, for instance, 05.08.09,
day long ahead of today .

On 20 июл, 13:54, "Rod Gill" <rodATproject-systemsDOTcoDOTnz> wrote:
Have to ask, the second task is linked to the first, has no
progress
and
has
no date constraint?

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA,
see:http://www.projectvbabook.com



Hi,

I've got a little problem.
In WBS I have 11 similar tasks (programming). All of them goes
one
after another.
Task number 10 has start date (calculated) at 05.08.09 (DD.MM.YY)
and
finish date 08.08.09.
But responsible user completed that task much earlier (at
17.07.09).
I
approved his timesheet and after publication task number 10
marked
as
100% completed.
But the problem is that task 11 still has same start date as
before
(09.09.09). What did I wrong and is there any way to make tasks
start
moving towards the date of predecessor's end?

Thank you