Stories Dependency Management in TargetProcess

Howto Add comments
May 242009

Dependencies inside a single agile project and single agile development team are easy to manage informally without any tool, thus there is no explicit dependencies management in TargetProcess.

However, sometimes you have complex program with several projects and several development teams. Obviously, it is hard to avoid that all teams will work independently. In some cases a user story from project Alpha will depend on a user story from project Omega. How you may handle that in TargetProcess?

Luckily, there is a powerful Custom Fields concept to serve your needs. For example, you may create “Depends On” custom field for user story and select a user story from the project Omega to show the dependency explicitly.

See how you may setup dependencies management in TargetProcess in 3 minutes (screen cast)

Posted by Michael Dubakov at 10:06 pm
  • Anonymous
    That is quite handy, but what I really want is to be able to have an impediment that depends on, say, another request (different project) and when that request is completed, it automatically marks the impediment as resolved.
  • In fact you may implement a plugin that will do that. You may add custom field to Impediment and associate it with request A. The impediment itself related to User Story Y for example. On request A state change you may switch related impediment into final state (thus closing it). (It will be required to check custom fields via API, but it is doable task).
blog comments powered by Disqus
© 2012 TargetProcess Product Blog Suffusion theme by Sayontan Sinha