Welcome to Authentic Journeys - ഓതെന്റിക് ജെർനീയ്സ് - US-India Cross-Cultural Training

Authentic Journeys on Facebook
Authentic Journeys on YouTube
Authentic Journeys on LinkedIn
Authentic Journeys on WhatsApp
    Welcome to Authentic Journeys - ഓതെന്റിക് ജെർനീയ്സ് - US-India Cross-Cultural Training

September 12, 2020

Meanings of Words Used in Software Development in Ordinary English

Words Techies Use - For the rest of us!
This glossary is a work in progress. As I post this in September 2020, I have a list of over 130 words and phrases used by techies in daily conversations at work (with only about 1/3 defined). As I know there are plenty of people like me out there who interact with techies, but may not always get the technical language, I have decided to put together this dictionary of terms that are used in the industry so we can learn their language! This glossary may also help techies to talk about technical concepts to non-technics in more of a conversational English, or a non-industry English to help build context with their clients, stakeholders and others they interface with everyday. 

This glossary not only includes technical or industry jargon many use in the software industry, but also includes vocabulary (buzzwords, corporate speak, etc.) used in professional, office settings that may or may be recognized outside of the software or IT realm as well. 

The purpose of this glossary is to try to define the technical terms in English that can be understood by anyone. If you have ideas to help me fill in the blanks for the words not yet defined or to update the definitions of words already defined, contact us through our contact page to share your insights. If your business website/blog has definitions we can use here, we are happy to quote your resource and link back (we also hope for a link back to this post or another post on this blog). 

Let's get started!

Meanings of Software Developers Use 

A Dictionary For the Rest of Us!




Agile Manifesto

ASAP: Short form of “as soon as possible.” 
Cultural Tip: May be used in place of “at the earliest convenience” (Indian English). However, use with caution, as some may find this to be “not so polite.” 
Acronym expansion: As soon as possible

Avail: (short for available) free at the moment

Average handling time

AWOL: May be used in a meeting to inform the rest of the attendees someone is absent. (MIA is another similar term.) These terms derive from military culture, but are often used in corporate speak as well. 
Pronunciation Tip: When saying “AWOL” it is pronounced as a word, which sounds like “a wall.” MIA is pronounced as separate letters – eM – eye – ay. 
Acronym expansion: Absent without leave

Backlog: tasks not yet done by the team for the duration of a project, during a sprint, during a release (it’s like a to-do list of things that need to be done – features, bugs, etc.) May also be known as a PBI or a Product Backlog

Bandwidth: time and/or energy to help out or get involved (synonym: cycles) Sample question: Do you have the bandwidth?



Billable staff

Billed hours

Bio break: A euphemism for stating one has to go to the toilet or use the restroom. 
Cultural Tip: In the US the word “toilet” refers only to the toilet itself and not the room the toilet is in. So, in the US, people may use the word bathroom (even if there is no bathtub in the room), restroom, ladies room, men’s room, etc.).


BRB: Short form of “be right back.” Frequently used in chat conversations. However, note in more formal business chats, short forms should be avoided.

Bug /Bug fix

Burn down/burn down chart

Buy in: Get someone to agree to something 
See this blog:  Getting "Buy In" When Delivering Constructive Criticism 

C-sat Expansion of short form: customer satisfaction

Cascade: pass it down, share with others 
Sample use: Could you cascade this information to the team? Please feel free to cascade this as deemed fit. (Nidhin Joseph)


Cloud enabled

Cloud native: A digital product that is created and maintained in the cloud. No servers are needed for cloud native apps or software. 

Coding Language

Concall: Short way to write or say “conference call.”


Core competency

Crack team: a team of experts who ‘spearheaded’ a transition through to ‘pilot’ 
Synonym: core team. (Nidhin Joseph)

Creative Interface: It is the creative user interface design which is the graphical layout of an application.

Cron: a job scheduled to run at a specified time

Cross-functional team



Deck: A PowerPoint (PPT) slide deck

Deep dive


Demo: As elements of the software are completed and are functional, the developers demonstrate the functionalities of what has been completed so far (also may be called ‘sprint demo’) 
See our program "Wow US Clients at the Demo" 




DevOps - the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications (faster time to market) and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. (The development and production environments would be identical.)

Development Environment: the developer’s workstation (which may or may not be the final target environment – which could be a mobile device, embedded system, data center, etc.). Some call this the ‘sandbox.’

Digital Design

Drill down

Due diligence

EOD: Short form of End of Day or End of Business Day (EOB). 
Communication/Cultural Tip: When using this word, it’s not always clear to the receiver what time this refers to, as we may end our working days at different times. This is even more important when working across time zones. It may be helpful to add an actual time with a time zone identifier (EOD, by or before 5pm EST).

End users/users: end users are the actual people using the app or website. The end users will be referred to by different terms based on the business: college (students), store (customers), consulting (clients), hotels (guests), etc. 




Fire fighting

Functional specification: “A functional specification is a formal document used to describe a product's intended capabilities, appearance, and interactions with users in detail for software developers. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code.” From TechTarget Network   


Go live

Hard copy/soft copy

Heads up


Impediments: See "road blocks" 


Issue resolution: outcome of the problem and/or the process of how a problem needs to be resolve 
Acronym or short form: IR 
How to use it in a question: What was the issue resolution for that enquiry from the customer? 
How to use it in a sentence: We did use the IR before the closing the call.


