Agile Development Perspective

In response to the limitations of traditional plan-and-document approaches, the agile philosophy emerged in 2001 with the Agile Manifesto. Agile prioritizes flexibility, collaboration, and rapid delivery over rigid processes and comprehensive documentation.

The Four Key Principles

The Agile Manifesto establishes four fundamental values that guide all agile practices:

1. Individuals and Interactions Over Processes and Tools

What It Means:

• People matter more than procedures
• Communication is more valuable than documentation
• Teams should adapt processes to their needs, not the reverse

In Practice:

• Daily standups to synchronize the team
• Face-to-face conversations over lengthy emails
• Flexible team structures that evolve with project needs
• Tools that serve the team, not vice versa

"The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."

2. Working Software Over Comprehensive Documentation

What It Means:

• Deliverable software is the primary measure of progress
• Documentation supports development, not the reverse
• Just enough documentation to be useful

In Practice:

• Working software demonstrated every iteration
• Self-documenting code through clear naming and structure
• Minimal documentation focused on essential information
• Documentation evolves with the software

"Working software is the primary measure of progress."

3. Customer Collaboration Over Contract Negotiation

What It Means:

• Customers are partners, not adversaries
• Requirements emerge through ongoing dialogue
• Contracts should enable collaboration, not restrict it

In Practice:

• Customer representatives embedded or regularly available
• Continuous feedback loops with stakeholders
• Flexible contracts that accommodate change
• Shared ownership of outcomes

"The best architectures, requirements, and designs emerge from self-organizing teams."

4. Responding to Change Over Following a Plan

What It Means:

• Change is expected and embraced
• Plans are living documents, not rigid contracts
• Adaptability is a competitive advantage

In Practice:

• Regular reassessment of priorities
• Short iterations enable quick pivots
• Technical practices that support change (refactoring, testing)
• Strategic alignment maintained through frequent validation

"Welcome changing requirements, even late in development."

Incremental Development

Agile development delivers software in small, usable increments rather than one large release:

Characteristics of Incremental Delivery

Benefits of Incremental Development

• Early Value Delivery: Users benefit from partial functionality sooner
• Risk Mitigation: Problems are caught and corrected early
• Flexibility: Direction can change based on learning
• Motivation: Visible progress boosts team morale
• Learning: Each iteration provides data for improvement

Agile Approaches

Several frameworks and methodologies embody agile principles:

Extreme Programming (XP)

XP focuses on technical excellence and close customer collaboration:

Core Practices:

When XP Works Best:

• Small to medium-sized teams
• Projects with rapidly changing requirements
• Teams prioritizing technical quality
• Projects where customer involvement is possible

Scrum

Scrum provides a structured framework for managing iterative work:

Scrum Roles:

Scrum Events:

• Sprint Planning: Define what will be delivered in this iteration
• Daily Standup: 15-minute synchronization meeting
• Sprint Review: Demonstrate working software to stakeholders
• Sprint Retrospective: Team reflects and improves their process

When Scrum Works Best:

• Medium to large teams
• Complex projects with evolving requirements
• Organizations transitioning to agile
• Projects requiring regular stakeholder feedback

Kanban

Kanban uses a visual system to manage workflow:

Kanban Principles:

Kanban Benefits:

• No prescribed roles or ceremonies
• Continuous delivery model
• Visualizes bottlenecks
• Highly flexible and adaptable

When Kanban Works Best:

• Support and maintenance teams
• Continuous flow environments
• Teams that cannot work in sprints
• Organizations with multiple work types

Agile vs. Plan and Document: Choosing the Right Approach

Decision Factors

When to Choose Plan and Document

Use Waterfall or similar when:

• Requirements are clearly understood and unlikely to change
• The technology and domain are well-understood
• Regulatory or contractual requirements mandate extensive documentation
• The project is small with a fixed scope
• Long-term planning is required for budgeting
• The team is inexperienced with agile practices

When to Choose Agile

Use Agile when:

• Requirements are not fully understood at the start
• Changes are expected and welcomed
• Rapid delivery of value is prioritized
• Customer collaboration is possible
• The project is complex or innovative
• The team is experienced and self-organizing
• Continuous feedback is valued

Sommerville's Guidance: When to Use Which Approach

Based on software engineering principles (Sommerville, Addison Wesley):

Quick Decision Guide

Project Context Matrix

• Incremental Development: Delivering value in small, usable increments with rapid feedback

• Agile Approaches:

  • XP: Technical excellence through practices like TDD and pair programming
  • Scrum: Structured framework with sprints, roles, and events
  • Kanban: Visual workflow management with continuous delivery

• Choosing the Right Approach: Consider requirements stability, project size, team experience, and organizational context

Modern software development often employs hybrid approaches, taking the best elements from both agile and plan-and-document methodologies to suit specific project needs.