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 template. 

This checklist classifies requirements into expected features, ecosystem features, and infrastructure features. For example: 

1. Basic features for users: security, privacy, access control, accessibility, localization, analytics, configurability, etc. 
2. Ecosystem features: compliance, enterprise policy, interoperability, portability, etc.
3. 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.