2 ms·
Where I work we no longer use the term 'non-functional requirements', having replaced it with the term 'operational requirements.' We discovered the business wa
by taylodl 11y ago
Where I work we no longer use the term 'non-functional requirements', having replaced it with the term 'operational requirements.' We discovered the business was disinterested in discussing 'non-functional' requirements but are actively engaged in discussing 'operational' requirements. It's psychology, they equated 'non-functional' with 'not important to me.' That psychology cascaded down the entire development team: project managers, lead developers, QA analysts. Everyone but architects. Now everyone is on the same page recognizing the importance of these requirements and as a result we're doing a much better job implementing them.
- nickpsecurity 11y agoThat's great. I like that. Terms that bridge how laypeople think and perceive with tech are the best.
- dragonwriter 11y agoThat's a fantastic improvement in word choice that I plan to steal.