Yasin Avci

Yasin Avci

Full-Stack Developer

Paris, France

Contact me
Back to articles
MethodologyAgileTeam

The Agile Method: Much More Than a Buzzword

Daily meetings, sprint planning, retrospectives... How Agile concretely transforms the way to deliver quality products.

March 15, 20242 min read

When I started development, Agile seemed like a set of useless meetings. Today, after working in teams of 3 to 15 people, I couldn't do without it.

What Agile Is NOT

Let's start by deconstructing some myths:

  • It's not "no documentation" — it's useful documentation, at the right time
  • It's not "we change everything all the time" — it's adapting intelligently to feedback
  • It's not "no planning" — it's planning at a scale that makes sense

The Rituals That Change Everything

The Daily: 15 Minutes That Save Hours

An effective daily answers three questions:

  1. What did I do yesterday?
  2. What am I doing today?
  3. What's blocking me?

The key: stay factual. No technical discussions, no problem solving. Just a quick sync.

Sprint Planning: Defining the "What" and "How"

This is where the team commits to a realistic scope. Common mistakes:

  • Underestimating complexity (always add 20% margin)
  • Forgetting dependencies between tasks
  • Not challenging vague specs

The Retrospective: The Engine of Continuous Improvement

The retrospective is often neglected, yet it's where the team grows. Simple format:

  • What worked well (to keep)
  • What can be improved (concrete actions)
  • Ideas to explore (for the next sprint)

Agile in Practice: A Concrete Example

On a recent project, we had 3 weeks to deliver a major feature. Rather than developing everything in isolation for 2 weeks then integrating in a panic, we:

  1. Broke it into deliverable increments — each 1-week sprint produced something testable
  2. Integrated continuously — daily merge requests, no branches hanging around
  3. Adjusted along the way — sprint 1 feedback influenced sprint 2

Result: on-time delivery, fewer bugs, and a client who could validate progressively.

When Agile Doesn't Work

Let's be honest: Agile isn't a miracle solution. It fails when:

  • The client isn't available to give feedback
  • The team doesn't have autonomy to make decisions
  • Specs are set in stone from day 1

In these cases, a more traditional approach may be more suitable.

Going Further

Agile is learned by practicing it. If you're starting, begin with:

  • A daily standup (even with 2 people)
  • Short sprints (1-2 weeks max)
  • An honest retrospective at the end of each sprint

The rest will come naturally.