<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="TLS_2014_MCC-T_v01_M" xml-lang="en" xmlns="http://www.icpsr.umich.edu/DDI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.icpsr.umich.edu/DDI http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>DDI_TLS_2014_MCC-T_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Metadata Producer">Millennium Challenge Corporation</producer>
      <prodDate date="2015-01-05">2015-01-05</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (January 2015)
Version 2.0 (May 2015). Edited version based on Version 01 (DDI-MCC-TLS-SI-THRESHOLD-2014-v1) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Threshold 2014</titl>
      <subTitl/>
      <altTitl>MCC-T 2014</altTitl>
      <parTitl/>
      <IDNo>TLS_2014_MCC-T_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">Social Impact</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-14">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="Millennium Challenge Corporation" URI="" email="impact-eval@mcc.gov">Monitoring &amp; Evaluation Division</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">Not applicable to this evaluation; no quantitative data to be shared</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Transparency</keyword>
      <keyword vocab="" vocabURI="">Reform</keyword>
      <keyword vocab="" vocabURI="">Corruption</keyword>
      <topcClas vocab="MCC Sector" vocabURI="">Capacity Building and Institutional Development</topcClas>
    </subject>
    <abstract>This final performance evaluation is intended to provide an objective, rigorous, and evidence-based analysis of the Fostering Transparency Initiative's (FOTI) overall performance. Specifically, the evaluation will look to identify, review, and assess four key aspects by utilizing the following evaluation questions: 

1. Program Logic 
a. Were the original six program components relevant to the Timorese context? (e.g. were they based on initial analysis of assumptions, risks, and external factors?) 
b. Were any changes made to the program logic during the implementation? If so, were they appropriate? 

2. Activities Designed and Implemented 
a. Were planned activities actually implemented? Why or why not? 
b. Were any new activities designed and implemented? If so, why? 
c. What was the effectiveness of activities? 

3. Influence on Changes in Knowledge, Attitudes, and Behaviors 
a. Did implemented activities lead to measurable outcomes, such as changes in knowledge, attitudes, or behavior? 

4. Sustainability &amp; Lessons Learned 
a. Have key implemented activities been sustained? 
b. What is the likelihood for future sustainability? 
c. What are the key aspects of FOTI that should be continued in the near term? 
d. Which aspects of FOTI would be appropriate to replicate in other contexts?</abstract>
    <sumDscr>
      <collDate date="2014-02" event="start" cycle="Preliminary data collection"/>
      <collDate date="2014-02" event="end" cycle="Preliminary data collection"/>
      <collDate date="2014-07" event="start" cycle="Data collection"/>
      <collDate date="2014-07" event="end" cycle="Data collection"/>
      <nation abbr="TLS">Timor-Leste</nation>
      <geogCover>National coverage</geogCover>
      <geogUnit/>
      <anlyUnit>Individuals</anlyUnit>
      <universe/>
      <dataKind>Other</dataKind>
    </sumDscr>
    <!-- qualityStatement - ddi2.5 - complex type
     
     This structure consists of two parts, standardsCompliance and otherQualityStatements. 
     In standardsCompliance list all specific standards complied with during the execution of this 
     study. Note the standard name and producer and how the study complied with the standard. 
     Enter any additional quality statements in otherQualityStatements.
     
     -->
    <qualityStatement>
      <standardsCompliance>
        <standard>
          <standardName/>
          <producer/>
        </standard>
        <complianceDescription/>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes/>
    <!-- exPostEvaluation ddi2.5
      Use this section to describe evaluation procedures not address in data evaluation processes. 
      These may include issues such as timing of the study, sequencing issues, cost/budget issues, 
      relevance, instituional or legal arrangments etc. of the study. 
      
      The completionDate attribute holds the date the evaluation was completed. 
      The type attribute is an optional type to identify the type of evaluation with or without 
      the use of a controlled vocabulary.
    -->
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth/>
      <dataCollector abbr="" affiliation="">Casals &amp; Associates</dataCollector>
      <dataCollector abbr="SI" affiliation="">Social Impact, Inc.</dataCollector>
      <!-- collectorTraining - DDI2.5
        
        Collector Training

        Describes the training provided to data collectors including internviewer training, process testing, 
        compliance with standards etc. This is repeatable for language and to capture different aspects of the 
        training process. The type attribute allows specification of the type of training being described.
        
        -->
      <collectorTraining type=""/>
      <frequenc/>
      <sampProc>A random sample of monitoring data from 17 trainings was analyzed to assess both the strength of the technical questions in the tests and also the level of trainee learning as captured by the post-tests.  The Team Leader interviewed also 14 key informants interviewed during the preliminary fieldtrip in February 2014 using convenience sampling. A total of 44 informants were interviewed by the full field team during the field visit in July 2014. Four additional stakeholders were interviewed via phone after the fieldwork was completed.</sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <resInstru/>
      <!-- instrumentDevelopment - DDI2.5             
        Describe any development work on the data collection instrument. Type attribute allows for the optional use of a defined development type with or without use of a controlled vocabulary.
        -->
      <instrumentDevelopment type=""/>
      <collSitu>The mixed methods evaluation was carried out by a four-member team from Social Impact, Inc. during field visits in early 2014. In February 2014, while the FOTI project was still active, the Team Leader completed preliminary data collection during an evaluation design trip. In July 2014, the other three team members completed data collection during a two week field visit to Timor-Leste. The evaluation utilized ongoing data analysis, an iterative methodology, and careful triangulation of data sources throughout the research process. The evaluation team utilized the following methodologies: document review; technical evaluation of "deliverables"; pre- and post-test data; key informant interviews; and a field visit to Baucau. 

Although the evaluation team attempted to complete a rigorous examination of the approved research questions, it proved impossible to utilize all of the proposed research methodologies due to logistical and bureaucratic realities in Timor-Leste. For example, although the team initially planned to conduct mini-surveys and focus group discussions, the team did not gain access to enough program beneficiaries to make data obtained from such informants meaningful. Other limitations include: challenge in measuring qualitative outcomes; logistical and timing challenges; recall and attribution bias; selection bias; and use of interpreter. For further details, please see Annex II. While these factors limit the quantity and quality of the data collected, the team made every effort to fill gaps in the data, particularly by examining all available program documentation. Through this triangulation of sources, the team feels that the information presented in this report is an accurate depiction of the FOTI program.</collSitu>
      <actMin/>
      <ConOps/>
      <weight/>
      <cleanOps/>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate/>
      <EstSmpErr/>
      <dataAppr/>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://data.mcc.gov/evaluations/index.php/catalog/136">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/136
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="no" formNo="" URI=""/>
      <restrctn/>
      <citReq>U.S. Agency for International Development. Final Performance Evaluation of the Fostering Transparency Initiative Program in Timor-Leste. September 2014.</citReq>
      <deposReq/>
      <conditions>The report is available for USAID/MCC internal review and is not open to the public.</conditions>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
