Scribd
Upload
18 views11 pages

Jira Workflow

The document outlines the use of Jira for different departments, emphasizing that each team should operate under separate projects with customizable workflows and fields. It discusses task structuring, cross-team collaboration, and reporting needs, while clarifying that a Jira project does not equate to a real-life project. Additionally, it compares Kanban and Scrum methodologies for task management.

Uploaded by

Prabhat Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
18 views11 pages

Jira Workflow

The document outlines the use of Jira for different departments, emphasizing that each team should operate under separate projects with customizable workflows and fields. It discusses task structuring, cross-team collaboration, and reporting needs, while clarifying that a Jira project does not equate to a real-life project. Additionally, it compares Kanban and Scrum methodologies for task management.

Uploaded by

Prabhat Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Jira Workflow

17 January, 2025
Agenda

1. How should different departments use jira and collaborate


a. Each team should use a different project
b. Projects can have their own workflow
c. Projects can have custom fields
d. Kanban Vs. Scrum
2. Task structure
3. Linking items across projects (teams)
a. Management wants to drive a new initiative which will have a product change
b. How
c. I am onboarding a new customer. How do i track the operational tasks
d. Customer has reported a new enhancement request during the onboarding process. How should i relay it to the
required team
4. Reporting
a. I want a progress view of the major initiatives (status, timelines)
How not to use it

Project in jira is NOT synonymous with a real life dev/design/customer onboarding


project
Ideal Project Structure
Team Project Code

Product Product PD
Mgmt. Management

Design Team Design FET

Engineering Engineering EXE


Team

Customer Customer CS
Service Service
Team

.. ..

Project should be created for a team


Kanban Vs. Scrum
Workflow
Task Structure
Task Structure
Cross team Collaboration (Working session)
Reporting: Roadmap
Reporting: Dashboard

You might also like