Content ITV PRO
This is Itvedant Content department
Introduction to Scrum Framework
What is Agile?
Agile is a modern software development approach where work is done in small parts (iterations/sprints) instead of building everything at once.
Focus:
- Flexibility
- Customer feedback
- Continuous improvement
Unlike traditional methods, Agile allows changes at any stage.
Agile Manifesto defines four values and twelve principles that focus on flexible, collaborative, and continuous software development.
Agile Manifesto (2001)
The Agile Manifesto was created in 2001 by 17 software experts including:
- Kent Beck
- Martin Fowler
- Robert C. Martin
- Jeff Sutherland
They defined 4 core values to improve software development.
4 Agile Values (With Detailed Explanation)
1. Individuals and Interactions
over Processes and Tools
Meaning:
- People are more important than tools or strict processes
- Communication within the team is key
Example:
Instead of only using tools like Jira, direct discussion between developers and testers is more effective.
4 Agile Values (With Detailed Explanation)
2. Working Software
over Comprehensive Documentation
Meaning:
- Deliver a working product rather than spending too much time on documentation
Example:
A working login feature is more valuable than 100 pages of documentation.
4 Agile Values (With Detailed Explanation)
3. Customer Collaboration
over Contract Negotiation
Meaning:
- Continuous interaction with the client is important
- Feedback is taken regularly
Example:
Client reviews each sprint and suggests improvements.
4 Agile Values (With Detailed Explanation)
4. Responding to Change
over Following a Plan
Meaning:
- Agile welcomes changes anytime
- Plans can be modified as per requirement
Example:
If a bank wants to add UPI later, Agile allows easy changes.
12 Agile Principles
1️⃣ Customer Satisfaction
Deliver useful software early and continuously
Example: Deliver login feature first instead of waiting months
2️⃣ Welcome Changing Requirements
Even late changes are accepted
Agile is flexible, not rigid
3️⃣ Frequent Delivery
Deliver software in small parts (sprints)
Example: Every 2 weeks
12 Agile Principles
4️⃣ Collaboration
Business & developers must work together daily
Communication is very important
5️⃣ Motivated Individuals
Build teams with skilled and motivated people
Trust your team
6️⃣ Face-to-Face Communication
Best communication method is direct discussion
Faster problem solving
12 Agile Principles
7️⃣ Working Software is Progress
Progress is measured by working features
Not by documents
8️⃣ Sustainable Development
Maintain a consistent work pace
Avoid burnout
9️⃣ Technical Excellence
Focus on good coding and design
Improves quality
12 Agile Principles
🔟 Simplicity
Do only what is required
Avoid unnecessary work
1️⃣1️⃣ Self-Organizing Teams
Teams manage their own work
No micromanagement
1️⃣2️⃣ Continuous Improvement
Teams improve regularly
Learn from mistakes
Real-Time Example (Banking App)
Instead of building the full app:
Sprint-wise Development:
- Sprint 1: Login feature
- Sprint 2: Balance check
- Sprint 3: Fund transfer
- Sprint 4: Transaction history
After each sprint:
- Testing is done
- Client gives feedback
- Changes are implemented
Examples
| Feature | Agile | Traditional (Waterfall) |
|---|---|---|
| Flexibility | User Login | Login Validation |
| Delivery | User Login | Invalid Login |
| Changes | Password Reset | Forgot Password |
| Customer Involvement | Continuous | Limited |
Easy Way to Remember
Agile = Flexible + Fast + Feedback-based development
Scrum
By Content ITV
