Feasibility is the degree to which an idea can be implemented successfully within relevant business, technical, legal, financial, resource, and time constraints. A feasibility analysis is a preliminary, objective check of whether the proposed outcome is realistic and viable. Project discovery uses proof-of-concept work to test feasibility before committing to full execution. section 10.1.1 section 10.1.2
Assess feasibility by asking practical questions before the project advances:
- Check legal and business constraints: could regulations or market conditions prevent the product from being sold? section 10.1.2
- Check technical readiness: does the organization have, or can it create, the technology required? section 10.1.2
- Check authorization and dependencies: do the relevant teams and leaders support the work, and can dependent work proceed? section 10.1.2 section 3.2.1
- Check capacity and cost: are enough people, budget, software, hardware, and time available? section 10.1.2
- Use proof-of-concept work to test the value and practicality of an idea, such as time saved through automation. section 10.1.1
Project Accessible
A toy company plans a website for a new line of accessibility-friendly toys. Before execution, the project manager checks whether selling the products has legal obstacles, whether the hardware team has leadership approval, whether the website technology is available, and whether staffing and budget are sufficient. Senior engineers contribute to the technical assessment. Strong confidence allows the project to continue; unresolved doubts require reconsideration before the next stage. section 10.1.2
Feasibility also informs team goals and strategy: cost, development effort, timelines, dependencies, and feasibility analysis help determine whether objectives are achievable and aligned across teams. section 3.2.1
