Task Planner - Looking for "Best Practice"
In a coming construction project we are playing around with the idea of using Tasks in order to keep the number of activities low and easier to manage.
Something that we are thinking about is having QA/QC checks as a task instead of activity for example. Or having 1 activity per discipline and having the install steps as Tasks.
But before we get too far we want to get some advice and best practice.
Ex.
- How many tasks per activity is reasonable.
- Should we avoid having multiple discipline tasks per activitt?
- How much logic between activities should come from Tasks? If at all?
0