Please login or join to subscribe to this thread
Not everyone uses the terminology precisely. A method is a specific tool. A methodology is the rational to choose a specific method. A framework is a basic structure.
In my career as a SME of various things I have often mediated conflicts where two people are saying the same thing, but one or both is using incorrect terminology.
As stated in the 'Comprehensive List of Agile Frameworks' article by Mr. Render, …"Agile is not a framework or a methodology on its own, it is more of a philosophical approach to how things should be done." Agile has a set of values and principles in project management.
Evolving from that has been a plethora of processes or disciplines over time with their own specific rules and terms … such as Scrum, Lean, xP, SAFe, and on and on.
Whether it is 'methodology', 'framework', 'processes' or something else, they're all disciplines under the umbrella of Agile as a counter to TPM.
There is no controversy. The only thing people have to do is going to the basement which are before the movement on software domain Definition of agile and agility is there. Agile is not a method, not a process, not a life cycle, not related to IT. Just if you are talking about method then which are them is inside of the name and the definition. For example I can say you the first use of word Agile was in 1985 in a paper called "Agile Manufacturing" which was the first step to create the forum where agile and agility was defined in 1990 (I am saying that just to add information about something you pointed out). I am writting all these becasue I was part of it.
If we are talking about the same thing and we know it then I could not care less what you call it. 80% of time spent on explaining what something is/is not is such a waste of time and energy. Way too often I have seen somebody raise a question that is very clear and concise but might use different terminology. The bulk of the conversation is then around the wrong use of terminology instead of the question. I would rather spend half that just to ensure we are talking about the same thing and then move on to more important things. Oh, and BTW Agile is a Framedology ;)
I think we all tend to compartmentalize what happens around us. It leads to the use of labels and other divisors.
We should spend more time on what the speaker meant to say rather than how the speaker should say it.
As a leader, I try to understand what people mean even when they don't use the right terms. Language barriers can take intentional effort to work through. As a SME who must clearly communicate concepts and direction to others, I believe using the right terminology is important.
In Alexandre's original question I could read 2 separate questions:
1) Is agile more a philosophy or a cookbook?
2) Who's recipe for agile is best?
When the discussion is 1), that's usually a linguistic barrier. When the discussion is 2), that is usually people marketing their brand.
I have seen so many people come out of some kind of agile training or inherit some "agile process", and are convinced it is a set of rules which must be followed which shows that they missed much of the point. I try to help them understand that it is more of a guiding philosophy than a highly structured set of rules.
Using the right terminology as a SME may also impact your credibility with others. Consciously or not professionals often use words that sound like they are more technical in their description to showcase their knowledge. When speaking to someone who understands the actual meanings, using the wrong terms can actually erode their credibility, because the expert realizes the speaker doesn't actually understand the subject.
Please login or join to reply