James Robertson is a software consultant and member of the atlantic-systems-guild, known primarily for his work in requirements engineering. He is a co-author of adrenaline-junkies-and-template-zombies and works closely with his partner suzanne-robertson on requirements methodology.
Requirements engineering work
James Robertson's primary intellectual contribution is in the domain of requirements engineering — the discipline of discovering, articulating, and validating what a software system must do before construction begins. Together with suzanne-robertson, he developed the Volere requirements framework, a structured methodology for requirements discovery and specification that has been widely adopted in enterprise software development. Their jointly authored work on requirements methodology represents a sustained effort to bring the same rigor to the front end of software development that structured analysis brought to system modeling.
This positions Robertson within the structured methods tradition that shaped DeMarco's early career: the structured-methods-era project of making the analysis and specification phases of development disciplined and teachable, rather than tacit and ad hoc.
Atlantic Systems Guild
Robertson's membership in the atlantic-systems-guild connects him to the broader DeMarco/Lister intellectual network. The Guild's model — a collaborative consulting group in which members share intellectual resources and reinforce each other's reputations — allowed Robertson's requirements work to exist in the same institutional context as peopleware's team-dynamics arguments and steve-mcmenamin's essential systems analysis. The cross-pollination within the Guild meant that requirements engineering, team dynamics, and organizational behavior were treated as related rather than separate concerns.
Adrenaline Junkies
adrenaline-junkies-and-template-zombies (2008), co-authored with DeMarco, timothy-lister, suzanne-robertson, steve-mcmenamin, peter-hruschka, and larry-constantine, draws on the Guild's collective consulting experience. Robertson's contribution reflects his practitioner observation of the patterns — both productive and dysfunctional — that recur across software projects. The book's premise — that project behavior follows identifiable patterns regardless of methodology — resonates with Robertson's requirements work, which similarly aims to surface the underlying structure beneath the surface variety of software projects.