Agile Aur Scrum Kya Hota Hai? Indian Fresher Guide (Hindi 2026)

"Standup Mein Kya Bolna Hai?" Yeh Pehla Sawal Har Fresher Ka.#

Pehli IT job join ki. Manager ne bola "Kal subah 9:30 standup hai." Tumne soch liya yoga aur meditation karenge office mein. Subah jakar dekha sab log laptop ke saamne baith ke "yesterday, today, blockers" bol rahe hai.

Phir aaye Sprint Planning, Backlog Refinement, Retrospective, Demo, Story Points, Velocity. Aur tum laptop ke saamne baith ke confused face banake "Yes, agreed" bol rahe ho har 5 minute pe.

Yeh sab Agile aur Scrum ka jargon hai. Indian IT industry mein 90% companies isi method se kaam karti hai. Tumhe yeh samajhna padega. Aaj poori process Hindi mein samjhao. Real terms ke saath. Examples ke saath.

---

Pehle: Agile Kya Hai?#

Agile ek way of working hai software banane ka. Iska ulta hai Waterfall, jisme tum 6 months tak plan karte ho phir 6 months mein code likhte ho phir 6 months mein test karte ho. 18 mahine baad customer dekhega, "Yeh toh humne nahi maanga tha."

Agile ka idea hai: chhote-chhote tukdo mein kaam karo, jaldi-jaldi deliver karo, customer feedback lo, badlao.

Agile ek philosophy hai. Iske implementation ke kai tarike hai. Sabse popular hai Scrum. Doosra popular hai Kanban. Indian companies mein 80% teams Scrum follow karti hai.

---

Scrum Kya Hota Hai? Simple Words Mein#

Scrum mein tumhari team chhote chhote cycles mein kaam karti hai. Har cycle ko Sprint kehte hai. Usually 2 weeks ka.

Sprint mein tum decide karte ho ki "yeh 5-7 cheezein iss 2 hafte mein khatam karenge." Phir 2 hafte ke baad sab present karte ho. Lessons seekhte ho. Next sprint plan karte ho.

Yahaan complete Scrum cycle hai:

1. Sprint Planning (Day 1) - Decide karo kya kaam hoga 2 weeks mein
2. Daily Standup (Day 1-10) - Roj 15 min ka meeting
3. Sprint Demo / Review (Day 10) - Kaam dikhao
4. Retrospective (Day 10) - Sprint kaisa raha discuss karo
5. Backlog Refinement (Mid-sprint) - Future kaam plan karo

Phir cycle repeat. Saal mein roughly 26 sprints hote hai.

---

Sprint Mein Kya Hota Hai?#

Sprint matlab fixed time period (usually 2 weeks). Iss time mein tum aur tumhari team agreed-upon kaam complete karte ho.

Sprint ka structure:

• Day 1 (Sprint Planning): 1-2 ghante ka meeting. Product Manager batata hai customer/business ko kya chahiye. Team estimate karti hai kitna time lagega. Sab milke decide karte hai 2 weeks ka scope.

• Day 1-10 (Development): Tum apna kaam karte ho. Code likhte ho, test karte ho, code review submit karte ho.

• Day 10 (Sprint Demo): Sab apna kaam dikhate hai. Product Manager aur stakeholders feedback dete hai.

• Day 10 (Retrospective): Team discuss karti hai - "kya acha gaya," "kya improve karna chahiye."

• Day 11 = Day 1 of next Sprint

---

Daily Standup Kya Hota Hai?#

Yeh roj subah ka 15-minute meeting hai. Sab khade hokar karte hai (isliye "standup" - taaki short rahe).

Tumhe 3 cheezein bolni hai:

1. Yesterday: Kal kya kiya
2. Today: Aaj kya karunga
3. Blockers: Koi problem hai (kuch atak gaya hai)

Example:

"Yesterday I completed the login API. Today I will start working on the password reset flow. No blockers."

Bas. Itna hi. Long discussions nahi karne. Agar koi blocker hai toh "let's discuss after standup" bolo.

Standup pe galti #1: Bahut detail mein chala jata. "Maine pehle Slack pe message dekha phir code khola phir 30 min debug kiya phir realize kiya semicolon missing tha..." Nahi. Bas summary do.

Standup pe galti #2: Blockers chhupana. Agar tum atak gaye ho aur senior ki help chahiye, bolna padega. Warna sprint end mein dikhega jab kaam pending hai.

---

Sprint Planning Kya Hota Hai?#

Yeh sprint ka pehla meeting hai. 1-2 ghante ka. Pure team baith ke decide karti hai 2 weeks ka kaam.

