Modeling large programs of work with goals and projects

Projects, topics, and goals are designed primarily for team-level work units. However, there are various ways to leverage these features to enhance communication and connection between teams and stakeholders for larger work items. This guide outlines some best practices for program-level reporting.

There are two levels of reporting granularity in your Atlassian Home and these elements can be interconnected with teams and people working on the projects.

• Projects: Reported on a weekly basis

• Goals: Reported on a monthly basis

Modeling a program as a project

First create an Atlas project to represent the program. Then link related projects and mark them as dependent, or group them with a common tag. This allows stakeholders to follow either a single project for summaries or a tag for detailed updates. You can also link multiple teams together working on the same program to the project.

This model is useful if you want to provide frequent updates (as frequent as weekly) and when you want to view all the teams working on the program. However you must make sure that all sub-stream owners share their updates before you create the program-level update so that you can have all necessary information.

Modeling a program as a goal

First create an Atlas goal to represent the program. Then link related projects under this goal. Goals can also be grouped with tags and can include sub-goals.

This model is useful if you want to provide less frequent updates, maybe as often as monthly, and if you'd like to model sub-programs. You can use sub-goals to reflect this. However, goals can only have a single owner, and teams cannot be the owner of a goal.