✅ UNIT–III: Introduction to Scrum (Simple Notes)

 

✅ UNIT–III: Introduction to Scrum (Simple Notes)

⭐ 1. What is Scrum?

Scrum = most popular Agile framework.
Work happens in small cycles called Sprints (1–4 weeks).

👉 Simple meaning:
Plan → Build → Test → Show → Improve → Repeat

⭐ 2. Scrum Framework (Super Easy)

Scrum has 3 parts:

  1. Roles

  2. Events (Meetings)

  3. Artifacts (Documents)

⭐ 3. Scrum Roles (VERY IMPORTANT)

1. Product Owner (PO)

  • Decides what to build

  • Creates and manages Product Backlog

  • Talks with customer

👉 Keyword: Vision + Priority

2. Scrum Master (SM)

  • Helps team follow Scrum

  • Removes blockers/problems

  • Not a boss — a servant leader

👉 Keyword: Helper

3. Development Team

  • 5–9 members

  • Build the product

  • Self-organizing

👉 Keyword: Builders

⭐ 4. Scrum Artifacts (Simple Meaning)

A. Product Backlog

A big list of all features, tasks, ideas.

B. Sprint Backlog

Tasks the team will do in this sprint.

C. Increment

The working software created after each sprint.

👉 Easy Trick: P → S → I
(Product Backlog → Sprint Backlog → Increment)

⭐ 5. Scrum Meetings (Events)

1. Sprint Planning

  • Start of sprint

  • Decide: What work will be done?

2. Daily Scrum (Stand-up)

  • 15-minute meeting

  • Each member answers:

    • What did I do yesterday?

    • What will I do today?

    • Any issues?

3. Sprint Review

  • Show completed work to customer

  • Get feedback

4. Sprint Retrospective

  • Team discusses:

    • What went well

    • What needs improvement

👉 Easy Trick: Plan → Daily → Review → Retro

⭐ 6. Scrum Team Simulation (Simple Meaning)

Simulation = practice Scrum using a small example/project.

Example:
Team simulates:

  • planning

  • creating backlog

  • sprinting

  • review

  • retrospective

👉 Just understand: like a mock test of Scrum.

⭐ 7. Scrum Planning Principles (Easy Points)

  • Plan only for small time (sprint)

  • Prioritize important items

  • Make tasks small

  • Team must estimate tasks

  • Plan must be realistic

⭐ 8. Product & Release Planning

Product Planning

  • Create vision

  • Add features to product backlog

Release Planning

  • Decide which features go in future releases

  • Example:

    • Release 1 → Login, Signup

    • Release 2 → Cart, Payment

⭐ 9. Sprinting (3 Steps)

A. Sprint Planning

Choose tasks for sprint.

B. Sprint Execution

Team works:

  • coding

  • testing

  • designing

C. Sprint Review + Retrospective

  • Review = show work

  • Retrospective = improve next sprint

⭐ 10. User Stories (VERY IMPORTANT)

Simple requirement written from user’s view.

Format:
👉 As a [user], I want [feature], so that [benefit].

Characteristics (INVEST Rule — simple)

Good user story is:

  • Independent

  • Negotiable

  • Valuable

  • Estimable

  • Small

  • Testable

👉 Trick: I N V E S T

⭐ 11. Acceptance Tests

Acceptance test =
👉 A test to check if a user story is fully complete.

Example:
User story: “Add to cart”
Acceptance test:

  • Item should appear in cart

  • Quantity can be changed

⭐ 12. Verifying Stories

Verifying story = checking:

  • Is it complete?

  • Does it meet acceptance criteria?

  • Does it work for user?

⭐ 13. Burndown Chart

Burndown chart shows:

  • On X-axis: Time

  • On Y-axis: Work remaining

👉 Simple meaning:
How much work is left in sprint?

⭐ 14. Daily Scrum

A short 15-minute meeting.
3 questions:

  1. What did I do yesterday?

  2. What will I do today?

  3. Any blockers?

