A new team requests a Jira project.

The requirements for the new Jira project include a central backlog, burndown chart, different QA processes for defect types, and the ability to share schemes with another project. Thecompany-managed Scrumproject type (Option B) best fulfills all these requirements due to its support for Scrum boards, burndown charts, flexible workflows, and shared configurations.

Explanation of the Correct Answer (Option B):

Manage and prioritize all work from a central backlog:

Company-managed Scrum projects include aScrum boardwith a central backlog where issues (e.g., Stories, Defects) can be managed and prioritized.

Exact Extract from Documentation:

Company-managed Scrum projects

Company-managed Scrum projects provide a Scrum board with a central backlog for managing andprioritizing work.

To access:

Go toProject > Backlog.

Prioritize issues by dragging and dropping.Note: The backlog supports all issue types in the project.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")

Track progress with a burndown chart:

Company-managed Scrum projects supportburndown chartsin sprint reports, which track progress based on Story Points or issue count during a sprint.

Exact Extract from Documentation:

Burndown charts in Scrum projects

Company-managed Scrum projects include burndown charts in sprint reports to track progress.

To view:

Go toProject > Reports > Burndown Chart.

Select the sprint to view progress.Note: Burndown charts require sprints and Story Points or issue counts.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")

Move pre-production defects and production defects through a different QA process:

Company-managed projects allow different issue types (e.g., Pre-production Defect, Production Defect) to use distinct workflows via aworkflow scheme. This enables separate QA processes (e.g., different statuses or transitions) for each defect type.

Exact Extract from Documentation:

Configure workflows in company-managed projects

A workflow scheme maps workflows to issue types. Different issue types (e.g., Pre-production Defect, Production Defect) can use different workflows to support unique processes.

To configure:

Go toSettings > Issues > Workflow schemes.

Assign workflows to issue types in the project’s scheme.Note: Company-managed projects support complex workflow configurations.(Source: Atlassian Support Documentation, "Configure workflow schemes")

Have the project share its schemes with another project in the future:

Company-managed projects use shared configurations (e.g., permission schemes, workflow schemes, issue type schemes) that can be reused by other projects. This allows the new project to share its schemes with another project in the future.

Exact Extract from Documentation:

Shared configurations in company-managed projects

Company-managed projects use schemes (e.g., workflow, permission, issue type) that can be shared across multiple projects.

To share:

Create a project with a shared configuration inSettings > Projects > Create project.

Select the same schemes for another project.Note: Team-managed projects have project-specific configurationsand cannot share schemes.(Source: Atlassian Support Documentation, "Create a project in Jira Cloud")

Why This Fits: Thecompany-managed Scrumproject type supports a central backlog, burndown charts, distinct workflows for defect types, and shared schemes, fully meeting all requirements.

Why Other Options Are Incorrect:

Company-managed Kanban (Option A):

While company-managed Kanban projects support a central backlog (Kanban board) and shared schemes, they do not natively provideburndown charts, which are specific to Scrum projects for tracking sprint progress. Additionally, while different workflows for defect types are possible, Kanban projects are less aligned with sprint-based tracking like burndown charts.

Extract from Documentation:

Company-managed Kanban projects use a Kanban board but do not include burndown charts, which are specific to Scrum sprints.

(Source: Atlassian Support Documentation, "Manage Kanban projects in Jira Cloud")

Team-managed Scrum (Option C):

Team-managed Scrum projects support a backlog, burndown charts, and simplified workflows. However, they do not support shared schemes, as configurations (e.g., workflows, permissions) are project-specific and cannot be reused by other projects. Additionally, team-managed projects have limited workflow flexibility, making it harder to define distinct QA processes for defect types.

Extract from Documentation:

Team-managed projects have project-specific configurations and cannot share schemes with other projects. Workflows are simplified and may not support complex processes for multiple issue types.

(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")

Team-managed Kanban (Option D):

Team-managed Kanban projects support a Kanban board but lackburndown charts, as they do not use sprints. They also have project-specific configurations, preventing scheme sharing, and limited workflow flexibility for distinct QA processes.

Extract from Documentation:

Team-managed Kanban projects do not support burndown charts or shared schemes. Workflows are project-specific and simplified.

(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")

Additional Notes:

Creating a company-managed Scrum project requiresJira administratorprivileges (Settings > Projects > Create project).

The project can be configured with aScrum board,workflow schemefor distinct defect workflows, and shared schemes for future projects.

Burndown charts require sprints and Story Points or issue counts to be configured.