If you have been looking at tech job descriptions, you have almost certainly seen words like sprint, backlog, standup, and retrospective. Agile is everywhere in tech, and yet most people breaking in have no idea what it actually means in practice. Here is a plain-English explanation of Agile and Scrum — the framework you will encounter at virtually every tech company.
Agile is a mindset, not a process
Agile is a set of values about how software should be built: deliver value continuously rather than all at once, respond to change rather than following a fixed plan, and collaborate closely with users rather than building in isolation. It emerged as a reaction to waterfall — the old approach where teams spent months planning, then months building, then months testing, and only showed the product to users at the very end (often to discover it did not solve the right problem). Agile says: ship something small, learn from it, and improve quickly.
Scrum is the most common implementation
Scrum is a specific framework for practicing Agile. It organizes work into fixed time boxes called sprints — typically two weeks. Each sprint has a goal, a plan, and a review at the end. There are three roles in Scrum: the Product Owner (decides what to build and in what order), the Scrum Master (facilitates the ceremonies and removes obstacles), and the Development Team (builds the product). Most tech teams you will join use some version of Scrum, even if they have adapted the ceremonies to fit their culture.
The four ceremonies
Sprint Planning happens at the start of each sprint: the team pulls items from the backlog and agrees on what can be completed in the next two weeks. The Daily Standup is a short daily check-in — usually 15 minutes — where each person shares what they did yesterday, what they are doing today, and whether anything is blocking them. The Sprint Review happens at the end of the sprint: the team demonstrates what was built to stakeholders. The Retrospective follows the review: the team reflects on how the sprint went and agrees on one or two things to improve.
Kanban: the alternative to Scrum
Kanban is a different Agile approach that uses continuous flow instead of sprints. Work moves across a board (To Do, In Progress, Done) with limits on how many items can be in progress at once — called WIP limits. Kanban is common on support and operations teams where work comes in unpredictably rather than in planned batches. You will encounter both Scrum and Kanban in tech; understanding both makes you a more versatile team member.
Terms that confuse everyone
Velocity is the measure of how much work a team completes per sprint — useful for forecasting, not for comparing teams. Story points are the unit teams use to estimate effort — they are relative, not hours. Backlog grooming and backlog refinement mean the same thing: the ongoing process of reviewing, clarifying, and prioritizing items in the backlog before they enter a sprint. Do not be thrown off when you hear both terms.
What Agile means for your career change
Agile is a culture, not just a process. Tech companies want to hire people who understand that requirements change, that fast feedback beats careful planning, and that collaboration beats documentation. In interviews, you do not need to recite the Scrum framework — you need to show that you get the mindset. Talk about times you adapted quickly, delivered incrementally, or worked closely with users to improve something. That is what Agile looks like from the inside.