Project Life Cycle
Revision as of 12:38, 27 June 2020 by Natkeeran (talk | contribs) (Natkeeran moved page Template:Project Life Cycle to Project Life Cycle)
- Noolaham Foundation and relevant volunteers or stakeholders identify a project.
- Noolaham Foundation prepares a proposal document (Annex 5) which consists of Background and objectives, Target and Results, Justification, Beneficiaries, * Implementations, Budget, Work plan, and required annexure.
- The proposal is forwarded to management for assessment and approval by the Program Officer.
- The proposal is then submitted to the Governance Board for review and approval.
- If donors agree, an agreement should be signed between the Noolaham Foundation and donor agency.
- A more detailed Project Management Plan must be developed by the Program Officer extending the proposal. This plan must be approved by the Chief Operating Officer.
- As a general rule, Noolaham Foundation will do the procurement for projects. If any exceptions are to be made, the implementing agency should consult the Operations Unit in Noolaham Head Office.
- Funds shall be released to the implementing agency or obtained from donor agency as per agreement and against the milestones and deliverables. Generally, minimum 50% of the funds should be released before the project can commence.
- Project Status Updates must be submitted weekly to the Program Manager. Project Update Report must be submitted monthly on an agreed upon frequency by the Chief Operating Officer to the relevant stakeholders.
- After the close of the project, a Project Post-Mortem meeting should be held within one month with all stakeholders. The Lessons Learned and/or Learning Patterns should be documented in the Final Project Report.
- The Final Project Report must be submitted and approved by the Governance Board within three months.