Flow, service activities and rework
Describe the work needed beyond the main activity.
Build the route
A Flow describes the activities needed to complete a task type, such as development, review and testing. Service activities are real work: they need an estimate and a suitable person. Check the sequence, requirements and mapping of source statuses before calculating.
Check the remaining work
Remaining work for the main activity is not a remaining estimate for the entire Flow. A completed main activity can still leave review or testing to do. Check service estimates separately. Where a manual service estimate is entered, it takes priority over its calculated estimate.
Rework is work too
If the chosen Flow uses rework loops, check their route and estimates. Do not add duplicate activities to imitate a loop that is already represented. The selected Flow rules determine which work is included. Review warnings about one person performing both the main and service work.
Related articles
- People, skills and availability
Tell the planner who can do the work and how much time is available.
- Review task data before calculating
Resolve missing work estimates and external deadlines; review other warnings.