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?.
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
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!
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).
@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.