Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Have other members of PMI discovered that in project teams , you come across team members that tend to be stuck up on terminology , especially if there are different approaches to completing the project?
For example, if they are used to "Sprints", either because they have learnt it on a course or used it on projects as opposed to "Iterations", they make it a point to tell you or give the impression that they are not willing to adapt.
They wan't to see "Done" on the Kanban board instead of "Complete".
They cannot fathom "In progress" being divided into Development and Testing or cannot see Development and Testing to be combined into "in Progress"
I would have thought you can tailor the use of these terms on different types of projects where you expect "Rapid Delivery" and I certainly don't have an issue adapting myself.
And sometimes the argument is "The software tool (e.g. JIRA) defines it this way, so it HAS to be this way..."
Why wouldn't team members simply concentrate on the end product and be willing to tailor the "means" to getting there? Saving Changes...
Sort By:
Tove TronslienSenior Project Manager| Digital EchidnaLondon, Ontario, Canada
Hi Deepesh,
Indeed I have met those people. I work with mostly programmers, and having been one I know how my brain can become very "adhering to rules" - after all programming is very structured and rules based.
I also find that some individuals with certain, shall I say, personally traits, just don't have the ability to "think outside the box." They may have strong skills in one area (technical) but less strong in others (adaptive or people skills.)
In most instances the terminology definitions has been quickly resolved with a brief discussion, usually ending up writing down somewhere the new definition of the word.
Honestly, I pick my battles and there is no use for me to be just as stuck and there is no defeat to have the kanban board say Done instead of Complete. The only thing I ask let's just be consistent and all have the same understanding of what it means when we work with multiple projects/boards.
...
1 reply by Anton Oosthuizen
Jan 17, 2019 11:56 PM
Anton Oosthuizen
...
"The only thing I ask let's just be consistent and all have the same understanding of what it means when we work with multiple projects/boards."
And the crowd erupts!!!!!!
Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Thanks Tove :)
Yes your last few words offer the suggestion that I generally use. To use consistent terms wherever we use it on the project Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Don't get me started on this. I'm so over 'purists' who believe that terminology is more important than getting the job done. I can quote at least 100 post responses on this forum that are dedicated to pointing out that somebody referred [wrongly] to something as a method, methodology, framework etc. but do not answer the question asked. GET THE #@$#$ JOB DONE. DELIVER ON THE OBJECTIVE. Call it what you want I could not give a @#$@#. If we are all on the same page it does not matter, what matters is a common reference. If I call an apple an orange but you know what I am talking about, get on with it. If you are unsure THEN question the use of terminology.
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Jan 17, 2019 9:27 PM
Replying to Tove Tronslien
...
Hi Deepesh,
Indeed I have met those people. I work with mostly programmers, and having been one I know how my brain can become very "adhering to rules" - after all programming is very structured and rules based.
I also find that some individuals with certain, shall I say, personally traits, just don't have the ability to "think outside the box." They may have strong skills in one area (technical) but less strong in others (adaptive or people skills.)
In most instances the terminology definitions has been quickly resolved with a brief discussion, usually ending up writing down somewhere the new definition of the word.
Honestly, I pick my battles and there is no use for me to be just as stuck and there is no defeat to have the kanban board say Done instead of Complete. The only thing I ask let's just be consistent and all have the same understanding of what it means when we work with multiple projects/boards.
"The only thing I ask let's just be consistent and all have the same understanding of what it means when we work with multiple projects/boards."
And the crowd erupts!!!!!! Saving Changes...
Amit SharmaProject Manager| IT MajorDelhi, Delhi, India
Remind them of acceptance and of course, something called a "Thesaurus" Saving Changes...
There is some benefit in adopting standard terminology, especially when introducing a new way of working. So if we try to stick with the same terminology we used before, there will be less recognition of the fact that we are, in fact, trying to change how we work.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The worst thing a project manager must do is not creating a glossary of terms at the very begining of the project. In fact, the glossary of terms must be started by the business analyst before the project exists as a critical solution component. Unfortunatelly, this activity is mostly forgotten and that impacts in project delays, Saving Changes...
Working in a cross-functional projects there is a need to clarify at the beginning of the project "What does it mean for you Done"? And work with all the team members to build a glossary together. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Definitely agree that teams, or progress, should not be held up, or back, by the little things. As Anton said, if I know what they mean, then I'll let it be. The only time I would bring anything up, is to ensure we are on the same page.
There is also a professional way of going about things. And the above suggestions to work inside the team to have aligned definitions is good feedback.
There are certainly more important things in life and battles indeed should be picked. Saving Changes...
Greg GithensAuthor, "How to Think Strategically." Executive & Leadership Coach| Catalyst & Cadre LLCLakewood Ranch, Fl, United States
Nuance is important, especially when the project has an external face.
I'd encourage people to listen closely to others and their word preferences. Often, we can learn some very important lessons from considering their semantic distinctions. Saving Changes...
