M
Mandi Bishop
I'm working on the Project templates for a set of processes which *may* have
some iterative components.
For example, I submit an application to an agency. That agency may request
additional information, which adds an additional 30 days to my schedule. If
they accept the application and pass it on to the final regulating authority,
THEY may request additional information - adding another 30 days to my
schedule.
Is there a way to account for an optional, iterative task, without adding
several individual RAI tasks along each step of the process? If an RAI is
issued, it is mandatory and will become a dependency for other tasks; if it
is not, other tasks will continue on schedule.
Ideas on simplification welcome!
some iterative components.
For example, I submit an application to an agency. That agency may request
additional information, which adds an additional 30 days to my schedule. If
they accept the application and pass it on to the final regulating authority,
THEY may request additional information - adding another 30 days to my
schedule.
Is there a way to account for an optional, iterative task, without adding
several individual RAI tasks along each step of the process? If an RAI is
issued, it is mandatory and will become a dependency for other tasks; if it
is not, other tasks will continue on schedule.
Ideas on simplification welcome!