Boards, Sprints and Task Planned Completion Date Change Questions

[CBuckwal]

One of our teams wants to use dynamic boards, which will always be connected to project tasks. If using boards, a team member can easily change the board task planned completion date, which could affect the project timeline as a whole. We were told that best practice to change project task timelines is to increase the task duration to match the new planned completion date, while keeping the original task planned completion start date, rather than changing the task planned completion date. Is there any way to add the task planned duration to the card to keep this best practice? I don’t see a way to add that field. How are other people handling moving task planned completion in boards?

Also, this team also wants to work in two week sprints, but not use iterations and stories, since they can’t pull in stories dynamically to that team area. They will want to frequently move the task planned completion dates to the next two week sprint. This will affect new and in progress tasks. The team used to use a custom field tag to manually mark the task sprint in another system. I don’t see this as feasible for the team in Workfront, since there will be many more tasks to manage and this can be viewed in Workload Balancer using sprint date filters. Also, the task completion date needs to match up to the sprint date, not just have the card tagged with a certain sprint number. How are other people handing sprints and moving tasks within sprints?

Thanks for any insights on this!

[RowvillBh1 · Accepted solution]

No way to add duration. I think Planned completion date is your best bet to change the duration. You can possibly create a calculated field that mimics the duration column and pull that into your card, this can help see what impact does the change in date have to the duration. For Sprints, we have set ourselves up as an Agile team and we are using iteration to create two week sprints. We are then enforcing the tasks to follow sprint dates as their start and end dates. We are also planning to use "Commit date" to mark the expected completion of each task within the sprint.