Agile is an iterative and incremental software development methodology focused on delivering value quickly, responding to change, and continuously improving through collaboration.
| Topic | Details |
|---|---|
| Definition | Iterative and incremental development methodology. |
| Goal | Deliver value quickly and continuously. |
| Delivery Style | Small and frequent releases. |
| Team Structure | Cross-functional and self-organizing teams. |
| Documentation | Just enough documentation. |
| Customer Involvement | Continuous involvement throughout development. |
| Value | Description |
|---|---|
| Individuals and Interactions | More important than processes and tools. |
| Working Software | More important than comprehensive documentation. |
| Customer Collaboration | More important than contract negotiation. |
| Responding to Change | More important than following a plan. |
| Principle | Meaning |
|---|---|
| Customer Satisfaction | Deliver valuable software early and continuously. |
| Welcome Change | Even late requirement changes are accepted. |
| Frequent Delivery | Deliver software every few weeks. |
| Business Collaboration | Developers and business work together daily. |
| Technical Excellence | Improves agility and maintainability. |
| Retrospectives | Continuously improve processes. |
| Role | Responsibility |
|---|---|
| Product Owner | Owns product vision and prioritizes backlog. |
| Scrum Master | Facilitates Scrum and removes impediments. |
| Development Team | Designs, develops, tests, and deploys. |
| Stakeholders | Business users, customers, management. |
| Component | Description |
|---|---|
| Sprint | Time-boxed iteration (1-4 weeks). |
| Product Backlog | Prioritized list of requirements. |
| Sprint Backlog | Selected work for current sprint. |
| Increment | Potentially releasable software. |
| Definition of Done | Completion criteria. |
| Definition of Ready | Readiness criteria before development. |
| Event | Duration | Purpose |
|---|---|---|
| Sprint Planning | 2-8 Hours | Plan sprint work. |
| Daily Scrum | 15 Minutes | Daily synchronization. |
| Sprint Review | 1-4 Hours | Demo completed work. |
| Sprint Retrospective | 1-3 Hours | Continuous improvement. |
| Letter | Meaning |
|---|---|
| I | Independent |
| N | Negotiable |
| V | Valuable |
| E | Estimable |
| S | Small |
| T | Testable |
| Story Point | Complexity |
|---|---|
| 1 | Very Small |
| 2 | Small |
| 3 | Medium |
| 5 | Moderate |
| 8 | Complex |
| 13 | Very Complex |
| 21 | Epic |
| Aspect | Velocity | Capacity |
|---|---|---|
| Meaning | Delivered effort | Available effort |
| Unit | Story Points | Hours/Days |
| Purpose | Forecasting | Sprint Planning |
| Feature | Scrum | Kanban |
|---|---|---|
| Sprint | Yes | No |
| Planning | Sprint Based | Continuous |
| Release | End of Sprint | Anytime |
| WIP Limit | Optional | Mandatory |
| Question | Answer |
|---|---|
| What is Agile? | Iterative and incremental development methodology. |
| What is Scrum? | Agile framework using sprints. |
| What is Velocity? | Story points completed in a sprint. |
| What is Sprint? | Time-boxed iteration. |
| What is DoD? | Completion criteria. |
| What is DoR? | Readiness criteria. |
Agile is not just a process or framework; it is a mindset focused on continuous learning, customer value, collaboration, adaptability, and incremental delivery.
Agile mindset focuses on delivering customer value continuously, embracing change, learning from feedback, and improving processes through collaboration and iterative delivery.
| Value | Description |
|---|---|
| Commitment | Commit to achieving sprint goals. |
| Courage | Address difficult problems openly. |
| Focus | Focus on sprint objectives. |
| Openness | Be transparent about progress and challenges. |
| Respect | Respect team members and stakeholders. |
Backlog Refinement is the continuous process of reviewing, clarifying, estimating, and prioritizing backlog items.
| Category | Meaning |
|---|---|
| Must Have | Mandatory requirement |
| Should Have | Important but not critical |
| Could Have | Nice-to-have feature |
| Won't Have | Not included currently |
| Letter | Meaning |
|---|---|
| R | Responsible |
| A | Accountable |
| C | Consulted |
| I | Informed |
| Letter | Meaning |
|---|---|
| R | Responsible |
| A | Accountable |
| C | Consulted |
| I | Informed |
| Framework | Purpose |
|---|---|
| SAFe | Enterprise Agile Scaling |
| LeSS | Large Scale Scrum |
| Nexus | Multi-Team Scrum Coordination |
| Scrum@Scale | Scaling Scrum Organization-Wide |
Release Planning determines what features will be delivered and when they will be released based on team velocity, business priorities, and dependencies.
| Aspect | Agile | Waterfall |
|---|---|---|
| Delivery | Incremental | Single Release |
| Requirements | Flexible | Fixed |
| Testing | Continuous | End Phase |
| Customer Feedback | Frequent | Limited |
A Scrum Master acts as a Servant Leader by helping the team succeed, removing impediments, facilitating collaboration, and enabling continuous improvement rather than directing work.
Agile Mindset is a way of thinking that focuses on delivering customer value, embracing change, continuous learning, collaboration, adaptability, and incremental delivery rather than strictly following processes and plans.
Interview Answer:Agile Mindset is about continuously delivering value to customers, responding to changing requirements, collaborating effectively, and improving through feedback and iteration.
Scrum is built on five core values:
Product Backlog Refinement (Backlog Grooming) is the process of continuously reviewing, clarifying, estimating, prioritizing, and breaking down backlog items.
Activities:Backlog items are prioritized based on business value, customer impact, risk, dependencies, urgency, and technical considerations.
Common Techniques:| Category | Meaning |
|---|---|
| Must Have | Critical requirement |
| Should Have | Important but not mandatory |
| Could Have | Nice-to-have feature |
| Won't Have | Not included currently |
Technical Debt is the future cost incurred when quick or suboptimal solutions are implemented instead of the best long-term approach.
Examples:A Spike is a time-boxed research activity used to investigate technical uncertainties or gather information before implementation.
Example:Researching Kafka integration before developing a messaging solution.
Release Planning determines what features will be delivered and when, based on team velocity, capacity, business priorities, and dependencies.
Inputs:Velocity is the total number of story points completed in a sprint.
| Sprint | Completed Story Points |
|---|---|
| Sprint 1 | 30 |
| Sprint 2 | 35 |
| Sprint 3 | 40 |
Average Velocity = (30 + 35 + 40) / 3 = 35 Story Points
Team Capacity is the amount of work a team can realistically complete during a sprint based on availability.
4 Team Members × 10 Days × 8 Hours = 320 Hours
| Aspect | Agile | Waterfall |
|---|---|---|
| Delivery | Incremental | Single Release |
| Requirements | Flexible | Fixed |
| Testing | Continuous | End Phase |
| Customer Feedback | Frequent | Limited |
Scope creep occurs when additional requirements are added without proper evaluation.
Approach:Dependencies are identified during backlog refinement and sprint planning. Teams coordinate early to minimize delays.
Best Practices:Servant Leadership is a leadership style where leaders focus on supporting and enabling their teams rather than directing them.
Scrum Master Responsibilities:SAFe (Scaled Agile Framework) is a framework used to scale Agile practices across multiple teams and large enterprises.
Key Benefits:Backlog Grooming (Refinement) is the process of continuously updating, clarifying, prioritizing, and estimating backlog items.
Goals:Conflicts are resolved through open communication, active listening, collaboration, and focusing on team goals rather than individual opinions.
Approach:| Metric | Purpose |
|---|---|
| Velocity | Team throughput |
| Burndown Chart | Remaining sprint work |
| Burnup Chart | Completed work |
| Lead Time | Request to delivery duration |
| Cycle Time | Development start to completion |
| Defect Density | Quality measurement |
| Escaped Defects | Production defects |
| Sprint Predictability | Planned vs completed work |
I typically track Velocity, Burndown, Lead Time, Cycle Time, Defect Density, Escaped Defects, Sprint Predictability, and Customer Satisfaction metrics to measure team performance, delivery efficiency, and product quality.