Sprint Planning ka format:

1. Product Manager priorities batata hai. "Yeh top 5 cheezein important hai customer ke liye."

2. Team requirements clarify karti hai. "User login mein OAuth chahiye ya simple password?" "Mobile pe bhi kaam karega?"

3. Estimates dete hai team members. "Yeh 3 din lagega," "Yeh 5 din."

4. Final scope agree karte hai. "Yeh 7 stories iss sprint mein karenge."

Story Points kya hote hai?

Story points ek estimation hai effort ka. Time mein nahi (kyunki time har banda ka alag), abstract units mein.

Common scale: 1, 2, 3, 5, 8, 13 (Fibonacci sequence).

• 1 = chhota kaam, half day mein khatam
• 3 = medium kaam, 1-2 din
• 5 = bada kaam, 3-4 din
• 8 = bahut bada, full sprint
• 13 = bigger than sprint, ise tod do chhote tasks mein

Indian companies mein zyada teams story points use karti hai. Kuch directly hours use karti hai. Tumhe jo team use kar rahi hai woh seekho.

---

Sprint Demo / Review Kya Hota Hai?#

Sprint ke end mein tum poori team aur stakeholders ko apna kaam dikhate ho. Live demo. Working software.

Tumhe ek feature dikhana hoga, kaise kaam karta hai. Stakeholders feedback denge.

Demo ke common mistakes:

1. "Yeh kaam karega... bas dikha nahi raha" - demo se pehle test karo. Kabhi local pe demo mat karo, staging ya production-like environment use karo.

2. Long technical explanations. Stakeholders ko code samajhna nahi hai. Bas feature dikhao.

3. Demo mein "I" use karna. "I built this..." Nahi. "We built this..." Team kaam tha.

---

Retrospective Kya Hota Hai?#

Sprint ke end mein team baith ke discuss karti hai - "kaisa raha sprint." Demo ke baad hota hai. 1 ghanta.

Standard format (4 questions):

1. Kya acha hua? ("Code reviews fast the")
2. Kya bekaar hua? ("Last 2 din mein 3 production bugs aaye")
3. Kya seekha? ("API rate limiting properly handle karna chahiye")
4. Action items? ("Next sprint mein rate limiting add karenge")

Retrospective mein honest bolna important hai. Lekin negative tone mein nahi. "Kal nikhil ne PR review nahi kiya" mat bolo. "PR reviews mein sometimes delay hoti hai, kya hum SLA decide kar sakte hai?" bolo.

---

Backlog Refinement (Grooming) Kya Hai?#

Yeh mid-sprint mein hota hai. 1 ghanta. Team future ka kaam discuss karti hai.

Product Manager naye user stories laata hai. Team questions puchti hai. Estimates lagati hai. Acceptance criteria define karti hai.

Yeh meeting iss liye important hai ki next sprint planning fast ho. Agar tumne abhi sab stories refine kar diye hai toh next planning meeting mein sirf select karna padega.

---

Roles in Scrum#

Scrum team mein 3 main roles hote hai:

1. Product Owner (PO) / Product Manager (PM)

Yeh banda customer aur business ke needs ko team tak laata hai. Backlog maintain karta hai - kaunse features priority hai.

PO decide karta hai kya banana hai. Team decide karti hai kaise banana hai.

2. Scrum Master

Yeh banda Scrum process ko smoothly chalata hai. Meetings facilitate karta hai. Blockers remove karta hai. Process ko follow karwata hai.

Indian companies mein Scrum Master often part-time role hota hai - same banda dev work bhi karta hai aur Scrum Master bhi hota hai.

3. Development Team

Tum, baaki engineers, designers, testers - yeh team development banata hai. Usually 5-9 log ka.

Junior developers (freshers) ko Software Engineer ya SDE-1 bolte hai. Yeh tumhara starting role hoga.

---

Common Scrum Tools#

Indian companies mein yeh tools commonly use hote hai:

1. Jira (Most Common)

Atlassian ka tool hai. Indian IT mein 70% companies Jira use karti hai.

Jira mein:

• Stories, tasks, bugs create hote hai
• Sprints plan hote hai
• Boards (To Do → In Progress → Code Review → Done) dikhte hai
• Reports nikalte hai (velocity, burndown)

Tumhe Jira ka basic use seekhna chahiye. YouTube pe 1 hour ka tutorial dekho.

2. Confluence

Atlassian ka doosra tool. Documentation ke liye. Meeting notes, design docs, runbooks sab yahaan likhe jate hai.

3. Slack / Microsoft Teams

Daily communication. Channels alag hote hai (engineering, product, random, etc.).

