This article is part of my work on Conversation Patterns for Software Professionals
We work with stakeholders needs hidden by wanted features, we try to fulfill our needs hidden by wanted refactorings :) I've already posted two entries in the subject. These are: A User Story Template Revisited and Don't Confuse a Need with a Feature.
But what is actually "a need"? I clarified this term in the Need Structure article on the Conversation Patterns for Software Professionals.