Best practices for driving dates on tasks with Dependencies: bottom-up or top-down?

Given Wrike's quirks (failures?) when it comes to large-scale, true Project Management (ala MS Project or SmartSheet), what seems to work out better to drive dates (and views) of tasks...?

  1. Let the sub-tasks, which are in a dependency chain, have dates that determine the date for the parent task (and have a predecessor somewhere(?)) OR
  2. Set a start date on the parent task that drives all the dates under it?

I've imported a workplan from Smartsheet, with over 500 tasks, and i'm having to rebuild the relationships and date drivers. I'd hate to do that more than once!

My concerns are around how they appear in GANTT charts and other views, reports, etc. AND how easy it will be to copy this whole plan each year, with all the dates just smartly re-aligning to a new annual season when i do so.

https://help.wrike.com/hc/en-us/articles/210323585-Gantt-Chart-Timeline-Overview-

 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
1 comment
Avatar
Stephen

Hi Jamie, thanks for your post. I think getting into detail on this here might not be as effective. I've spoken to your Customer Success Manager, Matt, who has time scheduled with you next week and asked to look at this on your account and suggest the best approach.

Great to hear from you here, thanks for posting! 🙌

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Best practices for driving dates on tasks with Dependencies: bottom-up or top-down?
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post