liveBook · Manning

Feasibility

Feasibility is the practical possibility or degree to which an activity, task, project, or solution can be carried out under relevant constraints and conditions.

How 4 Manning books explain it

The Art of AI Product Development

The degree to which a task or product capability can be implemented effectively with available technology, expertise, time, and resources.

How it is used
Prioritizes AI opportunities alongside user impact and business value before a team commits to a solution.
How deep it goes
Works through data and expertise checks, then contrasts model exploration and simulations for higher-stakes validation; it does not specify implementation steps.
Examples
Uses music recommendations backed by listening data and personalized treatment plans tested through model exploration and simulations.
What you can do after
Evaluate/understand it by checking available data and team expertise, then weighing buildability against impact and value.

Read how The Art of AI Product Development explains feasibility →

Think Like a Software Engineering Manager

Feasibility is the degree to which a proposed idea or solution can be successfully implemented under relevant constraints.

How it is used
Guides project discovery and preplanning by testing whether proposed work is realistic before full execution.
How deep it goes
Moves from proof-of-concept testing to preliminary legal, technical, financial, resource, and timeline checks, stopping before detailed execution.
Examples
Uses automation value testing and the Project Accessible website to illustrate feasibility questions and go/no-go decisions.
What you can do after
Evaluate project realism, identify fundamental flaws, involve senior engineers, and decide whether to proceed to the next stage.

Read how Think Like a Software Engineering Manager explains feasibility →

Delivering Machine Learning Projects: From design to deployment

Feasibility is the degree to which a proposed project or solution can be successfully carried out within its available constraints and conditions.

How it is used
Uses feasibility checks during project framing and sprint 0 to decide whether work can proceed under technical, access, and estimation conditions.
How deep it goes
Breaks technical feasibility into risk, novelty, skills, infrastructure demands, and mitigations, then revisits estimates during sprint 0.
Examples
Uses a customer-churn prediction hypothesis and sprint 0 requests for access, information, and accounts as feasibility checks.
What you can do after
Evaluate feasibility by running diligence, identifying capability gaps, checking infrastructure and data, and revisiting estimates.

Read how Delivering Machine Learning Projects: From design to deployment explains feasibility →

Interview Speak

The practical possibility of completing a requested outcome within available time, budget, system, and staffing constraints.

How it is used
Assesses whether stakeholder requests fit available time, budget, systems, and staffing while guiding a tactful response.
How deep it goes
Defines feasibility through four constraints and prescribes evidence, alternatives, and compromises, without detailing a complete resolution.
Examples
Uses a customized product request, short timeframe, customer-service channel, and required sales process.
What you can do after
Practice/perform a tactful feasibility conversation using factual evidence and workable alternatives.

Read how Interview Speak explains feasibility →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.