SWHISA: Introducing a team- based implementation approach Presentation on the Annual Work planning session 05-06, 2009 Bahir Dar Dereje Biruk, ATL

Why we need an improved approach? Group Vs Teams In this 5th year Woredas are going to carry much of the onus of implementation Smooth phasing out is necessary PSC decisions in favor of more shift to Woredas Woredas prefer a team of experts than individuals

What is the new proposal? Four Teams are proposed Water Harvesting, WHE Agricultural Extension, AEE Watershed Management, WME Irrigated agriculture research, IME Teams are not hierarchical Teams have an assigned leader and members

What is expected of each team? Define goals and purposes Define its own modes of operandi (date of regular meetings, reporting requirements for each team member to use…) Define its internal strategy to interact with partner institutions and woredas Hold regular team meetings, pass decisions and report to management Quarterly plans and budget and submits to management for implementation upon approval

Plans team-travels to Woredas (as may be required), Undertakes regular and pre-planned technical support to woredas Reports as a team (quarterly as well as field reports) Takes the team’s activities as one whole unit, as opposed to a collection of fragmented activities merged together mechanically Collaborative experts (GEE; TRG; MIS, M&E) work with the appropriate teams as required

Roles of Woreda Coordinators: changes from implementers to mentoring and following up Careful monthly planning of activities less external travels and more resources to the woredas including the use of the vehicle exclusively and strictly for implementation of SWHISA targets within the woreda Follow up and support the relevant process owners in the timely implementation of activities Manage some activities to be implemented directly by the project (study tours, some trainings by SWHISA teams…) Detail Tasks are defined and sent to coordinators

Time to start: All the tasks expected of the teams shall be submitted before 15 August (goals and purposes, modes of operandi, its internal strategy to interact with PIs and Woredas Teams prepare and submit their September plan by August 27/097

END