New agile checklist

Complete the five sections; the composite maturity, per-section bands, and flags are computed as you go.

0 of 57 items answered

  1. You
  2. Teams
  3. Stakeholders
  4. Practices
  5. Summary
Step 1 — Respondent identification

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

Step 2 — Teams (25 items)

Concrete behaviours of the people doing the work — autonomy, collaboration, learning, finishing, and motivation. Answer Yes when the behaviour is reliably true today, No when it is not, and N/A when the item does not apply.

Section progress: 0 yes · 0 no · 0 n/a · 25 unanswered
t01

Teams have problems to solve rather than lists of tasks to perform.

t01
t02

Teams generally make decisions without a manager's approval.

t02
t03

Teams adopt appropriate practices and improve them over time.

t03
t04

Teams working on a common product actively coordinate.

t04
t05

Teams openly share new ideas and experiences with others.

t05
t06

Teams decide how to execute work.

t06
t07

Teams quickly act on stakeholder feedback to improve the product.

t07
t08

Teams rarely wait for work to be completed by others.

t08
t09

Teams make every effort to fully complete all planned work.

t09
t10

Teams monitor and manage their own performance.

t10
t11

Teams understand the benefits and challenges of agile.

t11
t12

Teams responsibly deliver high quality work.

t12
t13

Teams welcome rather than resist changing requirements.

t13
t14

Teams collaborate to finish items.

t14
t15

Teams admit challenges and mistakes.

t15
t16

Teams can work outside their specialties to achieve goals.

t16
t17

Teams seek to learn relevant, new skills.

t17
t18

Teams continue to learn and improve skills.

t18
t19

Teams actively seek ways to improve ways of working.

t19
t20

Teams choose and use various ways of communicating.

t20
t21

Teams have all received basic training on agile concepts.

t21
t22

Teams feel safe to express dissenting views.

t22
t23

Teams start work even when some open issues remain.

t23
t24

Teams are motivated by performing their work.

t24
t25

Teams take pride in their craft.

t25
Step 3 — Stakeholders (14 items)

Behaviours of sponsors, executives, and other people outside the team whose decisions shape what the team can do — trust, delegation, experimentation, communication.

Section progress: 0 yes · 0 no · 0 n/a · 14 unanswered
s01

Stakeholders know which factors determine priorities and deadlines.

s01
s02

Stakeholders accept plans that are expressed with ranges.

s02
s03

Stakeholders and the team accept that plans may need to change.

s03
s04

Stakeholders have frequent opportunities to evaluate the product.

s04
s05

Stakeholders champion agile values and agile principles.

s05
s06

Stakeholders see quality as a right that the team has and they respect it.

s06
s07

Stakeholders delegate authority to teams.

s07
s08

Stakeholders don't take authority back at the first sign of trouble.

s08
s09

Stakeholders support teams in experimenting.

s09
s10

Stakeholders don't punish an unsuccessful experiment.

s10
s11

Stakeholders communicate what they hope to achieve by becoming more agile.

s11
s12

Stakeholders actively encourage teams to learn new skills.

s12
s13

Stakeholders actively encourage teams to learn new ways of working.

s13
s14

Stakeholders develop people rather than manage their performance.

s14
Step 4 — Practices (18 items)

Operating practices that bind teams and stakeholders together — pace of decisions, focus on finished work, transparency, and scope discipline.

Section progress: 0 yes · 0 no · 0 n/a · 18 unanswered
p01

The early release of a good product is generally favoured over the later release of a perfect product.

p01
p02

An educated executive sponsor ensures the change agent is empowered to make decisions.

p02
p03

Decisions are made quickly, sometimes with incomplete knowledge.

p03
p04

Plans are based on data and experience.

p04
p05

Dependencies between teams are proactively identified and addressed.

p05
p06

People are assumed to have acted with good intentions even when something goes wrong.

p06
p07

Trust is reciprocal within the team and with stakeholders.

p07
p08

Although formal documentation may exist, it is supplemented by conversations to the extent possible.

p08
p09

As more is learned, plans are updated rather than remaining based on outdated information.

p09
p10

A non-punitive attitude leads to the team's willingness to experiment with new tools, technologies, and ways of working.

p10
p11

Outside groups that partner with the team are aware of how this new way of working may affect their interactions.

p11
p12

The organisation places a higher value on finished work than it does on the number of work items in process.

p12
p13

Quality is rarely, if ever, sacrificed to meet a deadline.

p13
p14

When problems arise between teams, everyone focuses on a solution rather than blame.

p14
p15

Change agents are in place to help support and guide the transition.

p15
p16

Agile practices are being implemented beyond the group in which agile began.

p16
p17

Most people are assigned to only one team.

p17
p18

People honour commitments and keep promises.

p18
Step 5 — Summary, maturity & action plan

Items answered: 0 / 57

Overall: — (insufficient data)

Composite maturity: INSUFFICIENT-DATA

Composite maturity: INSUFFICIENT DATA

Operational flags:

  • [MEDIUM] Only 0 of 57 items answered; the composite maturity is not reportable below 30. — Complete more items before relying on the maturity result.

Per-section bands

  • Teams (0/0 yes) — · UNANSWERED
  • Stakeholders (0/0 yes) — · UNANSWERED
  • Practices (0/0 yes) — · UNANSWERED
Fired coaching rules (3)
  • R-TEAMS-UNANSWERED — Teams section was not answered.
  • R-STAKEHOLDERS-UNANSWERED — Stakeholders section was not answered.
  • R-PRACTICES-UNANSWERED — Practices section 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.