We find that there are cross-team dependencies in our world. For these teams, they have separate backlogs (ie. projects), but have the need to be aware when team 1 working in a different backlog releases changes that are dependent on their work. So, analogous to the ability to assign upstream/downstream dependencies on stories, it would be cool if you could do this from a backlog item to a project (or release in your words - via the 'release planning -> release scheduling' menu). Likewise the ability to apply to epics as well such that backlog items created from the epic auto inherit the dependency possibily?
by: Andy K. | over a year ago | Sprint Planning
Comments
definity needed
this is not just a "cool" feature, but is critical. I actually have a team now that has, dare i say, started using MS Project, to do dependency management, since V1 does not support it at the Epic level.
And, that is just one team for now, but as we move more towards an APM model, this becomes even more important!
Yes - great idea. I wold love to use the dependencies, but if i have an epic with 10 user stories that is dependent on another epic with 10 more user stories, the only way to show the dependency is to set 10 dependent links (upstream and downstream) in each of the twenty stories, instead of just making one Epic dependent on another. Epic content (other epics and stories) can inherit attachments and links, so why not inheriting dependencies?
I agree!
Especially Epic to Epic dependencies!
I think the current implementation where you can report rollups of interdependencies of work items contained with epics is ok but it does not meet our needs fully. We may have Epics that are not broken down yet that are fully dependent on other Epics. Currently it looks like you would have to at a minimum create one backlog item under each of these epics and map those as dependencies in order to see this. This is a bit clunky IMHO.
We currently have an Epic to cover a Reports change, but this cannot be implemented until another Epic to cover Database changes is completed. There is currently no way to visualize or indicate this that I can find.
In my view, an Epic is an extension of a User Story or can represent a collection of User Stories towards a higher level of changes. To this end, the functionality granted to User Stories should be extended to Epics as well.
To realistically use VersionOne for any true portfolio item planning, this is definitely needed (along with the dependency reporting from the story tabs). I echo the above comment - there really is little (maybe nothing?) that exists at the story level that shouldn't be available at the epic / portfolio item level. It's truly a superset.
We are planning to release Epic to Epic dependencies.
This is mandatory need for basis Project Management. Can you fast track it please ?
Thank you all for your valuable input. I am happy to announce that Epic to Epic dependencies have been implemented.
Using the new Portfolio Item Dependency relationship, you can identify, capture, and manage dependencies as soon as they are identified without needing to create stories. These dependencies can be set at any level in the Portfolio Item hierarchy. Therefore, you can also create dependencies between Capabilities, Epics, Initiatives, or any level in the hierarchy. Once created, these dependencies can be viewed on the Portfolio Item Dependency Diagram and on the Portfolio Item Relationship Visualization Tab. There is also a new Portfolio Item Dependency report for those who like to see these dependencies in a tabular form.
Please check it out and keep the good ideas coming.