Have you ever spent a two-hour Information Systems Department meeting without understanding a word of what was being said, just nodding when asked a question? So learn the jargon before getting fired. Speaking the same language as bullshitters is one of the keys to your future success. Plus you’ll be able to interact better and perhaps convey some good ideas for improvement (reminder: that’s half of what you get paid for, second half being perfect implementation).

- RF*

Request for *: corporate process aimed at one’s suppliers. Usually a tender.

- RFI

Request for Information: most of the time about a product (functionalities, pricing, etc.).

- RFQ

Request for Quotation: the client broadcast on its e-procurement system some specifications, and suppliers are asked to make a bid (price) to sell their product or service.

- RFP

Request for Proposal: the client asks its potential contractors to submit an integrated financial and technical offer, mentioning deliverables precisely and a schedule.

- QIP

Quality Insurance Plan: a document summarizing all quality processes and action linked with project deliverables (versions and updates management, engagement management, accountability, document management, etc.)

- PMP

Project Management Plan: a document stating the way (budget, processes, investments, stakeholders) a project will be led to success.

I’m sure you already know the ones below:

- UT

Unit Tests: when the developer tests her/his program her/himself.

- FT

Functional tests: testing the deliverable’s functional scope.

- iTests

Integration Tests: first tests made when different deliverables get integrated together.

- ST

System Tests realized on an integrated system using a test collection document. External modules might be simulated.

- TAM

Third-party Applicative Maintenance: maintenance and customer support realized by a third-party, i.e. a company that doesn’t host or hasn’t devised the system. Maintenance can be either corrective or aimed at upgrading quality standards, functionalities or performance.

- TAD

Technical Architecture Document: folder in which both physical architecture and operational model are described. Document aimed at facilitating maintenance and operational support. Functions are of course described, but what counts most is the detailing of the physical architecture of the system (servers, storage, parameters, flows, addressing plan, etc.).

Can you think of other useful jargon acronyms?