What is a project?

A project has a short key and a name. Work item keys start with that key. Membership is the gate: people outside the project do not read its backlog, documents, or reports.

• Backlog and board hold the work.
• Sprints, reviews, roadmap, and releases hold the plan.
• Documents hold project pages.
• Members holds who is on the team and which project roles they have.
• Reports holds delivery charts. Workload appears for Product Owners and Scrum Masters.

Projects are provisioned from an approved intake. Approval names the project and nominates the first Product Owner and Scrum Master. The same person may hold both; keeping the roles separate is recommended. Developers and specialty labels are added later on Members.

A Product Owner can add up to eight tags on a project, such as POC or Product Development. Tags are labels for that project. They do not change who can open it, how the board works, or sprint rules. Other members can see the tags and cannot change them.

A Platform Administrator can set the project methodology to Scrum, Kanban, or hybrid, and can require a sprint before work starts. Those settings live on the board. Everyone else uses the resulting board views.