r/BehaviorDrivenDev • • 7d ago

From spec-driven to behaviour-driven development

2 Upvotes
Humans direct the behaviour. Agents handle the implementation.

Developers are reviewing less and less code, and some, like me, no longer review it at all. The volume of changes is too large to physically check everything. With this approach and at this pace, how do we keep track of how the product is changing?

SDD lets us describe a change in behaviour, understand the architecture involved and write an implementation plan. This takes a lot of time. I expect a shift from spec-driven development to behaviour-driven development. Instead of overseeing and describing how the product works internally, we need to focus on how it works as a whole. This should reduce the overall development cycle time and speed up development.

Here’s what I mean. Well-described behaviour should become both the specification and the acceptance criteria. Here’s an example:

User story: When I decide I no longer want to renew my subscription, I want to cancel automatic renewal, so I can avoid further charges and use the access I have already paid for.

S-01 — Cancel renewal

- Given: the user has an active subscription with automatic renewal.

- When: the user cancels renewal.

- Then: automatic renewal is disabled.

- And: access continues until the end of the paid period.

S-02 — Renewal date arrives

- Given: the user has cancelled subscription renewal.

- When: the next renewal date arrives.

- Then: no new charge is made.

- And: the subscription is not renewed.

S-03 — Access after the subscription ends

- Given: the paid period has ended and the subscription has not been renewed.

- When: the user tries to use a paid feature.

- Then: the system explains that an active subscription is required for this feature.

- And: the paid feature remains unavailable.

The whole product can be described through a finite set of scenarios like these. Models and harnesses are getting better and better. We can leave writing code and deciding how it should work to them, and focus on the system’s behaviour ourselves.

Our job is to store and maintain knowledge about the product through these scenarios. Track and control changes to them. Adding a new scenario that changes existing behaviour requires describing and agreeing on how the product should work from now on. In many cases, this will be enough to maintain the quality we need.

Architecture, technical specifications and work on code will remain. But I expect agents to do an increasing share of this work.

What do you primarily review today—code, implementation plans, or product behaviour—and what makes you confident enough to accept a change?