Hi,
From a Programme and specifically Portfolio management perspective it is important to manage dependencies in a more detailed/structured way in Clarizen. It is also impossible to capture dependency specific information or related risk and issues to these. My suggestion is to treat dependencies more like a workitem that will allow more management and control as I said on portfolio and Programme Management level. Maybe have a seperate module for dependencies like risks or issues?
Good news, you can actually create custom fields and workflow on dependencies if you go to Configure >> All Links >> Dependency. You can even add a "reference to an object" field to link a dependency to any other object like a case. There are some limitations, but you should should be able to do most of what you described with current capabilities.
Please sign in to leave a comment.
Thanks Josh,
I see what you are saying but can't see/understand that working. Probably me being unexperienced in this area. Where and how could I create a view to list dependencies , use the standard & Custom custom Dependency fields or add the cases to it? I mean to the dependency itself, not the work items the dependency relate to.
First, create a few dependency custom fields such as "Dependency Risks" or "Dependency Columns." Next go to a project with dependencies and maximize the work plan. When you select a work item with dependencies, you will see information related to those dependencies on the right. Maximize that dependency panel and you can click the gear icon and add any of the custom fields that you just created to this dependency view. These custom fields apply to the dependency itself, not to the related work items or cases.