I would NOT create individual resources as that defeats the goal of having a generic resource team.

Each feature has 3 tasks that will be performed in a logical sequence, develop (implement), document, and test. Assuming the implementation is the starting element for each feature, create a plan with just that one task for all 35 features. Assign the team resource at 100% to all 35 implementation tasks (assuming only one member of the team is needed for each). The plan will show overallocation so apply leveling. That will re-distribute the workload and establish a start for each feature. Now, add the documentation and testing tasks to each of the implementation tasks using a finish-to-start dependency. That will insure that once a feature is started, it will be continued without interruption.

Hope this helps.

I would NOT create individual resources as that defeats the goal of having a generic resource team.

Each feature has 3 tasks that will be performed in a logical sequence, develop (implement), document, and test. Assuming the implementation is the starting element for each feature, create a plan with just that one task for all 35 features. Assign the team resource at 100% to all 35 implementation tasks (assuming only one member of the team is needed for each). The plan will show overallocation so apply leveling. If you do need/want to start some features before others, use the Priority field to establish a leveling order. Leveling will re-distribute the workload and establish a start for each feature. Now, add the documentation and testing tasks to each of the implementation tasks using a finish-to-start dependency. That will insure that once a feature is started, it will be continued without interruption.

Hope this helps.

I would NOT create individual resources as that defeats the goal of having a generic resource team.

Assume each feature has 3 tasks that will be performed in a logical sequence, develop (implement), document, and test. To facilitate planning, task groups are linked but features are not. In this example of 5 features (scalable as needed) task groups are linked and a team resource of 3 individuals (again scalable as needed) is created with a Max Unit value of 300%. That resource group is assigned to all tasks. With that basic structure, the resource team is overallocated (day by day) on all tasks.

Since it is undesirable to break a feature's task sequence once it is started each task in a feature's group is assigned a task priority, arbitrarily since completion of any feature is arbitrary relative to the other features. With a unique priority set for each task group the plan can be leveled using "priority,standard". The result is:

Hope this helps.

I would NOT create individual resources as that defeats the goal of having a generic resource team.

Each feature has 3 tasks that will be performed in a logical sequence, develop (implement), document, and test. Assuming the implementation is the starting element for each feature, create a plan with just that one task for all 35 features. Assign the team resource at 100% to all 35 implementation tasks (assuming only one member of the team is needed for each). The plan will show overallocation so apply leveling. That will re-distribute the workload and establish a start for each feature. Now, add the documentation and testing tasks to each of the implementation tasks using a finish-to-start dependency. That will insure that once a feature is started, it will be continued without interruption.

Hope this helps.