4. GitHub / GitLab / Bitbucket

Code repository. Pull requests yahaan create hote hai.

---

Standup Mein Achi Update Kaise Do#

Yeh most important skill hai pehle 3 months mein. Acche updates se manager ki impression banti hai.

Bekaar update: "Yesterday I worked on the login feature. Today I will continue. No blockers."

Achi update: "Yesterday I completed the OAuth integration with Google. Tested locally, all 5 test cases passing. Today I will write integration tests and submit a PR by EOD. No blockers."

Farak dekho:

• Specific deliverable mention kiya (OAuth, 5 test cases)
• Timeline diya (EOD)
• Progress show kiya (testing done)
• Tomorrow's plan clear hai

Pehle hafte mein notebook leke jao standup mein. Apni 3 lines pre-write kar lo. 1 month mein natural ho jayega.

---

Sprint Mein Kuch Kaam Pending Reh Gaya Toh?#

Hota hai. Sab kuch sprint ke andar khatam nahi hota. Galti chhupao mat.

Sahi tarika:

1. 2-3 din pehle hi flag karo. "Bhai, mujhe lag raha hai login feature iss sprint mein khatam nahi hoga."

2. Reason batao. "Backend API thoda complex tha, 1.5 din zyada lag rahe hai."

3. Solutions suggest karo. "Kya hum acceptance criteria thodi reduce kar sakte hai? Ya next sprint mein carry-over karte hai?"

4. Naye sprint mein priority pakda lo. Carry-over tasks first thing in next sprint.

Sprint demo mein pakad mein aaye - "yeh half-done hai" - toh image kharab hoti hai. Pehle se communicate karoge toh team appreciate karegi.

---

Velocity Aur Burndown Chart#

Yeh metrics tumhare manager track karta hai.

Velocity: Team kitne story points complete karti hai average per sprint.

Example: Last 4 sprints mein team ne 25, 28, 22, 26 points kiye. Velocity = 25 average.

Burndown Chart: Sprint ke during graph dikhata hai kitna kaam pending hai. Ideal mein straight line down hoti hai.

Agar burndown flat raha, matlab kaam start hi nahi hua. Agar last 2 din mein sudden drop, matlab sab kaam end mein hua (red flag).

Yeh metrics tumhe directly target nahi karne hai, lekin samajhna chahiye.

---

Agile/Scrum Certifications Worth Kya Hai?#

Freshers ke liye certifications not necessary hai. Lekin agar 2-3 saal experience ke baad Scrum Master ya Product Manager banna hai toh helpful:

1. CSM (Certified Scrum Master) - $1000, basic but useful
2. PSM I (Professional Scrum Master) - $200, harder but cheaper
3. CSPO (Certified Scrum Product Owner) - $1000, for PM track

Pehle 1-2 saal practical experience banao. Phir certification consider karo.

---

Common Agile Vocabulary#

• Backlog: Saari pending stories ki list
• User Story: "As a [user] I want [feature] so that [benefit]"
• Acceptance Criteria: Story complete kab maani jayegi
• Definition of Done (DoD): Team ka shared agreement - "story tab done jab unit tests pass + code reviewed + deployed to staging"
• MVP (Minimum Viable Product): Sabse chhota version jo customer use kar sake
• Tech Debt: Bekaar code jo refactor karna padega
• Refactor: Code ko clean karna without changing behavior
• Spike: Research task (kuch sikhna ya prototype banana, deliverable nahi)
• Epic: Bahut badi story jisme multiple sprints lagenge

Yeh terms har meeting mein bolne wale ho. Yaad rakho.

---

Bottom Line#

Agile aur Scrum Indian IT ka backbone hai. Pehle 3 mahine mein tumhe yeh sab natural lagne lagega.

Quick recap:

1. Sprint = 2 weeks ka cycle
2. Standup = daily 15 min update meeting (yesterday/today/blockers)
3. Sprint Planning = sprint start mein 1-2 ghante (what to do)
4. Demo = sprint end mein dikhao kya banaya
5. Retrospective = discuss kya improve karna hai
6. Backlog Refinement = mid-sprint, future stories prepare

Pehle 2-3 sprints mein observe karo. Notes lo. Questions pucho. 1 month mein tum natural ho jaoge.

Agar tum interview ki preparation kar rahe ho aur Agile/Scrum questions practice karna hai, hamara mock interview tool Scrum-specific questions ka set provide karta hai - "Sprint planning kaise karte ho," "Standup mein blocker kaise communicate karoge," etc.

Yeh sab process pehli baar bekaar lagti hai. 6 month mein tum khud bhi yeh structure prefer karne lagoge. Trust the process.