Product Operations Program ManagerBarcelona, Cataluña, Spain
FUBAR = Fouled Up Beyond Any Recognition. Used when things really turn ugly on a project.
Credit: Ammar Mango
...
1 reply by Rami Kaibni
Jan 23, 2020 12:04 PM
Rami Kaibni
...
Eduard, we can make an acronym for anything for would you put FUBAR in your minutes or an email ? :-)
Saving Changes...
Mbi Lawrence MbiProject Manager| Rakuten Symphony DeutchlandDuisburg/ NRW, Germany
Jan 15, 2018 7:52 AM
Replying to Kiron Bondale
...
George -
Here's ATDD from the Agile Practice Guide: "A method of collaboratively creating acceptance test criteria that are used to create acceptance tests before delivery begins."
I would have defined it as a good development practice which reduces gold-plating and increases quality by developing acceptance tests first and then developing only as much of the solution as is required to pass those acceptance tests.
I will present PERT - Program Evaluation & Review Technique which as per Wikipedia is "a method of analyzing the tasks involved in completing a given project, especially the time needed to complete each task, and to identify the minimum time needed to complete the total project."
Of course, the 5th edition of the PMBOK Guide took a different view focused purely on the use of the PERT formula: "A technique for estimating that applies a weighted average of optimistic, pessimistic, and most likely estimates when there is uncertainty with the individual activity estimates." Still, that's better than the 6th edition which eliminated PERT!
My favorite non-acronym is Gantt - I'm always amused when I see someone capitalize all the letters in it or try to come up with "what it stands for". Henry Gantt must be revolving at high speed in his grave whenever that happens!
Kiron
I am really glad to know about the ATDD , for sure I am yet to dig into the agile practice guide . Saving Changes...
RAM – Responsibility Assignment Matrix: is used to organize the work that is to be completed into elements and comparing it to resources. This is to ensure that adequate resources are available to complete the planned work. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 23, 2020 4:21 AM
Replying to Eduard Hernandez
...
FUBAR = Fouled Up Beyond Any Recognition. Used when things really turn ugly on a project.
Credit: Ammar Mango
Eduard, we can make an acronym for anything for would you put FUBAR in your minutes or an email ? :-)
...
1 reply by Eduard Hernandez
Jan 24, 2020 4:37 AM
Eduard Hernandez
...
Absolutely not ;-) I came across this invented acronym and found it worth sharing. But this brings the question: who decides on when a series of words can become an acronym? For instance, one could say that Laughing out Loud falls in the same category as FUBAR.
George,
Nice that you bring back this discussion.
We should limit to real acronyms that get used in projects. Some other acronyms are funny, there are over a million acronyms.
PM acronym is used for 195 different definitions :-) Saving Changes...
NA is used in many places, I found over a hundred definition.
In the project context, I can see a few ways it gets used
Not Available
Not Applicable
Not Authorized
Not Approved
Not Assigned
No Action
Not Acceptable and what about No Acronyms ;-)
Product Operations Program ManagerBarcelona, Cataluña, Spain
Jan 23, 2020 12:04 PM
Replying to Rami Kaibni
...
Eduard, we can make an acronym for anything for would you put FUBAR in your minutes or an email ? :-)
Absolutely not ;-) I came across this invented acronym and found it worth sharing. But this brings the question: who decides on when a series of words can become an acronym? For instance, one could say that Laughing out Loud falls in the same category as FUBAR.
...
1 reply by Wade Harshman
Jan 24, 2020 4:06 PM
Wade Harshman
...
"FUBAR" had a slightly more colorful meaning when I first learned it. As did "SNAFU." Both of those acronyms seem to have become commonplace in business, government, and broadcasting. You're right, though, I wouldn't personally use it in official correspondence.
Saving Changes...
Biren ParekhDirector| CRISILMumbai, Maharastra, India
FMEA - Failure Mode and Effect Analysis
It refers to a technique that represents an analytical procedure in which each and every singular potential and possible failure in each and every singular product component is reviewed and thoroughly analyzed in order to determine the ultimate effect of said failure on the overall reliability of the component by itself, or in conjunction with other possible modes of failure, on the overall reliability of the system or product in question, and on the ultimate effects on the functionality requirements of the product in question., It can also refer to the complete examination of the product to determine and itemize any and all potential ways in which a failure may take place For each potential failure, a formal estimate is derived to determine potential impact and in some cases the anticipated cost of both making up financially for said failure and also possibly the estimated costs in modifying the project to minimize the risks of this failure. Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Jan 23, 2020 12:56 PM
Replying to Vincent Guerard
...
NA is used in many places, I found over a hundred definition.
In the project context, I can see a few ways it gets used
Not Available
Not Applicable
Not Authorized
Not Approved
Not Assigned
No Action
Not Acceptable and what about No Acronyms ;-)
:)
...
1 reply by Vincent Guerard
Jan 24, 2020 1:42 PM
Vincent Guerard
...
I just listed those that could be of use in project context.