Scrum Master - Page -1

 

Module 1: Agile Fundamentals

1. What is Agile?

Agile is a software development methodology that focuses on delivering working software in small, incremental releases instead of delivering the entire product at the end of the project.

The goal of Agile is to:

  • Deliver value to customers faster

  • Adapt quickly to changing requirements

  • Encourage collaboration between business and development teams

  • Continuously improve the product

Key Characteristics

  • Customer collaboration

  • Frequent software releases

  • Continuous feedback

  • Cross-functional teams

  • Flexibility to changing requirements

Example

Instead of spending 12 months building an entire e-commerce website, an Agile team might deliver:

  • Sprint 1: User Login

  • Sprint 2: Product Catalog

  • Sprint 3: Shopping Cart

  • Sprint 4: Payment Gateway

Customers begin using the product early while the team continues adding features.


2. Agile Manifesto

The Agile Manifesto was created in 2001 by a group of software professionals to improve software development practices.

It is based on 4 Core Values and 12 Principles.

Four Agile Values

1. Individuals and interactions over processes and tools

People and communication are more important than rigid processes or software tools.

Example:
A quick discussion between developers often solves a problem faster than following lengthy documentation.


2. Working software over comprehensive documentation

Documentation is valuable, but delivering a working product provides the most value.

Example:
A functioning login page is more valuable than a 100-page design document.


3. Customer collaboration over contract negotiation

Customers should work closely with the development team throughout the project.

Example:
The Product Owner regularly reviews completed work and provides feedback after every sprint.


4. Responding to change over following a plan

Plans are important, but adapting to changing business needs is even more important.

Example:
If customers request a new payment option, the team can prioritize it in the next sprint instead of waiting until the project ends.


3. The 12 Agile Principles

1. Satisfy the customer through early and continuous delivery.

Deliver working software frequently so customers receive value sooner.


2. Welcome changing requirements.

Even late in development, changes should be accepted if they improve the product.


3. Deliver working software frequently.

Release software every few weeks rather than every few months.


4. Business and developers work together daily.

Close collaboration reduces misunderstandings and speeds up decision-making.


5. Build projects around motivated individuals.

Provide the right environment, trust the team, and support them.


6. Face-to-face communication is the most effective.

Direct conversations reduce misunderstandings. In distributed teams, video calls are often the closest alternative.


7. Working software is the primary measure of progress.

Progress is measured by completed, usable features rather than documents or hours worked.


8. Maintain a sustainable pace.

Teams should avoid burnout by working at a pace they can sustain over time.


9. Continuous attention to technical excellence.

High-quality code and sound design make future changes easier.


10. Simplicity is essential.

Do only the work that is needed. Avoid unnecessary complexity.


11. Self-organizing teams produce the best solutions.

Teams decide how to accomplish their work instead of being directed step by step.


12. Reflect and improve regularly.

At the end of each sprint, the team discusses what went well, what didn't, and how to improve.


4. Waterfall vs Agile

Waterfall

Waterfall is a linear software development model where each phase is completed before the next begins.

Flow:

Requirements
→ Design
→ Development
→ Testing
→ Deployment
→ Maintenance

Characteristics

  • Sequential process

  • Fixed requirements

  • Testing occurs near the end

  • Difficult to accommodate changes

  • Customer feedback arrives late

Advantages

  • Clear documentation

  • Predictable milestones

  • Suitable for projects with stable requirements

Disadvantages

  • High cost of change

  • Late discovery of issues

  • Long time before customers see results


Agile

Agile delivers software in small increments through repeated cycles called sprints.

Flow:

Plan
→ Develop
→ Test
→ Review
→ Deploy
→ Repeat

Characteristics

  • Iterative development

  • Frequent releases

  • Continuous testing

  • Regular customer feedback

  • Flexible planning

Advantages

  • Faster delivery of value

  • Easier to respond to change

  • Lower project risk

  • Higher customer satisfaction

Disadvantages

  • Requires active stakeholder involvement

  • Needs experienced, collaborative teams

  • Scope can evolve during the project


Waterfall vs Agile Comparison

WaterfallAgile
SequentialIterative
Fixed requirementsFlexible requirements
One major releaseFrequent releases
Testing near the endContinuous testing
Customer involvement is limitedCustomer involvement is continuous
Changes are expensiveChanges are expected and managed

5. Agile Lifecycle

The Agile lifecycle repeats through short development cycles called Sprints.

Typical lifecycle:

Product Backlog
→ Sprint Planning
→ Sprint
→ Daily Scrum
→ Sprint Review
→ Sprint Retrospective
→ Next Sprint

Product Backlog

A prioritized list of features, enhancements, bugs, and technical work maintained by the Product Owner.


Sprint Planning

The Scrum Team selects backlog items for the upcoming sprint and defines a Sprint Goal.


Sprint

A fixed-length period (commonly 1–4 weeks) during which the team designs, develops, tests, and completes selected work.


Daily Scrum

A short daily meeting (up to 15 minutes) where Developers coordinate work, discuss progress, and identify impediments.


Sprint Review

The team demonstrates the completed work to stakeholders and gathers feedback.


Sprint Retrospective

The Scrum Team reflects on how they worked together and identifies improvements for the next sprint.


6. Incremental vs Iterative Development

Although often used together, these terms describe different ideas.

Incremental Development

The product grows by adding new, complete pieces of functionality over time.

Example:

Release 1:

  • Login

Release 2:

  • Login

  • Product Catalog

Release 3:

  • Login

  • Product Catalog

  • Shopping Cart

Each release adds additional features while preserving previous functionality.


Iterative Development

The team repeatedly improves existing functionality based on learning and feedback.

Example:

Iteration 1:

  • Basic Login

Iteration 2:

  • Add password validation

Iteration 3:

  • Add multi-factor authentication

Iteration 4:

  • Improve user interface and performance

The same feature evolves and becomes better over multiple iterations.


Key Difference

IncrementalIterative
Adds new functionalityImproves existing functionality
Product expands over timeProduct is refined over time
Focus on feature growthFocus on feature improvement

Real-world Agile Example

An online shopping application may use both approaches:

Sprint 1

  • Build Login (Increment)

Sprint 2

  • Improve Login with password reset (Iteration)

  • Build Product Catalog (Increment)

Sprint 3

  • Improve Product Catalog with search (Iteration)

  • Build Shopping Cart (Increment)

This combination of incremental delivery and iterative improvement is one of the core strengths of Agile.

Comments

Popular posts from this blog

Scrum-Master

Scrum Master - Syllabus