Skip to content
Is2Be

Context requirements

Turns the voice of the customer, regulation and context into verifiable requirements and CTQs.

Command: /ef:context-requirements · Methodology: Is2Be Process · Phase: Phase 3 · Analysis

When to use it

Section titled “When to use it”

The core of Phase 3 in greenfield (mode B); in other modes, to shape the voice of the customer.

It’s working if

Section titled “It’s working if”
  • Every requirement has a MoSCoW priority and a verification criterion.
  • Conflicts between requirements go to a PDR rather than being settled quietly.
  • Volume assumptions state where they come from.

Where it fits

Section titled “Where it fits”

Requirements

Section titled “Requirements”

  • Your AI connected to the service with your licence key (how to connect).

  • The project set up once with /ef:setup.

  • The outputs of the previous steps (see Where it fits).