comments on: how to do rolling wave planning in primavera p6 - 瑞士vs喀麦隆足彩赔率

by: mudassir

sat, 12 jun 2021 08:29:59 +0000

superb! michael. this technique is super fast and easy to understand.

cheers!

]]>

by: michael lepage

thu, 21 mar 2019 15:58:45 +0000

gustavo rezende. awesome to hear!]]>

by: gustavo rezende

wed, 20 mar 2019 21:22:58 +0000

hi michael,
thanks for your sharing about level of effort activity, it is being very helpfull for my work.
not only for rolling wave planning aplication i think it can be also applyied for time controlled buffers that will expand or contract depending on related activities peformances.
also it can be used for reporting pdf file to client whitout detailed information. that way the creation of level of effort activity would happen after the detailes tasks.
i appreciate your comments on my post.
regards.

]]>

by: michael lepage

wed, 11 apr 2018 20:52:32 +0000

atef. true, using ms project it's easy to expand an activity with further sub-activities.]]>

by: atef

tue, 10 apr 2018 06:58:04 +0000

this is why ms project is better in this point

]]>

by: michael lepage

tue, 20 mar 2018 18:25:42 +0000

in reply to nigel simmons.

hi nigel,
thanks for the comments.
setting relationships on the loe – it’s appropriate either my way or your way – the result is the same as far as i can tell.

i do transfer the “previous predecessors” and successors to the detailed activities in the video. there aren’t many to transfer, so it happens fast. did i miss something else?

to your point, there is increased risk that a mistake is made in adding and removing logic to make this work.

]]>

by: nigel simmons

mon, 19 mar 2018 10:41:09 +0000

michael,
succint as always. i have used the technique to elaborate on the detail whilst keeping the continuity with previous programmes. the technique uses activity id subscripts as part of an inteligent id strategy to assist filters, searches etc. however the main point is the method of linking into the schedule. i have previously insisted to collegues that the correct relationship is to have the loe activity as a successor to the 1st and last detailed task. i.e it only has predecessors (ss or fs and ff or sf) as appropriate to the nature of the linked activities. also previous predecessors should be transferred to the relevant detail task and sucessors should link from the relevant detailed task. this makes a lot of work with icreased risk that the logic is not preserved. i notice you make no reference to the existing logic when the status is changed from activity to loe.
regards,
nigel

]]>

by: michael lepage

fri, 09 mar 2018 20:35:28 +0000

elmer. glad you liked it elmer.]]>

by: michael lepage

fri, 09 mar 2018 20:35:10 +0000

ali. thank you ali!]]>

by: elmer

fri, 09 mar 2018 06:23:42 +0000

i find the video very knowledgeable and interesting.

thank you.

]]>

by: ali

thu, 08 mar 2018 22:14:28 +0000

hi michael,

this is great solution and excellent description as always.
since i started with your courses i learned a lot of informative subject .
much appreciated!!!

ali

]]>