[Status: Not planned] Project/Folder Dependencies

Hello,

Something that I would be useful would be the ability to assign project/folder dependencies. Example:

Project: SQL Server Update

Folder: Reporting Rework (Depends upon completion of entire SQL Server Update project)

Task: Create XYZ report (Depends upon completion of SQL Server Update as a whole)

I hope that makes sense, basically just taking Dependencies and expanding them so they can be on projects/folder and also so that an assigned dependency can point to a Project/Folder.

Regards,

  Colby

Upvote 155
73 comments
Spot On Innovative Approach Stellar Advice
Avatar

Yes please! This would be such a great feature!

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This feature will help our team be better organized. The ability to add project dependencies is greatly needed. I upvoted in May of 2018 and commented then. The need remains. Please consider putting in front of your product development team for consideration. 

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Carole Charrade, Denise Miller, thank you both for adding your support for this suggestion 🙌🏼

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This came up in a meeting today - it's a feature that really would solve a lot of our operational and reporting needs.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Leann Lewis, thank you for sharing your feedback here, it's been passed on to our Product team 👍🏼

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you Cansu! Would it help for me to provide some clear examples of what we are hoping to accomplish? We currently do this "project dependency mapping" separately in LucidCharts.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Leann Lewis, of course, please do share your use case(s) here. All use cases shared help understanding the need, and popularity of a suggestion even though this is currently not planned by our Product team. 

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Cansu Up-vote for this feature! We run all of our projects through Wrike and having the ability to roadmap/plan with project dependences would add so much value to Wrike's reporting capabilities.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Ashley Anderson, welcome to the Community! 🤗
Thanks a lot for supporting this idea! I'm passing your feedback to our Product team  Please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions! 
If you'd like to know what this Community has to offer, please check out our New to Community forum 👋

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Add another vote for this feature from me, please. This is a feature I have missed since converting my plans from MS Project to Wrike. The workaround of linking to tasks within a project is cumbersome and makes for less readable plans.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hello Chris Broshears, thank you for adding your support here, and welcome to the Community! 

I've passed on your feedback to our team, and if there are any updates in relation to this request, we'll be sure to share them here.

In the meanwhile, if you'd like to discover our Community, please check out our New to Community forum 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Cansu here are two primary use cases for us:

1) Often times large implementation are broken into projects executed by different teams. So, for example, for the build of a new software or technical project there is a requirements gathering phase, stakeholder meetings, etc (often handled by project management, SMEs and stakeholders). From there the technical build phase consists of technical planning and project build. Beyond that there is rollout planning, training, support planning and support team hand off. Often, each phase is effectively a sub project and the start of one phase is impacted by the end date of the priot phase. For purposes of dev work, for example, a FULL project implementaiton may take a year, but the dev buil phase may consist of 3 - 6 month of that time so the ability to set a "project end date" for the technical portion alone for tracking purposes would be ideal. Right now we sort of handle this with projects within projects - but there is alot of manual maintenance of dates, no way to chart project dependencies, etc.

2) This use case is more complex and doesn't have as clean a work around. We often have full scale implementations that must be complete before the first phase of a future project can even be started. For example - in order to do a certain series of automated sales reports we have to complete two products: one that tracks revenue data granularly by specific metrics (we have this done), and another that integrates with our HRIS and maintains an org chart in a database (this one is in progress). As it stands, completion of those two prjects are pre-requisites for 4 - 6 other projects that measure operational performance regionally, sales driver performance and a number of other metrics. Those projects are all for separate business divisions with unique requirements - but they have overlapping pre-requisite infrastructure. Currently we map all of these global dependencies in LucidCharts to make sure that we are effectively prioritizing projects and identifying/measuring the long term impact of shifting project timelines.

I could also see this being useful for cross functional teams within technical developement, where an infrastructure team may have to set up servers and network infrastructure before a dev team can start to build out a product.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I also wanted to mention that I did take a look at the workarounds suggested. In order to do that effectively we would have to build out timelines for all future pojrects. We have an incoming docket of over 200 projects. We can identify project dependencies but going in and creating full scope plans for all of those when we may not not be starting on them for a year seems like a waste of time. Especially considering the fact that sometimes projects become moot or irrelevant in the face of business or technology changes. We need the project dates to move and to be able to RoadMap across a series of inter-dependant projects without necessarily having the entire scope for every single piece planned out.

0
Comment actions Permalink

Folllowing List for Post: [Status: Not planned] Project/Folder Dependencies
[this list is visible for admins and agents only]

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