What Actually Happens on Day One in an Engineering Team
When you join your first tech company in Bangalore, Pune, Hyderabad, or on a remote team, nobody tests you on textbook data structures. Your manager sets up your email, your tech lead adds you to the project repository, and you get a calendar invite titled: 'Sprint Planning & Backlog Grooming'.
You open Jira or Linear, see columns labeled 'To Do', 'In Progress', 'In Review', 'QA', and 'Done', and your heart sinks. You start wondering: What is a story point? Why is everyone talking about sprints? Am I expected to finish five tasks by Friday? What if my code breaks?
I felt that exact imposter syndrome when I started at my first low-paying developer job. Coming from self-study with zero formal team experience, I was terrified of sounding clueless in front of seniors. Let me take the mystery out of Agile so you can walk into your first sprint meeting with complete confidence.
1. The Big Picture: Why Teams Use Agile
Before Agile became popular, software teams used the Waterfall model. A client or manager wrote down a massive list of requirements. Developers spent nine months writing code in complete isolation. When they finally launched the product, the client realized half the features were unnecessary, users found critical bugs, and the company wasted millions of rupees.
Agile solves this by breaking work into small, iterative cycles (usually two weeks long) called sprints. At the end of every sprint, you ship a small piece of working software. The customer tests it, provides feedback, and the team adjusts the roadmap for the next two weeks.
2. Scrum vs Kanban: The Two Models You Will Encounter
Almost every software company uses either Scrum or Kanban:
Scrum: Time-Boxed Sprints
In Scrum, the team commits to a fixed set of tasks for a fixed period (typically two weeks). You do not add random new tasks midway through the sprint unless it is a critical production hotfix. Scrum is common in product companies building feature roadmaps on predictable schedules.
Kanban: Continuous Flow
In Kanban, there are no fixed two-week sprints. Instead, tasks flow continuously across the board from left to right. The team sets Work-In-Progress (WIP) limits on columns to prevent developers from starting five tasks at the same time. Kanban is common in site reliability engineering, DevOps, and maintenance teams handling incoming support tickets.
3. The Four Agile Ceremonies Explained Simply
As a developer on a Scrum team, your week will revolve around four recurring meetings:
- 1. Sprint Planning: Held on the first day of the sprint. The product owner presents user stories (features). Developers discuss implementation details and estimate how complex each task is.
- 2. Daily Standup: A quick 10-minute morning sync. You tell your teammates: what you completed yesterday, what you plan to work on today, and whether anything is blocking your progress.
- 3. Sprint Review (Demo): Held on the last day of the sprint. Developers demonstrate the working features to product managers and stakeholders on a staging server.
- 4. Sprint Retrospective: An internal engineering meeting right after the demo. The team discusses what went well, what caused friction, and what process improvements to try next sprint.
4. How Story Points and Ticket Sizing Work
During sprint planning, you will see teammates assign numbers like 1, 2, 3, 5, or 8 to tickets. These are story points, and they measure complexity, uncertainty, and effort rather than literal hours.
| Story Points | What It Means | Real-World Example |
|---|---|---|
| 1 Point | Trivial task with zero unknowns | Fixing a typo in a modal or changing button colors |
| 2 Points | Simple task with clear boundaries | Adding a new field to an existing API response and updating tests |
| 3 Points | Standard task with moderate effort | Building a new database table, backend endpoint, and basic frontend view |
| 5 Points | Complex task with third-party dependencies | Integrating a payment gateway with webhook verification and error handling |
| 8+ Points | Too large for a single ticket | Needs to be split into multiple smaller tickets before the sprint begins |
Tip for freshers: When sizing tickets, never call a ticket a 1-point task if you have never worked with that part of the codebase before. Always give yourself room to read the code and write tests.
5. Three Mistakes Freshers Make in Agile (And How to Avoid Them)
During your first six months, avoid these three common mistakes:
- Staying Silent When You Are Blocked: If you are stuck on an environment issue or confusing error for three hours, tell your senior developer immediately. Waiting until the next morning standup to admit you made zero progress is what causes missed deadlines.
- Hoarding Multiple Tickets: Never pull three tickets into 'In Progress' simultaneously. Pick one ticket, write clean code, write unit tests, open a pull request, and get it merged before picking up the next task.
- Forgetting to Move Jira Cards: Keep your board updated. When you start working on a ticket, move it to 'In Progress'. When you open a pull request, move it to 'In Review'. If your board reflects reality, managers will never micromanage you.
You do not need to pay twenty thousand rupees for a Scrum certification to succeed as a developer. Focus on clear communication, write clean code with tests, and stay honest with your team. Explore our Free Developer Tools including our JSON Formatter to speed up your everyday API testing.