Difference between revisions of "Retreat2016"
Jmstapleton (talk | contribs) (Imported from Wikispaces) |
|||
| Line 1: | Line 1: | ||
| − | + | ==''' Africa RISING PCT phase 2 proposal development retreat <br /> 21-23 March 2016<br/>Arusha, Tanzania'''== | |
| − | |||
| − | |||
| − | |||
---- | ---- | ||
| − | =Participants= | + | ===Participants=== |
| − | + | :-Irmgard Hoeschle-Zeledon | |
| − | Peter Thorne | + | :-Peter Thorne |
| − | Carlo Azzarri | + | :-Carlo Azzarri |
| − | Bernard Vanlauwe | + | :-Bernard Vanlauwe |
| − | Siboniso Moyo | + | :-Siboniso Moyo |
| − | Asamoah Larbi | + | :-Asamoah Larbi |
| − | Kindu Mekonnen | + | :-Kindu Mekonnen |
| − | Bekunda Mateete | + | :-Bekunda Mateete |
| − | James Stapleton | + | :-James Stapleton |
| − | =Objectives= | + | ===Objectives=== |
| − | + | * Complete a full draft of the overall phase 2 proposal | |
| − | + | * Produce good first drafts of the 3 region proposals; also the IFPRI one. | |
| − | + | * Agree steps to complete the overall proposal and regional/ifpri proposals sufficient to go to Jerry Glover at USAID, obtain any external reviews etc | |
| − | =Follow up / Actions= | + | ===Follow up / Actions=== |
[[phase2_planning| Phase 2 milestones (to be updated with results)]] | [[phase2_planning| Phase 2 milestones (to be updated with results)]] | ||
| − | =Agenda= | + | ===Agenda=== |
Day I | Day I | ||
| − | + | 09:00am Agree the expected outcomes. What do we want to achieve by the end of the three day<br/> | |
| − | + | 09:30am Stocktaking exercise: short updates on the shape of each of the regional documents: | |
| − | + | ::-Agree format of the region projects and how they link to overall concept.</br> | |
| − | 10 | + | 10:30am end of day I</br> |
| − | Based on the agreed principles of harmonization, critically | + | :-Based on the agreed principles of harmonization, critically each component/section of the current draft of the umbrella document. For each</br> |
| − | + | :-Identify the gaps and weaknesses of each section</br> | |
| − | + | :-Identify what needs to be done in each section, develop a to-do list</br> | |
| − | + | :-Delegate the work to groups and individuals, allowing the substance to be discussed by the writers.</br> | |
| − | + | :-Give finished pieces to editors/ writers to: | |
| − | + | Give feedback on draft changes</br> | |
| − | + | :-Strengthen the language in agreed texts and reviewing the coherence of the documentation.</br> | |
Day II | Day II | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | 09:00am Briefly review the work of day </br> | ||
| + | ::Consolidate of existing gaps, and identify what work needs to be done, who will do it and by when</br> | ||
| + | 10:00am Define and agree the substantive red threads all proposals need (harmonize where possible, while not sacrificing the quality of the work).</br> | ||
| + | :-After the discussion</br> | ||
| + | :- Delete the elaboration of the discussion to writers</br> | ||
| + | :- For common elements, agree graphics etc. and delegate to a group to work on</br> | ||
| + | :- Review the above work</br> | ||
| + | 02:00pm Based on the earlier conversation</br> | ||
| + | *Identify the gaps and weaknesses of each section of each country </br> | ||
| + | *Identify what needs to be done in each section, develop a to-do list</br> | ||
| + | * Delegate the work to groups and individuals, allowing the substance to be discussed by the writers.</br> | ||
| + | *Give finished pieces to editors/ writers to</br> | ||
| + | *Give feedback on draft changes</br> | ||
| + | *Strengthen the language in agreed texts and reviewing the coherence of the documentation.</br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | '''Day III''' | ||
| + | 12:00pm Briefly review the work of day II </br> | ||
| + | 12:30pm Consolidate of existing gaps, and identify what work needs to be done, who will do it and by when</br> | ||
| + | 04:00pm Agree the outline of the budget of each proposal | ||
| + | Work on it in groups</br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ===Outcomes=== | |
| + | # All the sections of the program document were reviewed, with the exception of three (achievements section, research questions and program coordination), by the team and passed on to James Stapleton for editing</br> | ||
| + | # James Stapleton finished of the following sections: background, vision of success, theory of change, stakeholder engagement, scaling. Six sections remain to be finalized by 24 March COB: Moving to phase II, core principles, response to demand-driven research-in-development, Cross-cutting issues / higher level outcomes, M&E, and communications</br> | ||
| + | # The overall structure of the regional proposals was discussed, tweaked and agreed.</br> | ||
| + | # Regional issues relating to budget, common graphs and targets were discussed, as were the issues of program coordination and M&E</br> | ||
| − | 28 March: Program proposal document edited (with the exception of the three missing sections) | + | ===Next steps=== |
| − | 28 March: comments received back on the program coordination document | + | 28 March: Program proposal document edited (with the exception of the three missing sections)</br> |
| + | 28 March: comments received back on the program coordination document</br> | ||
| − | 29 March: Text on research questions produced | + | 29 March: Text on research questions produced</br> |
| − | 31 March: Comments back and text on research questions agreed | + | 31 March: Comments back and text on research questions agreed</br> |
| − | 10 April: Regional target numbers finalized | + | 10 April: Regional target numbers finalized</br> |
| − | 15 April: Achievements and lessons learned section of the program proposal finalized | + | 15 April: Achievements and lessons learned section of the program proposal finalized</br> |
| − | 19 April: Program proposal documents edited | + | 19 April: Program proposal documents edited</br> |
| − | 22 April: All regional documents finalized | + | 22 April: All regional documents finalized</br> |
| − | 25 April: Regional documents checked for coherence by CKM, and adjusted as necessary | + | 25 April: Regional documents checked for coherence by CKM, and adjusted as necessary</br> |
| − | 05 May: All regional documents edited by respective centres | + | 05 May: All regional documents edited by respective centres</br> |
| − | 10 May: Program and regional documents sent to USAID | + | 10 May: Program and regional documents sent to USAID</br> |
Latest revision as of 09:19, 16 November 2018
Contents
Africa RISING PCT phase 2 proposal development retreat
21-23 March 2016
Arusha, Tanzania[edit | edit source]
Participants[edit | edit source]
- -Irmgard Hoeschle-Zeledon
- -Peter Thorne
- -Carlo Azzarri
- -Bernard Vanlauwe
- -Siboniso Moyo
- -Asamoah Larbi
- -Kindu Mekonnen
- -Bekunda Mateete
- -James Stapleton
Objectives[edit | edit source]
- Complete a full draft of the overall phase 2 proposal
- Produce good first drafts of the 3 region proposals; also the IFPRI one.
- Agree steps to complete the overall proposal and regional/ifpri proposals sufficient to go to Jerry Glover at USAID, obtain any external reviews etc
Follow up / Actions[edit | edit source]
Phase 2 milestones (to be updated with results)
Agenda[edit | edit source]
Day I
09:00am Agree the expected outcomes. What do we want to achieve by the end of the three day
09:30am Stocktaking exercise: short updates on the shape of each of the regional documents:
- -Agree format of the region projects and how they link to overall concept.
- -Agree format of the region projects and how they link to overall concept.
10:30am end of day I
- -Based on the agreed principles of harmonization, critically each component/section of the current draft of the umbrella document. For each
- -Identify the gaps and weaknesses of each section
- -Identify what needs to be done in each section, develop a to-do list
- -Delegate the work to groups and individuals, allowing the substance to be discussed by the writers.
- -Give finished pieces to editors/ writers to:
Give feedback on draft changes
- -Strengthen the language in agreed texts and reviewing the coherence of the documentation.
Day II
09:00am Briefly review the work of day
- Consolidate of existing gaps, and identify what work needs to be done, who will do it and by when
- Consolidate of existing gaps, and identify what work needs to be done, who will do it and by when
10:00am Define and agree the substantive red threads all proposals need (harmonize where possible, while not sacrificing the quality of the work).
- -After the discussion
- - Delete the elaboration of the discussion to writers
- - For common elements, agree graphics etc. and delegate to a group to work on
- - Review the above work
02:00pm Based on the earlier conversation
- Identify the gaps and weaknesses of each section of each country
- Identify what needs to be done in each section, develop a to-do list
- Delegate the work to groups and individuals, allowing the substance to be discussed by the writers.
- Give finished pieces to editors/ writers to
- Give feedback on draft changes
- Strengthen the language in agreed texts and reviewing the coherence of the documentation.
Day III
12:00pm Briefly review the work of day II
12:30pm Consolidate of existing gaps, and identify what work needs to be done, who will do it and by when
04:00pm Agree the outline of the budget of each proposal
Work on it in groups
Outcomes[edit | edit source]
- All the sections of the program document were reviewed, with the exception of three (achievements section, research questions and program coordination), by the team and passed on to James Stapleton for editing
- James Stapleton finished of the following sections: background, vision of success, theory of change, stakeholder engagement, scaling. Six sections remain to be finalized by 24 March COB: Moving to phase II, core principles, response to demand-driven research-in-development, Cross-cutting issues / higher level outcomes, M&E, and communications
- The overall structure of the regional proposals was discussed, tweaked and agreed.
- Regional issues relating to budget, common graphs and targets were discussed, as were the issues of program coordination and M&E
Next steps[edit | edit source]
28 March: Program proposal document edited (with the exception of the three missing sections)
28 March: comments received back on the program coordination document
29 March: Text on research questions produced
31 March: Comments back and text on research questions agreed
10 April: Regional target numbers finalized
15 April: Achievements and lessons learned section of the program proposal finalized
19 April: Program proposal documents edited
22 April: All regional documents finalized
25 April: Regional documents checked for coherence by CKM, and adjusted as necessary
05 May: All regional documents edited by respective centres
10 May: Program and regional documents sent to USAID
