Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

Beartracks

(14,157 posts)
3. Oddly, this is not, in fact, a "project" that we are working on.
Wed Dec 16, 2020, 01:14 AM
Dec 2020

It's just a sequence of events in a contract: "If a certain event happens, then that kicks off this process which can be no longer than X months, after which the customer has X amount of time to decide if they want to do such-and-such, and if they do then they need to give X days' notice before they can implement this-or-that, at the end of which they can terminate the contract -- but only on a specific day of the year."

We are trying to clarify this process -- not, in fact, manage an actual project. Basically, we are needing to demonstrate that in any case the process cannot play out as short as the customer would like it to be.

But if MS Project would be the way to go, I could probably learn enough to chart the steps and their relationships, even if I do need to run it and save a graphic file for multiple scenarios (in order to satisfy all the "what if" questions).

==================

Recommendations

0 members have recommended this reply (displayed in chronological order):

Latest Discussions»The DU Lounge»Timeline variables - how ...»Reply #3