Working with cross-functional teams, I have seen how easy it is for non-functional requirements to get sidelined until they cause real problems. Calling them “smart” only matters if they are treated as part of core planning, not an afterthought.
Agreed if they're an afterthought it will fail or it will cost a fortune to make change to the architrave retrospectively to meet the nfrs, and functional stakeholders need to be involved and need to understand the value of them
Working with cross-functional teams, I have seen how easy it is for non-functional requirements to get sidelined until they cause real problems. Calling them “smart” only matters if they are treated as part of core planning, not an afterthought.
What a time, you are inspiring every day. Well said, thanks for sharing it.
Agreed if they're an afterthought it will fail or it will cost a fortune to make change to the architrave retrospectively to meet the nfrs, and functional stakeholders need to be involved and need to understand the value of them