Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 41 ยท Agile and Scrum

Agile Mindset and Principles

Understand agile project management: the four values, twelve principles, iterative delivery, the cost of change curve and how agile differs from predictive planning.

Traditional ("predictive") project management plans the whole project up front, then executes the plan. That works well when requirements are stable and the work is well understood, as in building a bridge. It works badly when the customer cannot describe what they want until they see something, or when the market moves faster than a year-long plan.

Agile is a family of approaches built for uncertainty. Instead of one big plan and one big delivery, you deliver small working increments often, learn from real feedback, and adjust. Scrum, Kanban, XP (Extreme Programming) and others are specific frameworks that put the agile mindset into practice.

The Agile Manifesto

In 2001, seventeen practitioners wrote four value statements. Each says "while there is value in the items on the right, we value the items on the left more":

We value more Over
Individuals and interactions Processes and tools
Working software Comprehensive documentation
Customer collaboration Contract negotiation
Responding to change Following a plan

It does not say the right-hand items are worthless. A contract and a plan still matter; they just must not stop you from delivering something useful.

The twelve principles in plain words

The manifesto adds twelve principles. Grouped by theme:

  • Deliver value early and often: satisfy the customer through early, continuous delivery; deliver working increments every few weeks.
  • Welcome change, even late, because it gives the customer a competitive advantage.
  • Collaborate daily: business people and developers work together; face-to-face conversation is the best way to convey information.
  • Trust motivated people, give them the environment and support they need.
  • Working software is the primary measure of progress.
  • Sustainable pace: sponsors, developers and users should be able to maintain a constant pace indefinitely.
  • Technical excellence and good design enhance agility.
  • Simplicity: maximize the amount of work not done.
  • Self-organizing teams produce the best architectures and designs.
  • Reflect and adjust regularly.

Predictive versus agile

Predictive Plan everything, then build.
Agile Plan a little, build a little, learn.
Delivery One big release versus many small ones.
Change Resisted versus expected.

Most real projects mix both.

1 / 2

Iterative and incremental delivery

Two ideas are easy to confuse.

  • Incremental: build the product in slices, each one usable (first login, then profile, then payments).
  • Iterative: build a rough version of something, then improve it with feedback (a sketch, then a better version).

Agile projects do both: each cycle (an iteration or sprint, usually 1 to 4 weeks) produces a potentially releasable increment, and the next cycle refines it using what users said. The shorter the cycle, the faster the feedback and the cheaper the correction.

flowchart LR
  P["Plan a little"] --> B["Build a slice"]
  B --> R["Review with users"]
  R --> L["Learn and adapt"]
  L --> P

The same loop repeats; each pass reduces uncertainty.

Why the feedback loop pays: cost of change

In a traditional project, a requirement mistake found in design costs little to fix, but found after release it can cost many times more. Agile tries to flatten this curve by finding mistakes sooner. Here is a toy model that compares them.

Python When do you find the mistake?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers are illustrative, not measured, but the shape of the argument is real: late discovery is expensive.

Simulating value delivery

The other argument for agile is that value arrives sooner. Compare a project that delivers everything at month 6 with one that delivers a sixth of the value each month.

Python Cumulative value over six months

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Both reach 100 at month 6, but the incremental plan has delivered (and possibly earned revenue from) value for five months. Ordering by value is a key habit: do the most valuable things first, and you can stop when the rest is not worth the cost.

Agile roles in general

Details vary by framework (see Scrum), but the roles are consistent:

  • Product owner / customer representative decides what is most valuable.
  • Cross-functional team has all the skills to deliver an increment.
  • Servant leader (Scrum Master, coach) removes obstacles and protects the process.

A project manager's role changes: less assigning tasks and tracking against a plan, more facilitating, removing blockers, managing stakeholders, budgets and risks around the team. See project leadership.

Where agile struggles

  • Fixed price, fixed scope, fixed date contracts: agile varies scope, so you need flexible contract forms (for example a fixed budget with a prioritized backlog).
  • Heavy regulation or safety-critical work needs more documentation and traceability; teams adapt agile rather than drop it.
  • Distributed or large organizations need scaling approaches (the next lessons and choosing a methodology cover this).
  • Teams without authority cannot be self-organizing if managers still dictate everything.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which pair matches the Agile Manifesto's values?

    The manifesto prefers customer collaboration to contract negotiation, though it still values contracts.
  2. 2. What is the difference between iterative and incremental?

    Increments add new pieces; iterations improve what exists. Agile teams usually do both.
  3. 3. Which is the primary measure of progress in agile?

    Principle: working software (a working product) is the primary measure of progress.
  4. 4. Agile projects have no planning.

    Agile replaces one big up-front plan with continuous, lightweight planning.

Summary

  • Agile suits uncertain, changing work; it delivers small increments and learns from feedback.
  • The manifesto has four values and twelve principles; both sides of each value matter, but the left side wins ties.
  • Incremental means usable slices, iterative means refining with feedback.
  • Early feedback lowers the cost of change; early delivery earns value sooner.
  • Agile reshapes the project manager's role and has limits in fixed-contract and regulated settings.

Next: Scrum Framework