Enterprise features/products need to support requirements that may not be directly related to the feature. These are known by many names: non-functional requirements, technical requirements, minimum requirements, etc. A new feature may impact other product areas, products, or product lines. Such features are also frequently found in RFPs issued by enterprise companies.
I call these enterprise product requirements. These requirements are hard to memorize and easy to overlook, so a checklist is useful.
Here’s the enterprise product requirements checklist.
This checklist classifies requirements by personas: end-users and enterprise personas such as Admin/IT, Infosec, Privacy, Legal/GRC, Business/GTM, Ecosystem/Platform, and Infrastructure/Engineering.
Broadly speaking, these requirements can be classified as basic features for users, enterprise ecosystem features, and infrastructure features.
- Basic features for users: security, privacy, access control, accessibility, localization, etc.
- Enterprise ecosystem features: analytics, configurability, compliance, enterprise policy, interoperability, portability, etc.
- Infrastructure features: performance, availability, scalability, cost, maintainability, observability, etc.
Also see templates for product opportunity brief and pre-release notes with FAQ.
PS: Typically I write about building products. I write to pay it forward and to clarify my thinking.