aRustyDev Pragmatic Institute Framework (High relevance) distinguishes MRD (problem space: personas, their problems, market opportunity) from PRD (solution space: features, user stories, acceptance criteria). Its key insight: requirements should be written as problems to be solved for specific personas, not feature lists. This prevents over-engineering and keeps focus on product-market fit.
ISO 9001:2015 (Medium-High relevance) requires "documented information" but doesn't prescribe formats. The practical document hierarchy is: Quality Policy → Procedures → Work Instructions → Records. Even non-regulated startups benefit from lightweight quality management, and many B2B customers require ISO 9001 certification. The 2015 revision eliminated the mandatory Quality Manual and reduced prescriptiveness.
IEEE 29148:2018 (Medium relevance) is the current requirements engineering standard, superseding IEEE 830. It defines four specification types: StRS (Stakeholder Requirements), SyRS (System Requirements), SRS (Software Requirements), and OpsCon (Operational Concept). The templates provide excellent structural guidance even if a startup doesn't follow them formally. Its requirements classification aligns with BABOK's four-tier scheme: Business → Stakeholder → Solution (functional + non-functional) → Transition.
BABOK v3 (Medium relevance) doesn't prescribe document formats but defines a powerful requirements classification: Business Requirements → Stakeholder Requirements → Solution Requirements (subdivided into Functional and Non-Functional) → Transition Requirements. The 50+ elicitation techniques are directly useful.
IEEE 1016 (Medium relevance) defines the Software Design Description (SDD) structure: design views organized by viewpoints (architectural, logical, physical, process). The concept of multiple views of the same architecture — each serving different stakeholders — is valuable regardless of format.
ISO/IEC/IEEE 42010:2022 (Medium relevance) defines Architecture Description as composed of views, viewpoints, stakeholder concerns, and architecture decisions. The key concept: architecture documentation should be organized around stakeholder concerns, with each viewpoint defining conventions for one type of view. Practically, this means having a system context diagram, a decomposition view, and documented architecture decisions.
IEEE 15288:2023 and IEEE 12207:2017 (Medium relevance) define system and software lifecycle processes respectively, with IEEE 15289 serving as the companion standard that maps processes to the seven generic document types. The process checklists help ensure nothing critical is missed in engineering workflow design.
PMBOK 7th Edition (Medium relevance) defines artifacts in 9 categories including Strategy Artifacts (Project Charter, Roadmap), Log Artifacts (Risk Register, Backlog), Plan Artifacts (14 types of management plans), and Hierarchy Charts (WBS). A startup primarily needs: Project Charter (lightweight), Risk Register, and WBS for hardware development scheduling.
SAFe (Low-Medium relevance) defines a useful artifact hierarchy: Epic → Capability → Feature → Story and introduces Solution Intent as a living repository for both fixed requirements (compliance) and variable requirements (still being explored). These concepts are applicable even outside the full SAFe framework.
CMMI (Low relevance for startups) defines "typical work products" per process area but is designed for organizational maturity assessment in large enterprises. The underlying concepts (requirements management, configuration management, verification) are universally valuable even though formal CMMI appraisal provides no startup benefit.