How can I create a Task dependency with an offset?

  • 1
  • Question
  • Updated 2 years ago
I would like to be able to let a task start after a certain time another task has started or before another task will finish. Currently the Task Dependency does not facilitate this as far as I can see. In MS-Project this is called Lag and is very usefull for project planning

Is this possible and if so how?

If this is not possible would it be possible to have this build into the next update?
I'm using Mindmanager 15

/martin
Photo of Martin van Schooten

Martin van Schooten

  • 6 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Nick Duffill

Nick Duffill, Champion

  • 508 Posts
  • 169 Reply Likes
Hello Martin

I am not aware of any way to specify this. As a workaround, could you insert a delaying task between the end of one task and the start of the next?

Please also feel free to email me at nick at harportconsulting dot com as there might be other solutions :)
Photo of Martin van Schooten

Martin van Schooten

  • 6 Posts
  • 0 Reply Likes
Hello Nick,

Inserting delay-tasks is certainly an option though that would make the diagrams more complex. I've also thought of splitting the one task into a pre-lag and post-lag so that the dependent task can be linked to the right task. That would also increase the complexity of the diagrams.
Photo of Ary Velstra, Expert Trainer

Ary Velstra, Expert Trainer

  • 1248 Posts
  • 187 Reply Likes
Just curious.... Why do you need the time delay?
Photo of Martin van Schooten

Martin van Schooten

  • 6 Posts
  • 0 Reply Likes
Hi Ary,

Let's say Task 1 is scheduled for 3 weeks and forecast is that after 2 weeks that task provides sufficient information to start Task 2.
In that case I would like to be able to create a Start-Start dependency of Task 2 to Task 1 with a Lag of 2 weeks.

This is just one of the examples to use Lag which is very much used in project management.
Photo of Ary Velstra, Expert Trainer

Ary Velstra, Expert Trainer

  • 1248 Posts
  • 187 Reply Likes
Ok I understand the need. At this time this is not possible in MindManager.

However, I could imagine that creating an in-between task called (provide sufficient information to start task2) could solve this. (similar to Nick Duffils suggestion)

And you would have the benefit of keeping track of this in the same way as all the other tasks.

At the time when Mindjet purchased the Cohuman cloud solution, now called Mindjet Tasks, that took those waiting for aspects into account.
We should find out if it still does that after the integration and introduction of the new name.
Photo of Martin van Schooten

Martin van Schooten

  • 6 Posts
  • 0 Reply Likes
An in-between task makes larger projects, with lots of "products", impossible to manage. That is why I still do use MS-Project. MindManager is excellent to make the Product Breakdown Structure and if it would enhance it's planning capabilities it would be the single needed tool for effective project management. ^_^

Photo of Joaco Gonzalez

Joaco Gonzalez

  • 2 Posts
  • 0 Reply Likes
I agree with all that you say.

I'm currently planning a project and, since in my organization they use MS Project, I have to make it readable and presentable in MS Project, but for me it's certainly better to do it in MindManager. The thing is, when I go back and forth between MM and Project, I lose information.

The first thing are the Callouts Info. I Realize that MS Project file doesnt save that data, but, could it be done by a byproduct file that stores all the Map Info? 

The other thing is, when I started correcting the mpp file in Project, it appeared everything as "This task has a Start No Earlier Than" Constraint, so, when I put Start as Early as Possible, all the Tasks that I intentionally delayed (in MM) to start like, for example, 3 weeks after a previous task with Start to Start Relationship, it got slacked down (the program thinks this is Slack Time!). But, It wasn't. I wanted to wait for 3 weeks. So I took Project and in the Predecessor Column I put 55SS + 3wk. 
This way, its not considered slack time, and the schedules are consistent. 
The problem is, when I import this file into MM, this data is not stored, so it's lost, and we are back to square one. If I move the task, instead of not moving into the offset time (the 3 weeks), it goes all the way to the 55SS.
I find this really frustrating, because if this worked, the integration would run really smoothly.

Sorry I took long, but maybe in this way gets discussed for addition, or resolved in some other way.

And the workaround.... it's a workaround. :)

Thanks
Photo of Alex Gooding

Alex Gooding, Champion

  • 842 Posts
  • 211 Reply Likes

While the following won't unfortunately provide a workaround, it helps in understanding how this issue arose in the first place.

Prior to version 9 of MindManager it was possible to define a task with a larger number of days between start and finish than the actual task duration. For example, you could give a task a duration of only one day but with the start and finish a week or two apart. While this probably isn't exactly what you describe it may have provided a workaround.

The problem was that until that point Gantt charting for MM maps was provided by a separate program which could be synced with MM - JCV Gantt. This couldn't show this arrangement; anything that was synced between MM and JCV had to have a duration that was equal to the amount of time between start and end date, and vice versa; however, any tasks that had this slack time arrangement in maps that were not synced with the JCV program were unaffected.

When JCV Gantt was integrated into MM itself the rule requiring a duration equal to the difference between start and finish times was also instituted for all MM tasks (much I understand to the chagrin of several add-in developers), so now there is no way of incorporating any slack time into a individual task.

(Edited)