Logged in hours

Login time


Low hanging fruit: something completed or obtained with little to no effort 
Cultural note: This idiom is used outside the offices in ordinary conversations as well.




Non Disclosure Agreement (NDA)

See more: Terminology of Outsourcing & Outsourcing FAQ


Onprem: On premises – hosted onsite vs the cloud


OOO: out of office


Ping: A full description of the meaning of "ping" and "ping me" is here.




Product Owner

Production Environment: This is the actual live version of the app or website that the end users (customers, clients, students, general public) can access. It is in the production environment where features ‘go live.’

Proof of concept (POC)/Prototype

Quick Fix


Recovery work

Red flag: A warning about something

Regroup: meet again later How to use it in a sentence: We are running out of time today, let’s regroup tomorrow at the same time.
This word could be used in a question form if the client wants to extend the meeting, but you have another meeting to get to: “This is an important matter that we are addressing. Unfortunately, as it’s near the top of the hour, I have a meeting with my manager now. Shall I meet with her now, discuss this with her, and we can regroup later?” 

Release: A series of sprints 

Retrospective: the last ceremony in a series of sprint ceremonies where the team ‘regroup’ to review the project; what went well and things to improve for the upcoming projects 

Revert/Roll Back Roadblock: something that is causing us to get stuck when solving a problem, an impediment (“blockers” is also a common shorter form of this word I have heard) 
Cultural note: This is an actual word used in conversation out of work, which means a physical roadblock in the road- such as the picture below. 
Synonyms: I have heard “speed bump,” “bump in the road,” “hiccup.” 
Cultural Note #2: When working with US clients, it’s not a good idea to always only talk about roadblocks without discussing any possible solutions that have been tried (and why they may not be the right solution), or possible solutions that have not been tried yet, or open the conversation up to the clients to see if they have ideas. In coaching we practice how to articulate this in a quick and succinct way during stand-up meetings

A literal roadblock! We can't go any further - ROAD CLOSED!

Roadmap: a plan about how a project will be undertaken 

Roll out: software development process of introducing a new feature to a set of users  

Rota: schedule for a group of people (Origin: British English, may not be used in the USA) 



Scrum Master 

Self-organizing team

Service Level Agreement
Short form: SLA




: Used in a question: Will there be any spill over after this sprint?

Spill over: Spill over are the stories which did not meet the criteria of the current sprint. 
Sentence example: It looks like we will have some spill over after this sprint.

Stories/User Stories


Scrum Ceremonies: the series of “meetings” that constitute a sprint- Sprint Planning, Daily Scrum (aka daily stand up), Sprint Review (aka iteration review), Sprint Retrospective (Also known as “scrum events.”)  

I’ve also seen them termed as sprint ceremonies or agile ceremonies. The word ‘events’ can be used in place of ‘ceremonies’ (scrum events, agile events, sprint events).  

SDLC: This acronym seems much more common than the expansion, below. It refers to the methodology or process chosen by a team or company in executing a software development project. The most common types are agile and waterfall, which can sometimes be combined, though there are conflicting viewpoints about this. A few other SLDC approaches are: DevOps, iterative model, V shaped model, big bang model, spiral model Long form: Software Development Life Cycle


Shippable product

Stand up meeting/daily stand up meeting

Long form:Statement of Purpose

Sprint: the shortest amount of time to achieve tasks in a backlog (a way of time and task management in the agile methodology)

Staging/Staging Environment: A staging environment is a clone of your deliverable/shippable in a semi-private environment. It’s a clone of the real thing, but not ‘live.’ So, for example, for a website, it could be “staged” on a URL that is not available to the public. Staging helps the team and stakeholders interact with the product in a simulated environment to identify the usability, bugs, interactivity and other functionalities of the site before it is made public. In this stage, unlike the development stage (where the code is on a local machine), the code will be on a server or in the cloud (if it is cloud native). 

Suite: (as in software "suite") Read about the differences in the words suite/sweet (definition and pronunciation) 

Sunset - And if you are getting rid of an application you are “sunsetting it”.

Sunset means "it's time to say good bye"

Technical Debt: the process of prioritizing speedy delivery over perfect code. Technical debt may be more relevant to agile development than waterfall development.  Also known as: tech debt or code debt

Test cases

Test reports

Time sheet

Time to market



UI Long form: user interface


Upscale: increasing size/scope of operations or improving the quality of a service or product

User Experience

User interface



Work around

Author of this post, Jennifer Kumar, provides leadership and communication coaching to offshore teams in the software industry in Kerala and throughout India. She specializes in working with those who work with US Americans from anywhere in the world, with a focus on US business cultural know-how and English fluency (for ESL and non-native speakers). Get in touch with her to help upskill your team to work more impactfully with US Americans to build, scale and grow your business.

Authentic Journeys: Bridging Culture on Virtual Teams

We help build effective, culturally competent global teams with focus on the cultures of the USA and India. Jennifer Kumar, Managing Director, an American citizen, has almost 10 years experience living, studying and working (owning a business) in India. Authentic Journeys Consultancy is registered as a Private Limited in India (Kerala) and an LLC in the USA (Salt Lake City, Utah). We provide onsite and live-online instructor-led courses, facilitation and corporate coaching.