beyond basic scheduling issues

[Ammar Al-Saket]

Hi Everyone,

What are overall recommendations (best practices) that planner needs to keep
in mind while developing a project schedule on MSP “beyond basic scheduling
issuesâ€. e.g. [critical path to look in certain way; total slack not to
exceed certain number; preference of use certain constrains or task types;
use of lag-lead in certain way; create buffer zone(s) …etc].

I do understand that each project is unique, and each project requires its
own arrangements, However, I also, think that there are some overall
scheduling selections that would lead to effective implementation of project.


Any contribution would be highly appreciated and thank you in advance…
_____
AS

 

[Dave]

One thing I think is often overlooked is to have sufficient 'stages'. A
stage need not describe a functional part of the project 'development',
'initiation', 'testing' etc. Rather the project should be broken up
into stages which don't exceed 3 months. In order to build in
contingency, they I have 'contingency' tasks between the stages to which
I add the project team.

The other thing to be aware of is to have properly defined tasks where
it is clear what the work for that task is and to make sure the range of
tasks properly cover the entirety of the work in the project. All too
often I see people saying 'I added a meeting to the schedule because
somebody arranged a new one'. That means the schedule is documenting
the day-to-day activities rather than driving the work. Why weren't
meetings thought of in the first place. Add contingency to cover the
things that haven't been thought of.

Make sure the team know what the project is. It isn't enough that they
know they are developing software module X. They should know that the
project has to deliver 3 units. Those units have to be installed in 2
geographically diverse sites and tested. Operational procedures need to
be developed before the project can finish. Make the entire team read
the project proposal and ask them questions on it in team meetings.

 

[vanita]

Hi AS

Always group your project activities into series of Summary tasks. The
Summary tasks represent the upper nodes of WBS and the detailed activities or
the sub-tasks are the activities at the end of each branch of WBS. If the
schedule is grouped like this using the Filter of 'Summary Tasks' from the
detailed schedule you will also be able to generate the Summary Report of the
project required by Senior Management and other stakeholders.

I hope it helps.
Vanita

 

[Michael.Tarnowski]

Hi AS

Always group your project activities into series of Summary tasks. The
Summary tasks represent the upper nodes of WBS and the detailed activities or
the sub-tasks are the activities at the end of each branch of WBS. If the
schedule is grouped like this using the Filter of 'Summary Tasks' from the
detailed schedule you will also be able to generate the Summary Report ofthe
project required by Senior Management and other stakeholders.

I hope it helps.
Vanita
--
Project Management consultant and trainer
(e-mail address removed)

Hi Everyone,

What are overall recommendations (best practices) that planner needs tokeep
in mind while developing a project schedule on MSP “beyond basic scheduling
issues”. e.g. [critical path to look in certain way; total slack not to
exceed certain number; preference of use certain constrains or task types;
use of lag-lead in certain way; create buffer zone(s) …etc].

I do understand that each project is unique, and each project requires its
own arrangements, However, I also, think that there are some overall
scheduling selections that would lead to effective implementation of project.

Any contribution would be highly appreciated and thank you in advance…
_____
AS

Hi AS
an interesting post on this issue maybe "Tracking a schedule: best
practices":
http://groups.google.com/group/micr...+the+left+of+the+status+date#d0d94be1c1732f60

Cheers,
Michael

 

[Ammar Al-Saket]

Thanks Michael its really helpful
___
AS

Hi AS

Always group your project activities into series of Summary tasks. The
Summary tasks represent the upper nodes of WBS and the detailed activities or
the sub-tasks are the activities at the end of each branch of WBS. If the
schedule is grouped like this using the Filter of 'Summary Tasks' from the
detailed schedule you will also be able to generate the Summary Report of the
project required by Senior Management and other stakeholders.

I hope it helps.
Vanita
--
Project Management consultant and trainer
(e-mail address removed)

Hi Everyone,

What are overall recommendations (best practices) that planner needs to keep
in mind while developing a project schedule on MSP “beyond basic scheduling
issuesâ€. e.g. [critical path to look in certain way; total slack not to
exceed certain number; preference of use certain constrains or task types;
use of lag-lead in certain way; create buffer zone(s) …etc].

I do understand that each project is unique, and each project requires its
own arrangements, However, I also, think that there are some overall
scheduling selections that would lead to effective implementation of project.

Any contribution would be highly appreciated and thank you in advance…
_____
AS

Hi AS
an interesting post on this issue maybe "Tracking a schedule: best
practices":
http://groups.google.com/group/micr...+the+left+of+the+status+date#d0d94be1c1732f60

Cheers,
Michael