Introduction to Project Feasibility
Welcome to your study notes for Feasibility of the Project, a vital part of CCEA A2 Unit 3: Project Management Skills and Processes. In this portfolio unit, which makes up 24% of your total A Level (and 60% of your A2 mark), you take on the professional role of a Project Manager.
Before any business commits money, time, and staff to a new project, they need to answer one crucial question: "Is this project actually viable and worth doing?" This is where feasibility comes in. Conducting a feasibility study stops businesses from wasting valuable resources on ideas that cannot succeed.
Quick Review: A Feasibility Study is a structured evaluation of a proposed project's potential for success, carried out during the Initiation Phase of the project life cycle—before detailed planning begins.
The Role of the Project Manager & Professional Context
In Professional Business Services, you are not just a student completing a task; you are acting as an external consultant or internal Project Manager advising a client or firm.
Your job during the feasibility stage is to:
• Gather facts, data, and technical requirements.
• Objectively assess whether the project can realistically be delivered.
• Present a structured Feasibility Report to decision-makers to justify whether to proceed or stop.
Analogy: Think of a feasibility study like surveying land before building a house. You wouldn't buy bricks or hire builders before checking if the ground is solid and you have planning permission!
Classifications of Feasibility: The TELOS Framework
To evaluate a project thoroughly, project managers use the TELOS framework. This splits feasibility into five key dimensions:
1. Technical Feasibility
This evaluates whether the organization possesses or can acquire the necessary technology and technical skills.
• Key Questions: Do we have the hardware, software, and IT infrastructure needed? Does our team have the technical expertise to build and maintain the solution?
• Example: If an accounting firm wants to implement an AI document processing system, do they have the server capacity and trained technicians to run it?
2. Economic Feasibility
This involves a financial cost-benefit analysis to determine whether the project provides an acceptable return on investment (ROI).
• Key Questions: Can the business afford the upfront "price tag" of expertise, equipment, information, and staff time? Do the projected financial or strategic benefits outweigh the costs?
• Formula Context: Financial return must justify the capital outlay: \( \text{Net Benefit} = \text{Total Financial Gains} - \text{Total Project Costs} \).
3. Legal Feasibility
This ensures the proposed project complies with all mandatory laws, regulations, and industry standards.
• Key Questions: Does the project comply with data privacy laws such as GDPR / Data Protection? Does it follow Health and Safety regulations and employment law?
• Example: Setting up a client portal requires strict compliance with data storage laws so customer data is not illegally exposed.
4. Operational Feasibility
This focuses on human factors and business fit. A project can be technically brilliant, but it will fail if people refuse to use it.
• Key Questions: Does the project fit the current business culture and day-to-day operations? Will staff resist the change, or will they support it? Is there sufficient training planned?
• Example: Introducing a digital timesheet system will only work if employees find it easy to use and management supports the rollout.
5. Schedule Feasibility
This assesses whether the project can be completed within the required timeframe and target deadlines.
• Key Questions: Are the proposed milestones realistic? Can deliverables be achieved before strict client deadlines or seasonal market windows?
Memory Trick (TELOS):
• T – Technical (Can we build it?)
• E – Economic (Can we afford it?)
• L – Legal (Is it lawful?)
• O – Operational (Will it work in practice?)
• S – Schedule (Can we finish on time?)
Required Portfolio Evidence: The Feasibility Report
For your Unit A2 3 portfolio, you must produce a comprehensive Feasibility Report. This report must contain four central components:
1. Project Objectives (SMART)
Every project needs clear direction. Objectives must follow the SMART criteria:
• S (Specific): Clearly state what is to be accomplished.
• M (Measurable): Include quantifiable targets (e.g., reduce processing time by 15%).
• A (Achievable): Realistic given the team's capabilities.
• R (Realistic / Relevant): Aligned with the organization's overarching business strategy.
• T (Time-bound): Specify clear start and finish dates.
2. Risk Assessment
Every business project carries uncertainty. Identifying potential barriers or "expensive failures" early protects the business.
• Identify potential risks such as unexpected budget overruns, key staff illness, supplier delays, or software failure.
• Evaluate the likelihood and impact of each risk, and outline practical mitigation strategies.
3. Stakeholder Analysis
A stakeholder is any individual or group affected by the project. You must analyze:
• Internal Stakeholders: Project team members, managers, employees, and board directors.
• External Stakeholders: Clients, customers, suppliers, and regulatory bodies.
• Assess their level of interest and influence to ensure effective communication throughout the project.
4. Resource Requirements
You must outline and estimate all necessary resources before work starts:
• Human Labor: Staff hours, specialist contractors, and management time.
• Materials & Physical Assets: Equipment, workspace, and office supplies.
• Technology: Software licenses, cloud storage, and security tools.
Selecting a Project Management Methodology
As part of your feasibility assessment, you must select and justify an appropriate Project Management Methodology for your specific project. Common methodologies include:
• PRINCE2 (Projects IN Controlled Environments): A structured, process-driven methodology focusing on business justification, defined management stages, and clear roles.
• Waterfall: A sequential, linear methodology where each phase must be completed before the next begins (ideal for projects with fixed, well-defined requirements).
• Agile: An iterative, flexible methodology focusing on collaboration, rapid delivery of small components, and adaptability to change.
Key Tip: You must justify why your chosen methodology fits the specific nature, complexity, and timeline of your chosen project.
Assessment Objectives & Examiner Advice
Your feasibility evidence is assessed primarily against two Assessment Objectives:
• AO1 (Knowledge and Understanding): Demonstrating clear, accurate knowledge of feasibility concepts, project tools, and professional frameworks.
• AO2 (Application): Applying these concepts directly and realistically to your specific business scenario.
Common Pitfalls to Avoid
• Confusing Feasibility with Planning: Do not jump straight into Gantt charts and project execution schedules before proving feasibility. Feasibility justifies whether the plan should even be created.
• Generic Analysis: Avoid simply listing textbook definitions of TELOS. Examiners award top marks when you explain how each point applies specifically to your client or business scenario.
• Underestimating Risks: Identifying few or trivial risks weakens your critical evaluation. Real-world projects face budget constraints, technical glitches, and time pressures.
• Forgetting the Professional Persona: Maintain a formal, consultant-style tone throughout your Feasibility Report.
Chapter Summary
• Feasibility is conducted during the Initiation Phase to evaluate project viability.
• Use the TELOS framework: Technical, Economic, Legal, Operational, Schedule.
• A complete Feasibility Report requires SMART Objectives, a Risk Assessment, Stakeholder Analysis, and Resource Requirements.
• Justify an appropriate Methodology (such as PRINCE2, Waterfall, or Agile) tailored to the project's needs.