Introduction to the Logical Framework Approach - Stockholm ...

More documents

Recommendations

Info

Introduction to the LFAReaderThe decision on whether or not to include an assumption in the logframe (is itsufficiently important?) can become difficult. Indicating assumptions shouldserve the purpose to assess the weight of risks and dependencies beforedeciding on the implementation of a project and later on to observe theserisks and dependencies during project implementation. The choice whichwhich assumptionsto place inassumptions to include in the matrix should be made bearing this purpose inmind. In general the risks for project implementation should not be too high. the matrix?Stating many assumptions in the logframe suggests high risks for a project,that’s why only the most important (in the sense described above)assumptions are mentioned. Exceptions definitely exist where risks arewillingly being accepted and the project is willingly being placed in an“insecure” setting. The decision depends on the acceptability of risks for aproject in a specific situation. The purpose of stating risks and dependenciesstays the same, that is to identify, assess and observe them.Assessment of AssumptionsDSEIs the external factor important?Will it be realised?Almost certainlyLikelyYesUnlikelyRedesign the project by addingactivities or results; reformulate theImmediate Objective if necessaryYesNoDo not include in logframeDo not include in logframeInclude as an assumptionIs it possible to redesign the project inorder to influence the external factor?NoThe project is not feasibleFor group discussions it might be of help to use the algorithm displayedabove. It is by no means a “mathematical” instrument as the name mightsuggest. It can help to facilitate and structure group discussions to distinguishbetween those assumptions to be included in the matrix and those to be leftout. 3333 Graph adapted from European Commission, 1999, p. 27.26
Introduction to the LFAFollowing the algorithm’s logic (above) it becomes clear that those externalfactors that are essential for the project to achieve its objectives, but willmost probably not be realised become so called “killer assumptions” ifthe project cannot be redesigned to achieve its objectives without having torely on the realisation of the respective external factor.Reader“killerassumptions”Project Strategy & AssumptionsDSEProjectStrategyObjectivelyVerifiableIndicatorsSources ofVerificationAssumptionsDevelopmentObjectives• Biodiversity of globallysignificant aquatic lifeconserved• Living conditions of localpeople improvedImmediateObjectivePollution load of wastewaterdischarged into riverreducedPollution through applicationof fertilizers/ pesticidesreducedOutputs1. Incentives for avoidinghigh pollution ofwastewater are effectiveUpstream water qualityremains stableActivities1.1 Analyse environmentalinvestments ofcompanies1.2 Identify relevant cleantechnologies1.3 Design incentives1.4 Test incentives1.5 Adapt incentivesMeansCostPre-conditionsForeseen budget forenvironmental measures isavailable in timeAssumptions are not meant to serve as excuses for project managers shiftingresponsibilities for sustainability outside the range of the project (on thedevelopment objective level). Sustainability has to be build into the projectdesign, otherwise it won’t be accomplished, especially not through factorsexternal to the project. 342.3.4. Objectively Verifiable IndicatorsObjectively verifiable indicators (OVIs) describe a project’s objectives inmeasurable “empirically observable” 35 terms and provide the basis forperformance measurement and project monitoring and evaluation: they areparameters of change or of results, indicating as to what extent theproject objectives have been achieved. Indicators help to createtransparency conveying to others what the project intends to achieve andare placed into the second column of the logframe matrix.indicators asparameters ofchange orresults34 Also see COMIT, p. 71.35 COMIT, p. 75.27
Page 6 and 7: Introduction to the LFApicture what
Page 8 and 9: Introduction to the LFA• a consis
Page 10 and 11: Introduction to the LFAand projects
Page 12 and 13: Introduction to the LFAReaderIndivi
Page 14 and 15: Introduction to the LFAplanning ste
Page 16: Introduction to the LFAproblems are
Page 19 and 20: Introduction to the LFApotentials s
Page 21 and 22: Introduction to the LFA2.3. The pla
Page 23 and 24: Introduction to the LFA2.3.2. Level
Page 25: Introduction to the LFAthe initial
Page 29 and 30: Introduction to the LFAachievement
Page 31 and 32: Introduction to the LFAReaderThe De
Page 33 and 34: Introduction to the LFA• Specify
Page 35 and 36: Introduction to the LFASpecifying f
Page 37 and 38: Introduction to the LFAReaderLogfra
Page 39 and 40: Introduction to the LFA“Lack-fram
Page 41 and 42: Introduction to the LFAGenerally th
Page 43 and 44: Introduction to the LFAIt should be
Page 45 and 46: Introduction to the LFAReader3. APP
Page 47: Introduction to the LFAReader47
Page 50 and 51: Introduction to the LFAReaderLFA to
Page 52 and 53: Introduction to the LFA4. ANNEXESRe
Page 54 and 55: Introduction to the LFAReader4.3. G
Page 56 and 57: Introduction to the LFAMilestonesOb
Page 58: Introduction to the LFAStrategy Ana

Introduction to the Logical Framework Approach - Stockholm ...

Create successful ePaper yourself

Delete template?

Save as template?