Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira and traditional project methodologies

Hello. When the company is starting in the use of agile methodologies and Jira,  is a good practice to include the  projects in execution with traditional methodologies  in Jira?.


@Jose_Vendries -

Welcome to the community.  It will be depended on your customers willingness to convert the traditional PM ways to adopt to Agile.

You need to focus on the "CHANGE" process at your end.  I would recommend to showcase on teams who have transformed their processes into Agile via Jira (showing to your communities with the benefits of using Agile).

Hope this helps... Remember "Changes" may not always be easily implemented/accepted.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Like Nic Brough -Adaptavist- likes this

I'd argue for bringing the non-agile projects into Jira, just so people are working in the same place, it makes collaboration and reporting easier if nothing else.

Even if your "traditional" projects don't want to go Agile, they'll still be using the same data, a common language, have the same set of people to talk to on hand, and can cross link between projects.  And I've seen projects drift to be more Agile just because they've moved into Jira and seen how Jira does things.

But, whatever you do, remember it's about your people - always start with the people and what they're doing and what they want to do!

@Nic Brough -Adaptavist- -

I agreed with your statement too.  Especially - remember it's about your people - always start with the people and what they're doing and what they want to do!

Best, Joseph

Like Nic Brough -Adaptavist- likes this

People are in the center of projects. thanks.

@Jose_Vendries , what do you see yourself as benefits and downsides of doing it?

Thanks. Pros: All projects in one place, users Will get used to the tools and way of Work. Cons: Two kind of configurations (Flow and documents).

Thanks again.

@Jose_Vendries  , you should determine first what is suitable for your business then search for the tools to apply that.

Thanks. You  are right, tools after way of work is defined.


Log in or Sign up to comment

Atlassian Community Events