3 ms·
A functional requirement is like adding a room to your house. A non functional requirement is defining what the construction material is and what the constructi
by partycoder 11y ago
A functional requirement is like adding a room to your house. A non functional requirement is defining what the construction material is and what the construction standards are.
What you describe is like constructing a house, then once it is constructed, specify it needs to be earthquake resistant.
That should be specified as an upfront requirement not a story.
If you construct it, and it was already earthquake resistant, should not be a problem. But if it wasn't, you will need to rebuild.
- jacques_chester 11y ago> What you describe is like constructing a house, then once it is constructed, specify it needs to be earthquake resistant. That should be specified as an upfront requirement not a story. There's no law against writing every story with some NFR component, or interspersing NFRs with regular feature stories. The process of writing, test-driving and accepting stories is a framework, it's guidelines. When I or other engineers see obvious architectural landmarks ahead, we often encourage the product managers to bring those forward. A story can have user value, and it can also have business value outside of user value. One such business value is attacking architectural risks. And sometimes you tell business "this unaddressed architectural scope is a big risk", and they say "OK, let's fix it". And that is still agile. The point was never rejecting high ceremony in order to replace it with low ceremony. It was that professionals should talk to each other. Constantly.
- partycoder 11y agoNFRs can be hard to add once something is built.
- jacques_chester 11y agoNobody is arguing with that. But it's also very wasteful to build an earthquake resistant house in a geologically stable area. You have to talk it over.