Tasklists

Tasklists can be used to gather tasks into logical groups for ease of prioritization and filtering.  They are also a logical level at which to assign a promise date to drive risk alerts.  Tasklists can be nested to give you deeper groupings as necessary. 

When you create a new project in LiquidPlanner, a corresponding tasklist is created for you by default.  You'll want to build an expanded task list structure that reflects the way you manage your work over time. 

There is no one tasklist structure that is best for everyone. Some teams like to have tasklists for each phase of a project, while others prefer to have a tasklist for each month.  Software development teams often create tasklists for each sprint, or release, of their product.

If you execute projects concurrently, be sure to read our post on multi-project scheduling.  You'll see an example of a flexible tasklist structure that allows you to interleave tasks from different projects within the same tasklists. 

Phase-based tasklists for a marketing project

 Sprint-based tasklists for an agile development project