⭐ 15. Scrum Case Study (Easy Version)

Example Case Study:

Project: Online Food Delivery App

  • Product Owner creates backlog (Login, Menu, Cart, Payment)

  • Team selects tasks for Sprint 1

  • Daily Stand-up

  • Sprint Review → Show login & menu

  • Retrospective → Improve communication

👉 Write any small example like this.
Full marks.

🎯 Unit-III Memory Booster (Final Quick List)

  • Scrum = 3 Roles + 3 Artifacts + 4 Meetings

  • Roles → PO, SM, Dev Team

  • Artifacts → Product Backlog, Sprint Backlog, Increment

  • Meetings → Planning, Daily, Review, Retro

  • Sprint = 1–4 weeks

  • User Story = As a user, I want…

  • INVEST → Good story rule

  • Burndown Chart → Work left vs time

Comments

Post a Comment

Popular posts from this blog

⭐ UNIT – 3 (Easy Notes + PDF References) Wireless LAN • MAC Problems • Hidden/Exposed Terminal • Near/Far • Infrastructure vs Ad-hoc • IEEE 802.11 • Mobile IP • Ad-hoc Routing

  ⭐ UNIT – 3 (Easy Notes + PDF References) Wireless LAN • MAC Problems • Hidden/Exposed Terminal • Near/Far • Infrastructure vs Ad-hoc • IEEE 802.11 • Mobile IP • Ad-hoc Routing I have rewritten everything in easy school-level English so you can understand quickly. 🔵 1. What is WLAN? (Wireless LAN) (Page 1 U-3 Wireless & mobile computing ) WLAN = Wireless Local Area Network. It allows devices to connect without cables using radio, infrared, or microwave signals. Why WLAN? ✔ No wires needed ✔ Quick installation ✔ Can attach to existing wired network ✔ Useful in disasters or old buildings where wiring is impossible 🔵 2. Design Goals of WLAN (Page 2–3 – Table shown in PDF U-3 Wireless & mobile computing ) ✔ Simple to use Users should easily connect. ✔ Low power use Mobile devices need long battery life. ✔ No license needed Using license-free bands reduces cost. ✔ Handle interference There is a lot of radio noise; WLAN must work even in interference. ...
Read more

UNIT–5 (Simplified & Easy Notes) Software Architecture Documentation

  UNIT–5 (Simplified & Easy Notes) Software Architecture Documentation ✅ What is Software Architecture Documentation? It explains how the software system is structured . Helps developers understand system components , modules , and design , without reading code. Works as a communication tool between architect, developer & stakeholder. ⭐ Goals of Documentation (Very Important) Knowledge Sharing Helps new developers understand the system quickly. Communication Architects share design ideas with developers. Analysis & Review Used to check if architecture meets requirements. ⭐ Two Ways to Create Architecture 1. Top-Down Approach Start from big design → break into smaller parts. Used when system requirements are clear. 2. Bottom-Up Approach Start from small components → combine to form system. Used when building systems step-by-step. ⭐ Principles of Sound Documentation (Super Important – Exam Repeated) Princ...
Read more

ch 2 pm

 Here's a breakdown of the Software Engineering Institute's (SEI) Capability Maturity Model Integration (CMMI) framework elements, particularly relevant to the Unified Process (UP) and other structured methodologies: Framework Elements: Life Cycle Phases: Inception: Focuses on establishing the project's vision, scope, business case, and feasibility. Elaboration: Defines the architecture, refines requirements, and plans the remaining project. Mitigates high-risk elements. Construction: Iteratively develops and integrates the bulk of the software, building working versions. Transition: Deploys the software to the user community and ensures operational readiness. (Note: Your request mentioned "training phase" which often aligns with Transition activities.) Artifacts of the Process: The Artifact Sets (Categories): Management Artifacts: Pertain to project planning, tracking, and control (e.g., business case, project plan, risk list). Engineering Artifacts...
Read more