Help Guide > Planning and Scheduling > Multi-Project Scheduling
Multi-Project Scheduling
Many teams don't have the luxury of focusing on only one project at a time. If your team is juggling multiple projects, you probably work a task from Project A, then a task from Project C, then back to Project A, etc. In LiquidPlanner, the key to easily modeling concurrent projects is creating packages that align with your project methodology.
Tasks from different projects can be co-mingled in shared packages to reflect the order in which the work will be done. If you need to see a precise long-term forecast for all of the work in all projects, you might package all tasks from all projects right up front. If you only focus on near-term scheduling, you might leave some tasks unpackaged until you are ready to pull them into your near-term focus.
There's no single package structure that is best for every team. Agile development teams might create packages to represent their sprints, while calendar focused teams might go with quarterly, monthly or even weekly packages. You want to go with a structure that most naturally meshes with the way you manage your work over time.
Some packages can be useful for all teams, regardless of the primary package structure you use: ASAP, Events, Ongoing Tasks, Backlog, etc.
Sample Package Structures
A picture is worth a thousand words, so be sure to look at our white paper Using Packages for Cross-Project Prioritization. You'll see some common package structures and how they are used to model concurrent projects. One of those sample structures might resonate for you, or they might spark a vision of a different structure that would be just the right fit for your team.
