Skip to main content

What are the side effects of for a company applying scrum for the first time with it's own existing terminology?

Last post 12:01 pm March 3, 2015 by Ian Mitchell
1 reply
07:45 am March 3, 2015

for example : they use development manager terminology for scrum master
second example : They use product directory as product owner. etc.

My personal views:

1) It creates confusion with the scrum concepts.
2) Company might end up missing some useful feature or power of scrum.
....and many more.


There is similar question on open assessment. But, somehow I do not understand one situation where It says management may feel less anxious as one of the possible situation.

This is what i don't understood. Less anxious meaning less worries. My feeling is when company misunderstands scrum (specially when it is new to the organization), It leads to more worries.

Please help me understand if "less anxiety for management" is one of the possible situation or not.

p.s. I started preparing for scrum certification. Please correct me if i am wrong.


12:01 pm March 3, 2015

> Less anxious meaning less worries. My feeling is when company misunderstands
> scrum (specially when it is new to the organization), It leads to more worries.

That's right...it will *lead* to more worries. Management will eventually realize that the benefits they expected are not accruing, and they'll wonder why.

Using an existing terminology could make them feel less anxious to begin with, because it would imply continuity rather than change. Genuine change is needed, however, if an organization is to implement Scrum and obtain its associated benefits. Using Scrum's own terminology emphasises the fact that it involves a different way of working, and that change may neither be comfortable nor something that can be taken for granted.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.