Loading Profile...
We have a need to be able to "pause" a project.
The way we work means that we sometimes do not start the project directly after we write the stories for the project (although we may start some chores like setting up environments etc) hence our velocity calculations take longer to be accurate due to the time period between when we do setup work and actual stories. Additionally, We sometimes have clients who come back to us for a second round of work after some break during that break our velocity numbers drop significantly because no work is happening. It would be nice to have our velocity calculated based on the last actual 3 weeks of work. Lastly having a 'pause' on a project would then allow us to look at the state of the project when it ended (work last stopped) including the backlog, the current lane, and the accurate velocity.
65
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
The best points from the company
-
We've added a couple of features that help with projects where activity fluctuates. It's possible to override the length of a given iteration (in # of weeks), so combined with a team strength of 0, you can essentially put a project on hold for as long as you'd like. Also, you can now set an explicit project start date, for projects that are planned to start in the future.
3 people think
this is one of the best points
-
Hi Desi...we agree that Tracker's velocity calculation doesn't handle situations like resuming work on a project, or 0 point iterations early in the project very well. We're going to do some brainstorming in our next release planning session about possible solutions, and will definitely consider the project pausing idea. Thanks for suggesting it!
3 people think
this is one of the best points
-
-
-
Inappropriate?Hi Desi...we agree that Tracker's velocity calculation doesn't handle situations like resuming work on a project, or 0 point iterations early in the project very well. We're going to do some brainstorming in our next release planning session about possible solutions, and will definitely consider the project pausing idea. Thanks for suggesting it!
3 people think
this is one of the best points
2 Comments Add a comment
This is one of the best points
-
Thanks for the reply. Did you guys come up with a plan to address this going forward? -
Hi there, Is there any news about the decision regarding this feature? I'm interested it gets implemented too :)
-
Inappropriate?I've just signed up specifically to add my vote to this one. The lack of this feature means we often have to override our velocity ...
One clean way to implement this might be to allow the optional setting of a 'start no earlier than' date for each iteration? -
Inappropriate?I'm considering using Tracker on my team's next release and this would be a great addition. The product we're working on will get attention for a while during this release, then sit for a bit while the team is focused on something else. It would be great to "pause" the whole project to communicate clearly that no work is currently being done on this project.
I’m agreeing
-
Inappropriate?We work intensively on internal projects whenever we have spare developer time. But we often pause them when client's need those developers. This really messes up the velocity statistics.
I’m pleased others are interested
-
Inappropriate?I think that having a start date option would be very useful. The system currently assumes that as soon as you start adding stories you're actively working on a project. We use this tool to estimate project duration in the initial stage of a project, usually before we actually start working on it. It is useful to use the initial velocity and iteration length tools for a project to get an idea about roughly how long a project will take. However, the dates that show up for each iteration are inaccurate if the project isn't already started. This is confusing to us, and especially confusing when going over project story and timeline details with a client.
I’m hopeful this will be added
-
Inappropriate?During a project's lifetime we may have a little break for a week or two where no work is done. It would be nice to be able to pause a project rather than having empty iterations and adjusting the team strength to 0%.
I’m hopeful this feature will be implemented
1 person thinks
this is one of the best points
-
Inappropriate?We are developing an app in five iteration releases, where we plan for 1 week and develop for 4. When we stop to plan, our velocity is reduced considerably. A pause feature would allow us to have a better estimate for completing a release once we get back on the horse. Otherwise, we have to wait three iterations to see our velocity normalize and get a usable estimate.
Although Schlick's 0% team strength for the planning iteration seems to be adequate.
I’m hoping this feature will be implemented... soon.
-
Inappropriate?We've added a couple of features that help with projects where activity fluctuates. It's possible to override the length of a given iteration (in # of weeks), so combined with a team strength of 0, you can essentially put a project on hold for as long as you'd like. Also, you can now set an explicit project start date, for projects that are planned to start in the future.
3 people think
this is one of the best points
-
Inappropriate?Please, please add a pause feature. If you can, make it available from the dashboard so I could get to it without having to drill down into a project :)
Right now we're considering trying to build our own pause/unpause by setting team strength to 0 via the api.
I’m frustrated
-
Inappropriate?Hey guys, any news about that? The metrics of my project were so beautiful, now that I will have to pause it for a while, I think that will mess up my metrics. =(
I’m anxious
-
Inappropriate?Hi Hugo...is overriding the length of the current iteration, and adjusting it's team strengh to 0% not working for you? We'd love to add the ability to pause a project, but I can't promise when we might get the bandwidth to do so.1 Comment Add a comment
This is one of the best points
-
Thanks Danp, I'm trying that now, I'll see if that will work as I expect.
-
Inappropriate?If you set team strength to 0% for a few weeks what will happen to the average velocity? Will those weeks be disregarded from the calculation?
-
Inappropriate?Effectively, it should, but what I would do is take the iteration in which the project "paused", change it's length to something long (eg 52 weeks), and set it's team strength to 0%. That should make it the current iteration, excluding it from velocity calculation.
-
Inappropriate?I see there is the option to put the team strength at 0 for the same effect, but what happens if the team is going on vacation for a different length of time than the iteration length?
It would be nice to be able to pause a project entirely and pick up at a later date that would signify the beginning of the next iteration.
This reply was created from a merged topic originally titled
Can we pause a project?.
I’m confused
EMPLOYEE
