If I have a story with multiple tasks for different users, is there a good process flow when a task is dependent on previous tasks to ensure subsequent assigned users are aware that they now have a task ready to be worked on?
Assume that all tasks are already assigned to appropriate users.
Basically when the developer finishes their coding and checks in, there is another task following it for a different user to do some additional work.
Looking for something where the 2nd user will simply not see their task until the dependent task is done.
My one thought is:
- A status for the 2nd TFS task that is "Not Ready" and a TODO query that excludes these.
- As a matter of process, if a developer completes a task, they should look at the story to see if there is a task following it, and if it is "Not Ready" change it to "New".
- Users will use the TODO query to review tasks they have to complete, and the task changing from "Not Ready" to "New" will cause it to show up in their query.
Can I rely on ordering of tasks to be consistent within a story? I.e. so it is clear when completing a task, which one is clearly "next" without setting specific dates. (We usually don't set dates to tasks, and plan by assigning to sprints.) I've never noticed if tasks have a consistent ordering within a story in the absence of any priorities, or if it is just a bucket with arbitrary ordering.
Any pitfalls to this?
Obviously the one thing not ideal is it depends on a human process as a matter of habit. I'm not extremely concerned about that, but certainly not ideal.
Open to ideas for other processes to accomplish the same.
I'd rather avoid custom scripting behaviors in TFS, and just stick with customization via configuration.
To clarify, this is TFS within Visual Studio Online.