Works on requirements are distributed by assigning the requirements or tasks to assignees (or owners). If you need to involve several project participants to implement a requirement, create the corresponding tasks. In this case, tasks can be implemented sequentially or concurrently. Usually team defines the order of task implementation independently, and participants can select tasks for themselves independently or by agreement.
Binding requirements and tasks to stages in the project plan, e.g., iterations or stages, allows to plan task implementation by time, and form a detailed planning schedule of project implementation. Software development focuses on delivery of the result valuable for user. Therefore, we must plan not separate tasks, but a requirement suite, implementation of which can bring tangible benefits. Each project stage has small duration, which allows to deliver value to user iteratively.
Planned requirements and tasks have the corresponding workloads estimation. Project participants have planned loading. Based on these attributes, we can estimate team possibilities regarding implementation of the requirement suite within the certain project stage, e.g., the upcoming sprint. Use "Iteration planning” (or "Operational plan") module to form a planning schedule of project implementation.
General structure of work decomposition is displayed in "Work tree” module. An additional panel for releases and iterations on the right displays a detailed Gantt chart of the selected project stage implementation.
System automatically aligns tasks on the schedule chart based on the target dates (start of iteration), special requirements to the start date ("Start by" field), the task priority and order number, finish date of the previous task, and the rule that employees implement project tasks sequentially.