Adjusting planned dates in an iteration

[#1]

When a task is in an iteration it assumes the planned completion date is the end of the iteration. When we have a month long iteration we frequently have tasks that will be completed at different points through out the iteration. We would like to be able to modify that start and end dates as long as it is within the iteration dates.

[#2]

This would be very helpful for us as well since we have teams who want to work as Agile teams but the tasks they will be assigned are part of larger waterfall-style projects -- when the team tries to add tasks to an iteration, the waterfall project dates get overwritten.

[#3]

We have seen the same as Barbara. Mixing Agile Teams with Waterfall projects is very problematic. Any Waterfall task assigned to a sprint can have very nasty date consequence on a waterfall project.

[#4]

Same case for us. We have teams working on Agile and when project tasks are assigned to these team are added to iteration, the project schedule gets screwed up. Something has to be done to address this if Workfront is promoting that you can mix agile and waterfall in their system.

[#5]

I agree with the sentiment and have upvoted this.

But I think the problem is with mixing agile and traditional methodologies, not with the WF implementation. How WF is currently working is technically correct from a process point of view.

[#6]

If the waterfall project views are still important, then WF should be configurable to override the planned completion date or not. Choosing one approach obviously doesn't work for everyone.

[#7]

Not only does it set the planned completion date, but it does so without any consideration to predecessors. Even on an agile team you may be a dependency within an iteration where one user story must complete before starting on the next. Being able to reset the planned dates will allow the team to account for that.

[#8]

This is applicable for some of the work that comes in to one of our Agile teams - most work is fine to be assigned the S/F dates of the sprint, but there are a few items that have a specific due date at some point mid-sprint. We end up adding the actual due date in the title of the task, which is a fine workaround, but it can cause confusion at times.

[#9]

I'm in the same boat. In fact, I'd say the date issue is one of the biggest factors in moving to Agile Marketing Management. Tasks have due dates that are dictated by things entirely outside of the iteration time boxing, like editorial calendars, print dates, and intersections with product launches and other promotions. Forcing all the tasks/issues to have the same end date as the iteration screws all of this up.

[#10]

I have been a SM, PO, and a PM at this point in my career. while I did my time in the SM/PO world, it was a common complaint that my PMs were unable to adjust dates within the iteration, in addition to this, the dates of the iteration also adjust the dates within the project. I would like to see this! Upvoted!

[#11]

We have same requirement, it will ease in many ways.