Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Issues & Questi... > How should we handle Task...

How should we handle Task predecessors/prerequisites RSS Feed

Wednesday, August 20, 2014
We have seen that a task can have a start date and an end date and a relationship to a requirement.  Tasks can also be "Blocked".  What seems to be missing is some sense of what a task is blocked by, like a predecessor or a prerequisite.  

How do other people handle this within SpiraTeam?

Our sponsor wants us to plan out tasks through deployment and guesstimate an end date.  I don't see how I can do that in SpiraTeam due to the apparent inability to specify predecessors.  So, I either need to explain how SpiraTeam has been set up to do things differently or use a different project management tool for that kind of planning.  Any suggestions?  (The organization is still fairly new to Agile but I don't want to just say something about how things are done differently in Agile.  Executives still need some sense of dates so they can plan ahead.)
1 Replies
Jim R.Jim R.
re: Jon Freed on Wednesday, August 20, 2014
Monday, August 25, 2014
Hi Jon

We are actually adding the ability to specify task associations and the ability to specify the type of association (related-to, dependent-on, etc.) in v4.2 of SpiraTeam.

In terms of the overall question, with SpiraTeam (and agile in general) what you would do is lay out the Iterations in your release and then put the requirements and tasks into the iterations. That way you'll see how many iterations you'd need and therefore a projected end-date.

  • Started: 8/20/2014
  • Last Reply: 8/25/2014
  • Replies: 1
  • Views: 2912
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2017 | Licensed to Inflectra Corporation.