Capacity Development Project Formulation Exercise
EXT 505 – Capacity Development | Practical 2
M.Sc. Extension Education · Punjab Agricultural University, Ludhiana
Introduction
Practical 1 answered "what do people need?" Practical 2 answers the next question: how do we turn an identified need into a fundable, implementable project? A needs assessment produces a list of gaps and priorities — a project proposal turns the top priority into a logically structured plan with objectives, activities, indicators, budget, and a monitoring framework that a funding agency (ATMA, NABARD, ICAR, an NGO donor) can actually appraise and approve.
The core tool taught in this practical is the Logical Framework Approach (LFA), developed originally for USAID in 1969 and now the standard planning tool used by FAO, World Bank, NABARD, and most bilateral donors worldwide.
Learning Outcomes
- Distinguish project, programme, scheme, plan, and policy.
- Construct a problem tree and convert it into an objective tree.
- Build a complete Logical Framework (Logframe) matrix with indicators, means of verification, and assumptions.
- Draft the standard components of a project proposal.
- Apply Indian institutional project-formulation formats (ATMA/SREP, NABARD, RKVY).
- Identify common logical and design flaws in a weak project proposal.
ЁЯФм Why This Matters
Most extension project proposals are rejected or under-perform not for lack of good ideas, but for weak internal logic — activities that don't actually produce the stated outputs, or indicators that can't be measured. The Logframe exists specifically to force this logic to be tested on paper before money and time are committed.
Project vs Related Concepts
Terms students routinely confuse in exams and in real proposal writing:
| Term | Definition | Example |
|---|---|---|
| Project | A time-bound, budgeted set of activities with specific objectives, a defined target group, and a start/end date | 18-month FPO capacity-building project for 500 farmers |
| Programme | A broader, often ongoing collection of related projects working toward a common goal | ATMA's annual extension programme (contains many projects) |
| Scheme | A government-designed benefit or support mechanism with defined eligibility rules | PM-KISAN, RKVY, PMFBY |
| Plan | A statement of intended goals and the broad strategy to reach them, without necessarily being budgeted or time-bound | District Agriculture Development Plan |
| Policy | A governing principle or rule that guides decisions across many programmes/projects | National Agricultural Policy (2000) |
⚠️ Common Error
Students often use "project," "programme," and "scheme" interchangeably in written answers. Examiners specifically test this distinction — a project always has a defined budget, timeline, and closure; a programme or policy usually does not.
Step 1: Problem Analysis (Problem Tree)
Before writing any objective, the core problem must be stated precisely and its causes and effects mapped. The Problem Tree (a core LFA tool) has three layers:
- Core Problem (trunk) — the central negative situation, stated as a single problem, not as "lack of a solution"
- Causes (roots, below) — what is producing the core problem
- Effects (branches, above) — what results from the core problem
Worked Example: Low Vegetable Farmer Income
⚠️ Common Design Flaw
Writing the core problem as "lack of training" or "absence of a scheme" is a frequent student error — this states a missing solution, not a problem, and it pre-judges the intervention before the analysis is done. The problem should describe the negative situation (e.g., "low income," "high crop loss"), never a missing service.
Step 2: Objective Analysis (Objective Tree)
Every negative statement in the problem tree is rewritten as a positive, desired condition. Causes become means; effects become ends. This directly generates the hierarchy of objectives used in the Logframe.
| Problem Tree (Negative) | → | Objective Tree (Positive) |
|---|---|---|
| Low and unstable income of small vegetable growers | → | Stable, improved income of small vegetable growers |
| Low productivity (poor IPM knowledge) | → | Farmers apply IPM practices effectively |
| High post-harvest losses | → | Post-harvest losses reduced |
| Weak market linkage | → | Farmers have improved market access and price negotiation |
The bottom row of the objective tree ("Farmers apply IPM," "Losses reduced," "Market access improved") becomes the Outputs of the project; the top statement becomes the Goal/Overall Objective.
The Logical Framework Approach (LFA)
The Logframe organises the objective hierarchy into a 4×4 matrix with two kinds of logic:
- Vertical logic: Activities → Outputs → Purpose → Goal (the "if-then" chain — if activities are done, outputs result; if outputs are achieved, purpose is served; if purpose is achieved, it contributes to the goal)
- Horizontal logic: for each level, how it will be measured (Indicator), how that measurement will be verified (Means of Verification), and what external condition must hold true (Assumption)
The Logframe Matrix
| Level | Narrative Summary | Indicators | Means of Verification | Assumptions |
|---|---|---|---|---|
| Goal (long-term impact) |
Improved and stable livelihood of small vegetable growers in the block | Average household income from vegetables up by 20% within 3 years | District income/agriculture statistics, follow-up survey | Market prices remain stable; no major climatic shock |
| Purpose (project outcome) |
Small vegetable growers adopt improved production and marketing practices | 70% of trained farmers adopt ≥2 improved practices within 1 year | Follow-up field survey, adoption records | Farmers remain motivated after training; inputs remain accessible |
| Outputs (deliverables) |
1. Farmers trained in IPM 2. Post-harvest handling improved 3. Market linkage established |
150 farmers trained; loss reduced from 22% to 12%; 1 FPO-market tie-up signed | Training attendance records, loss-assessment survey, MoU with buyer | Trainers and inputs available on schedule |
| Activities (actions) |
1.1 Conduct 5-day IPM training 2.1 Demonstrate low-cost storage 3.1 Facilitate FPO-buyer meetings |
Inputs: budget, trainers, venue, demo materials | Financial records, activity reports | Timely fund release; farmer willingness to participate |
ЁЯМ╛ How to Read This Matrix
Read the Narrative Summary column bottom-to-top with "if...then": IF activities are carried out AND assumptions hold, THEN outputs result; IF outputs are delivered AND assumptions hold, THEN purpose is achieved; IF purpose is achieved AND assumptions hold, THEN it contributes to the goal. This "if-then" chain is exactly what an appraisal committee checks first.
⚠️ Common Design Flaws in Student Logframes
- Unmeasurable indicators — "farmers' knowledge improves" (how much? by when?) instead of "70% score ≥80% on post-test within 1 month"
- Confusing outputs with activities — "conduct training" is an activity; "farmers trained and certified" is the output
- Assumptions that are actually pre-conditions for the whole project to make sense (a "killer assumption") — e.g., "government releases funds on time" being listed as an assumption for a government-funded project is often unavoidable, but assumptions like "monsoon is normal" for an irrigation project should trigger a rethink of design, not just be listed and ignored
The Project Formulation Process
Full sequence from needs assessment output to an approved project — narrate the linkages verbally; table gives quick reference.
| Step | Quick Note |
|---|---|
| 2. Stakeholder Analysis | Identify who benefits, who implements, who might resist — a matrix of interest vs. influence is commonly used |
| 5. Strategy Analysis | Multiple branches of the objective tree usually can't all be funded — select the most feasible/impactful cluster as the project's actual scope |
| 7. Activity & Resource Schedule | Gantt-chart style timeline mapped to each activity in the Logframe |
| 8. Budgeting | Line-item budget tied directly to activities (honoraria, materials, travel, contingency) |
| 10. Appraisal & Approval | Technical appraisal (is the logic sound?) + financial appraisal (is the budget justified?) by the funding body |
Standard Components of a Project Proposal
The template most funding agencies (ATMA, NABARD, ICAR schemes, NGO donors) expect, in order:
1. Title & Summary
Concise project name; one-paragraph executive summary.
2. Background & Rationale
Situation analysis; why this problem, why now — drawn directly from the needs assessment.
3. Goal & Objectives
From the objective tree / Logframe Goal and Purpose rows.
4. Target Group & Area
Who benefits, how many, where — with selection criteria.
5. Methodology / Strategy
Approach and methods (training, demonstration, PRA, etc.) linking to Outputs and Activities.
6. Work Plan / Timeline
Activity schedule (Gantt chart), responsible persons.
7. Budget
Line-item costs matched to activities; source of funds.
8. Monitoring & Evaluation Plan
Indicators and means of verification from the Logframe; who monitors, how often.
9. Sustainability Plan
What continues after project funding ends.
10. Annexures
Logframe matrix, CVs of key personnel, letters of support, budget details.
ЁЯЗоЁЯЗ│ Indian Institutional Formats
ATMA/SREP: block-level proposals built directly on the participatory needs assessment (Practical 1), consolidated into the district Strategic Research and Extension Plan. NABARD: requires a detailed logframe-style project report (DPR) with financial and technical appraisal for farm-sector credit-linked projects. RKVY / ICAR schemes: standardised proposal formats with defined objective, output, and budget headings, closely mirroring the Logframe structure even where "Logframe" isn't named explicitly.
Beyond Agriculture — Same Logic, Other Sectors
ЁЯФД Transferable Framework
The Logframe is sector-neutral. A health NGO formulating a maternal-nutrition project runs the identical sequence — problem tree (high maternal anaemia) → objective tree → Logframe (Goal: improved maternal health; Purpose: improved dietary practices; Outputs: women trained, supplements distributed). A school proposing a remedial-education project for weak learners follows the same structure with different content. Worth a one-line mention in class so students see this as a general planning competency, valuable beyond agricultural extension roles.
❓ Frequently Asked Questions
Click any question to reveal the answer.
An Output is a direct deliverable the project controls (e.g., "150 farmers trained"). An Outcome/Purpose is the behavioural or condition change that results if farmers actually use what they learned (e.g., "farmers adopt IPM practices") — it depends on the target group's response, which the project cannot fully control, hence the "Assumptions" column exists at that level.
Yes, deliberately. No project fully controls its environment. Naming assumptions forces planners to identify external risks (weather, input availability, government fund release) up front, so they can be monitored — rather than being discovered as an excuse only after the project fails.
The Logframe is a one-page planning and logic-check tool (usually an annexure). The project proposal is the full narrative document — background, rationale, methodology, budget, timeline — that uses the Logframe's Goal/Purpose/Output/Activity structure as its backbone.
Break the qualitative concept into observable proxies — e.g., for "women's empowerment": number of women attending village meetings, number holding SHG leadership roles, or self-reported decision-making participation on a rating scale. The indicator doesn't have to capture the whole concept, just a defensible, countable proxy for it.
No. The problem tree usually reveals more causes than one project can address. Step 5 (Strategy/Alternative Analysis) is exactly where the team selects a feasible cluster of causes to act on, based on budget, mandate, and impact — the rest are acknowledged but left out of this particular project's scope.
References (click to expand)
Logical Framework Approach
- NORAD. (1999). The Logical Framework Approach: Handbook for Objectives-Oriented Planning (4th ed.). Norwegian Agency for Development Cooperation.
- AusAID. (2005). AusGuideline: The Logical Framework Approach. Australian Agency for International Development.
- European Commission. (2004). Aid Delivery Methods: Project Cycle Management Guidelines. EuropeAid Co-operation Office.
Project Planning and Capacity Development
- Kaufman, R. (2000). Strategic Planning for Success: Aligning People, Performance, and Payoffs. Jossey-Bass.
- Morgan, P. (2006). The Concept of Capacity. European Centre for Development Policy Management.
- FAO. (2010). Capacity Development Learning Modules. Food and Agriculture Organization of the United Nations.
- UNDP. (2009). Capacity Development Practice Note. United Nations Development Programme.
Extension Education Texts
- Ray, G. L. (2005). Extension Communication and Management. Kalyani Publishers.
- Sandhu, A. S. Extension Programme Planning. Punjab Agricultural University Publications.
- Dahama, O. P., & Bhatnagar, O. P. Education and Communication for Development. Oxford & IBH Publishing.
Indian Institutional Context
- NABARD. Guidelines for Preparation of Detailed Project Reports (DPR). National Bank for Agriculture and Rural Development.
- Ministry of Agriculture and Farmers' Welfare. ATMA Guidelines and Strategic Research and Extension Plan (SREP) Format. Government of India.
- ICAR. (2012). Strategic Plan 2012–2017. Indian Council of Agricultural Research.