Answer.
Feasibility analysis is the study of project requirements for technical, business, resource, time, and legal viability.
The business analyst conducts this analysis before the decision is approved and handed over for development, in order to reduce the risk of delays or investing resources in unachievable functionality.
During the analysis, the business analyst:
- Checks whether the requirement can be implemented considering technological constraints (e.g., integration with legacy systems).
- Evaluates how the requirement aligns with business goals and strategy.
- Validates legal compliance (GDPR, local legislation).
- Estimates resource and time requirements.
Key features:
- The analysis is conducted iteratively, involving architects and key stakeholders.
- Requirements that do not pass this stage are revised or discarded.
- Feasibility can be economic, technical, operational, and legal.
Tricky questions.
Is the expert opinion of a business analyst enough for feasibility analysis?
No, teamwork is necessary: analyst, architect, specialized developers, often — lawyers.
If a requirement passes feasibility, does that mean it will automatically be implemented?
No, feasibility is a necessary but not sufficient condition, as project priorities and constraints also affect the choice.
Is feasibility analysis needed only at the start of the project?
No, it should be repeated with each significant change in requirements or implementation conditions.
Common mistakes and anti-patterns
- Neglecting feasibility analysis for "simple" or typical requirements
- Underestimating technical or regulatory constraints
- Focusing only on stakeholder wishes, without consulting architects or developers
Example from life
Negative case:
- The business wanted to implement a super-fast online calculator but did not account for outdated infrastructure. As a result, it became apparent just a month after the start that the requirement was unachievable — the product had to be scaled down.
Pros: Fast response to business needs.
Cons: Loss of time, money, dissatisfaction of stakeholders.
Positive case:
- Before launching new functionality for retail clients, the requirements underwent preliminary feasibility analysis, constraints were identified, and some requirements were revised. The final release was delivered on time and with minimal adjustments.
Pros: Minimization of risks of delays and budget overruns.
Cons: Time spent on analytical work before the start of work.