Making Cross-Functional Requirements (CFRs) a first-class citizen at AvidXchange
summary
AvidXchange defines CFRs with 11 categories, 30 subcategories and prioritizes them by product impact, using examples like perishable delivery within four hours and Amazon’s 1.6M orders/day to justify scale targets. CFRs are documented with templates, map CFRs to epics and acceptance criteria, and require explicit testing and verification. Adoption is incremental: pilot initiatives, elicitation question sets to drive conversations, and tradeoffs shown (five-nine vs two-nine availability) tied to cost and complexity.
AI-written summary · about
chapters (4)
related talks
46mCreating Effective and Objective Architectural Decision Records (ADRs)
35mUsing CNCF Best Practices for Software Supply Chain to Guide and Enha...
01h 01mArchitecting for rapid, frequent, reliable delivery of software.
38mCustom Resource Definitions: Let's Talk About Versioning and Releases
31mLightweight Software Architecture
13mBuilding a Unicorn
40mPractices from trenches for embracing evolutionary architecture in wild
37mAPI Tour - Get to know the APIs we shipped in the last 6 months