It seems very common that certain customer requirements -- we call them "checklist features" -- won't ever be used. So when I'm deriving specifications, I alwa

It seems very common that certain customer requirements -- we call them "checklist features" -- won't ever be used. So when I'm deriving specifications, I always pay special attention to separating out the real needs and expectations from the checklist stuff. If you can do that well, then you can minimize the resources invested in the latter. But for whatever reason, those items are still on their list, and we can't just omit them. The trick is identifying which they are, and finding the minimum specification that allows it to be checked off the list.