NOT List

⏱ 3 min  ·  📅 2026

The NOT list is a technique for defining the scope of a project during the inception phase. It explicitly sets out, for everyone involved, which features or aspects are not part of the scope, which are part of it, and which are pending a decision. It was described by Jonathan Rasmusson in The Agile Samurai (2010).

Purpose

The NOT list offers a clear first approximation of the size and scope of the work. It establishes a reference point and shared expectations between the team and the stakeholders before development begins.

The value of the list does not lie only in the YESes: the NOs are equally important because they manage expectations that would otherwise lead to costly misunderstandings later on. Knowing explicitly that something is not going to be done in this phase prevents confusion and wasted work.

How to apply it

A board or work area is used to display the scope items in three clearly differentiated zones:

• YES: features, platforms, environments, or aspects that are included in the scope of the project or of the current phase.
• NO: features or aspects that are explicitly out of scope.
• ?: items still pending a decision: there are unanswered questions or missing information needed to determine whether or not they are included.

Items in the "?" zone have a deadline: each one needs an owner and an agreed time to resolve the uncertainty.

When to use it

• In the project inception or kick-off session, to align the team and stakeholders on scope from day one.
• When the customer or stakeholders have implicit expectations about what will be built that could lead to conflicts later on.
• As a complement to the Agile inception deck or Lean inception.

Common mistake

Leaving the "?" zone unresolved. Items pending a decision are the most delicate part of the list: if no one resolves them, they become a permanent source of ambiguity. Every item in "?" must leave the session with a name and a committed date for the decision. If that is not possible, it is a sign that a necessary conversation is not taking place.

References

• Rasmusson, Jonathan. (2010). The Agile Samurai: How Agile Masters Deliver Great Software. The Pragmatic Bookshelf.

See also

Inception Agile inception deck Lean inception Product vision Minimum viable product Commitment prioritization

Want to grow in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.

Search calls

Agile Club