Examples

1st example is the Budget Office's timeline. They have:

• monthly tasks that need to happen each month
• an annual timeline of tasks that need to happen at certain times of the year, e.g., Board materials need to be prepared quarterly, a government report is due at a certain of the year, etc.
• the actual budget creation timeline

In order to see how the different steps in each of the three timelines effect steps in one of the other timelines, the Budget Office created a "Stacked" Template (and project)

2nd example is a Software Implementation project. There are steps that need to be done by:

• IT
• the department getting the new software
• the vendor

Steps for all three areas happen often simultaneously and are dependent on each other. So that it does not become confusing, IT, the Department, and the Vendor each get their own layer. Then these three layers are stacked into one project. This allows to create dependencies between steps done by IT vs. the Department, etc. It also allows to see the overall progress of the project. Last but not least, as you work on 'your' steps, you can just look at the layer that concerns you and your view is not cluttered by what the other 2 areas need to do