Stop 07 · Agile, Execution & DeliveryTopics · 1/12

Agile Principles & the Agile Manifesto

In short

In 2001, a group of software people wrote four short lines that changed how most teams work. Knowing what they actually say helps you spot fake "agile" quickly.

A set of values prioritizing working software, customer collaboration, and responding to change over rigid upfront planning — the philosophy behind Scrum, Kanban and most modern PM workflows.

The purple blob drives an auto-rickshaw through a side lane around a traffic jam.

Think of it like this

The auto driver who reroutes

A bus follows its fixed route even if the road ahead is jammed. A good auto driver sees the jam, takes the side lane and still drops you on time. Agile teams plan, but they change course when reality changes.

Watch it happen

The four values: left side valued more

People > process

Working software > docs

Customer collab > contracts

Responding > the plan

1/5The manifesto lists four pairs. Both sides matter, but the left side matters more.

The big ideas

What you need to know

Ship in small pieces

Deliver working software often, in weeks rather than months, so feedback arrives early.

Talk face to face

Direct conversation is the fastest way to share understanding inside a team.

Welcome change

Late changes are allowed if they help the customer. Short cycles make that affordable.

Not anti-planning

The manifesto values plans and docs. It just values the left side more.

Save yourself the pain

Common mistakes

Oops

Saying "we're agile, so we don't need documentation".

Do this instead

The manifesto says working software is valued more, not that docs are useless. Write what helps.

Oops

Calling any process with standups "agile".

Do this instead

Check the values: are you shipping often, talking to users and adapting?

Your mission

Read the source

~15 min

Quick check

According to the Agile Manifesto, how should teams treat a plan?

Go deeper

1Read the original 12 principles behind the Agile Manifesto (short, worth reading fully).
2Identify which principle your current or most recent team violates most often.
3Learn that 'Agile' is a mindset — Scrum and Kanban are just two implementations of it.