When Eliciting requirements, these are question I usually raise independently on the domain:
- Why It is a Problems for you?
- Why do you need this?
- Why It needs to be different?
I believe the answers are crucial for the requirement analysis. They basically will show the customer's real needs, their business problems. Detail requirements from this point is supposed to be safer and we'll see why.
What is a Business Problem?
A problem on this context is something that does not let business goes forward as it needs. You can think on it as the reason why you (Software Engineer) was called. A Problem is usually characterised as something that involves money somehow. When talking with business people about some problem, try to get from him how the problem (usually mentioned as a business need) he is talking about makes his company loose money.
Why Identify Problems is Important?
As a Software Engineer, have you received a complied requirements list ready to be implemented? If your answer is yes, how were you sure these requirements are really the ones your customer is waiting for? If you manage to correlate requirements to business problems to be solved, you'll be able to have this answer. By doing that, you avoid resources to be wasted by implementing features that are not valuable to business.
Spreading this mindset to the whole tech team is also valuable due several reasons:
- Team can prioritise refactorings and design efforts on parts of the systems that will really makes the difference.
- The feeling that the team is building something really valuable.
- Team is able to understand what makes business slow down, then create solutions that properly address these issues.
How to Identify Business Problems?
Looking for business problems when eliciting requirements may seem too vague, a good tip here is look for problems that make the company loose money directly or indirectly. Business people usually report them as ".. this process it taking too long .. " or ".. Because it is too complex and involves too many people be coordinated..", etc. Even not mentioning the word "money" explicitly, they are talking about time, resources, etc.
Achieve this point may be tricky and will demand you some experience on the field depending the domain you are. BTW, a technique is which is helpful is here to use Business Objective Models. It helps to identify business problems and objectives. Going through this process, you will also be able to have a set of high level features that the final solution will need to provide.
Even looking obvious, there are projects where this process is just ignored. By doing that, people are assuming the risk to be working on requirements that doesn't bring the value business is expecting. Be suspicious when your customer came to saying: "My solution needs to do this and that...". You are may running in this scenario.
By doing the Problem Discovery approach, it is gonna be also easier to have everyone on the same page (business and tech team) on which regards where the efforts needs to be applied, once the objectives are clear to everybody.
It also works well with the Iterative approach. You'll may have a chance to work with your customer showing him business problems that even him isn't not aware of.