How to change the << Projects >> terminology ?

[Deleted user]

Dear Atlassian Community,

I come before you today in ask for your wisdom.

We planning to convert our company to Agile methodology. It won’t be easy. But with great challenge comes great rewards? Anyway, as we try to keep things super simple, we are stuck on a terminology point.

Indeed, we are going to create  << Projects >> for every Services, to be as close as possible to our organizational chart.

So here is my question : How can I change the << Projects >> terminology to << Services >> ?

Our people will be lost otherwise, you know, the challenges of the digital transition….

Cheers

[John Funk · Accepted solution]

Hi Arthur  - Welcome to the Atlassian Community!

No, that is not possible and you should not try to do that. 

In our organization, the project is really more a Team and not a true project, as it will never really end for the most part. So, it's just an education on our part that when you see Project, think of a Team. 

[Jack Brickey · Accepted solution]

It is not possible to change any of these system level names. 

[Jack Brickey]

further I would think that you really would not want to do that. The reason is I’m confident that in time you are going to create other projects that are not associated to your current “services “. So if you were able to change it to services then six months from now or whenever you’re creating a new project and it’s called a service and it has nothing to do with services. 

[Nic Brough -Adaptavist-]

I've seen something like this done on server - it's not a huge job technically, but it does turn out to be a vast waste of time.

Because the new word for "project" is often nonsensical for many other areas and teams using Jira, and people (especially those who have used Jira before) suddenly need training on terminology, you'll be building a load of training and education debt instantly, plus erecting barriers to communication by imposing different terminology on groups of people who simply won't use it.  You'll find most of your people will call Jira projects "Projects", no matter how you re-word it, just so they can be clear on what they're really talking about.

[Deleted user]

Thank you guys for your insights.

I used to have big backlogs with only user stories. No Epic, or overclass "Projects", whence my confusion. At first I thought to follow the terminology and create a project for every project (1:1) but we would end with too much. And end up with the idea of 'context' from GTD.

I will follow your recomandations.

Much appreciated