Forum Discussion
Solved
Managing Agile Project With Project- How To Handle Sub-Tasks When They Don't Finish and Need Moved?
I'm trying to use Project to manage an agile project, and where I'm running into problems is if I have a story which is an auto scheduled sub-task and the Iteration/Sprint is a fixed duration manuall...
- John,
Keep in mind that summary lines are NOT tasks, they are simply a summary of the performance (subtasks) under them. If you move a performance task that started on 6/8/22 under a summary line that previously showed a start of 6/22/22, that summary line is going to re-set its start date to 6/8/22 because it is "summarizing" the new subtask start.
Summary lines do NOT "actually" start or finish, they just parrot the subtasks which do have actual starts and finishes. So, there is no "false" reporting, Project is performing the way it was designed.
John
John,
Keep in mind that summary lines are NOT tasks, they are simply a summary of the performance (subtasks) under them. If you move a performance task that started on 6/8/22 under a summary line that previously showed a start of 6/22/22, that summary line is going to re-set its start date to 6/8/22 because it is "summarizing" the new subtask start.
Summary lines do NOT "actually" start or finish, they just parrot the subtasks which do have actual starts and finishes. So, there is no "false" reporting, Project is performing the way it was designed.
John
Keep in mind that summary lines are NOT tasks, they are simply a summary of the performance (subtasks) under them. If you move a performance task that started on 6/8/22 under a summary line that previously showed a start of 6/22/22, that summary line is going to re-set its start date to 6/8/22 because it is "summarizing" the new subtask start.
Summary lines do NOT "actually" start or finish, they just parrot the subtasks which do have actual starts and finishes. So, there is no "false" reporting, Project is performing the way it was designed.
John