New agile principles assessment

Complete all 14 sections; the composite maturity, per-principle bands, and operational flags are computed live and finalised on submit.

0 of 12 principles scored

  1. You
  2. P1 Customer
  3. P2 Change
  4. P3 Deliver
  5. P4 Collab
  6. P5 People
  7. P6 Conv
  8. P7 Software
  9. P8 Pace
  10. P9 Quality
  11. P10 Simple
  12. P11 Self-org
  13. P12 Reflect
  14. Summary

Step 1 — Respondent identification

Tell us who is completing this assessment and which team or organisation you are scoring. None of these fields affect the maturity calculation.

Step 2 — Principle 1: Customer satisfaction

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

We measure success by customer outcomes, not by milestones met. Working software reaches real users early and often, and feedback shapes the next iteration.

How well does this describe your team / organisation today?
principle-1

Click a score to select. Click the same score again to clear.

Step 3 — Principle 2: Welcome change

Changing requirements are welcomed, even late in development, to harness competitive advantage.

New information is treated as a gift, not a threat. The team adapts the plan when the world changes; change-control overhead is light.

How well does this describe your team / organisation today?
principle-2

Click a score to select. Click the same score again to clear.

Step 4 — Principle 3: Deliver frequently

We deliver working software frequently, in short cycles ranging from a couple of weeks to a couple of months, with a preference for the shorter timescale.

Releases are routine and low-drama. Cycle time is measured in days or low weeks, not quarters.

How well does this describe your team / organisation today?
principle-3

Click a score to select. Click the same score again to clear.

Step 5 — Principle 4: Daily collaboration

Business stakeholders and developers work together daily throughout the project.

Product, business, and engineering share context and decisions in real time. There is no over-the-wall handover.

How well does this describe your team / organisation today?
principle-4

Click a score to select. Click the same score again to clear.

Step 6 — Principle 5: Motivated individuals

We build projects around motivated individuals, give them the environment and support they need, and trust them to get the job done.

Hiring, environment, tooling, and management style are all set up to attract and keep motivated people, and to remove obstacles instead of adding them.

How well does this describe your team / organisation today?
principle-5

Click a score to select. Click the same score again to clear.

Step 7 — Principle 6: Face-to-face conversation

The most efficient and effective method of conveying information within and to a development team is rich, real-time conversation (face-to-face or its synchronous video equivalent).

Critical decisions are made in conversation, not in long async threads. Documentation captures decisions; it does not replace them.

How well does this describe your team / organisation today?
principle-6

Click a score to select. Click the same score again to clear.

Step 8 — Principle 7: Working software

Working software is the primary measure of progress.

We track shipped, working capability — not story points, hours, or the percentage of a Gantt chart that is green.

How well does this describe your team / organisation today?
principle-7

Click a score to select. Click the same score again to clear.

Step 9 — Principle 8: Sustainable development

Agile processes promote sustainable development. Sponsors, developers, and users should be able to maintain a constant pace indefinitely.

We do not rely on heroics, weekends, or crunch. Velocity is what the team can hold next quarter and the quarter after that.

How well does this describe your team / organisation today?
principle-8

Click a score to select. Click the same score again to clear.

Step 10 — Principle 9: Technical excellence

Continuous attention to technical excellence and good design enhances agility.

Refactoring, automated tests, code review, and infrastructure quality are part of the work, not a separate "later" project.

How well does this describe your team / organisation today?
principle-9

Click a score to select. Click the same score again to clear.

Step 11 — Principle 10: Simplicity

Simplicity — the art of maximising the amount of work not done — is essential.

We pull only what we are certain we need. Scope is actively trimmed; we do not gold-plate, over-engineer, or build for hypothetical futures.

How well does this describe your team / organisation today?
principle-10

Click a score to select. Click the same score again to clear.

Step 12 — Principle 11: Self-organising teams

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

Teams choose how to deliver outcomes. Architecture decisions sit with the people closest to the work; managers set context and remove blockers.

How well does this describe your team / organisation today?
principle-11

Click a score to select. Click the same score again to clear.

Step 13 — Principle 12: Regular reflection

At regular intervals the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

Retrospectives happen on a schedule, produce concrete experiments, and the team verifies whether each experiment worked.

How well does this describe your team / organisation today?
principle-12

Click a score to select. Click the same score again to clear.

Step 14 — Summary, maturity & action plan

Principles answered: 0 / 12

Unweighted mean: — (insufficient data)

Composite maturity: INSUFFICIENT-DATA

Composite maturity: INSUFFICIENT DATA

Operational flags:

  • [MEDIUM] Fewer than six principles received a score; the composite maturity is not reportable. — Complete the remaining principles before relying on the maturity result.

Per-principle bands

  • P1 — Customer satisfaction — · —
  • P2 — Welcome change — · —
  • P3 — Deliver frequently — · —
  • P4 — Daily collaboration — · —
  • P5 — Motivated individuals — · —
  • P6 — Face-to-face conversation — · —
  • P7 — Working software — · —
  • P8 — Sustainable development — · —
  • P9 — Technical excellence — · —
  • P10 — Simplicity — · —
  • P11 — Self-organising teams — · —
  • P12 — Regular reflection — · —
Customise weights

Weight each principle between 0.5 (half-weight) and 2.0 (double-weight). Default is 1.0. Weights only affect the weighted mean and the composite maturity; the unweighted mean remains visible above.

  • P1 — Customer satisfaction
  • P2 — Welcome change
  • P3 — Deliver frequently
  • P4 — Daily collaboration
  • P5 — Motivated individuals
  • P6 — Face-to-face conversation
  • P7 — Working software
  • P8 — Sustainable development
  • P9 — Technical excellence
  • P10 — Simplicity
  • P11 — Self-organising teams
  • P12 — Regular reflection
Fired coaching rules (12)
  • R-P01-UNANSWERED — P1 UNANSWERED: Principle 1 (Customer satisfaction) was not answered.
  • R-P02-UNANSWERED — P2 UNANSWERED: Principle 2 (Welcome change) was not answered.
  • R-P03-UNANSWERED — P3 UNANSWERED: Principle 3 (Deliver frequently) was not answered.
  • R-P04-UNANSWERED — P4 UNANSWERED: Principle 4 (Daily collaboration) was not answered.
  • R-P05-UNANSWERED — P5 UNANSWERED: Principle 5 (Motivated individuals) was not answered.
  • R-P06-UNANSWERED — P6 UNANSWERED: Principle 6 (Face-to-face conversation) was not answered.
  • R-P07-UNANSWERED — P7 UNANSWERED: Principle 7 (Working software) was not answered.
  • R-P08-UNANSWERED — P8 UNANSWERED: Principle 8 (Sustainable development) was not answered.
  • R-P09-UNANSWERED — P9 UNANSWERED: Principle 9 (Technical excellence) was not answered.
  • R-P10-UNANSWERED — P10 UNANSWERED: Principle 10 (Simplicity) was not answered.
  • R-P11-UNANSWERED — P11 UNANSWERED: Principle 11 (Self-organising teams) was not answered.
  • R-P12-UNANSWERED — P12 UNANSWERED: Principle 12 (Regular reflection) was not answered.

The maturity result is intended to seed coaching conversations and retrospective items. It is a self-report; cross-team aggregation should be done before drawing organisation-wide conclusions.