ZICONNECT Project Charter
This project charter serves as a statement of scope and objectives for the Unicef Schools Connectivity project developed by Jobzi.
Document Created: 18/10/2022
Author: Jobzi Team
Document Revision History
| Revised By | Date | Comment |
|---|---|---|
| Armando Horie | 11/10/2022 | Concept of Unicef and Giga Project |
| Eduardo Laber | 14/10/2022 | Deliverable scope adjustments |
| Sergio | 26/10/2022 | Added new concepts prediction analysis |
| Tiagp Parra | 12/11/2022 | Added frontEnd frameworks |
| Mathues Werner | 12/11/2022 | Added backEnd frameworks |
| Frances Gomes | 16/12/2022 | Added gitHhub and devOps workflow |
| Start Date | End Date | Project Manager | Client |
|---|---|---|---|
1: Guiding Principles
This project-charter file provides the content and information necessary to identify the project in the context of its purpose, funding, resource requirements and approval. This document target audience is the major departmental stakeholders and decision makers in the leadership team.
2: Scope
Jobzi has a considerable knowledge and experience to provide AI NLP solution designed to guide, contribute and merge the Job and Education market. As a part of this experience we are helping the Unicef and Giga a platform and AI prediction models to identify Internet availability in Brazilian schools using geographical data and information on employability for the schools' region.
3: Relationship with Unicef Foundation and Giga Company
Additionally, we want to promote the Education towards employability, giving institutions the data and tools to improve their results. With Unicef Innovation Fund and Giga Project our objective it to leverage the inclusion of young people to better education and more opportunities through internet connectivity, as the world is facing a learning crisis.
3.1 Jobzi Commercial Solutions
Jobzi provides an unique AI NLP solution designed to merge Job and Education market in four solutions groups:
| Business Group | Data Crawling & Modeling | ATS SAAS Platform | Data Intelligence Provider | Career Center SAAS Platform |
|---|---|---|---|---|
| Jobzi Solution | Data Discovery & AI Special Projects | Job Portal & ATS Platform for HR process automation | API Solution for ATS, TMS and LMS | Platform for students, companies and educational institutions |
| Target Market | Eduaction & Financial | SMB Companies | HR, Learning and Upskilling Platform | Educational Institutions |
| Business Model | On Demand | On Hold ($ by Premium Plan) | $ by #API Request | $ by #Students |
We can have more Jobzi business model in (https://jobzi.com)
4: Unicef Project's Plan
The project's details and milestones were defined as follows:
-
Quarter 1
- Milestone 1 [Initial model to predict internet availability on Brazilian schools, based on information from GIGA (Backend and Frontend)]
- Data cleaning
- Additional geographical data acquisition
- Initial model evaluation
- Initial webpage with information on internet availability in Brazilian schools
- Milestone 2 [Updated model to predict internet connectivity on Brazilian schools, based on information from GIGA and on regional employability data (backend and frontend)]
- Data extraction
- Feature engineering
- Study of causuality between employability and connectivity variables via Bayesian networks
- Model testing
- Model selection
- Data summarizing
- Update webpage
- Milestone 3 [Cohort Product Development]
- Attend virtual technical product development session
- Milestone 4 [Communications and Branding]
- 1 image + caption per month to be shared on your social media channels
- 1 blog post at the beginning of the quarter
- Milestone 5 [Meeting Open Source Contractual Requirement]
- Determine licensing strategy for Open Source intellectual property (i.e. permissive or copyleft). Apply an Open Source Initiative-approved license to a public source code repository
- Create a project charter. Project charters should include: vision statement, mission statement, community statement, licensing strategy, and identification of key trademarks
- Create READMEs (in English) for all public repositories. READMEs should include: overview of specific repo, developer environment instructions (i.e. how to set software up), note about how repo connects into overall product, list of any Open Source software used to create product (including tools and frameworks)
- Create a public, standalone Open Source documentation website that corresponds to a public git repository. Use tools to set up automated deployments of HTML documentation site from public source code repository (e.g. with Continuous Integration)
- Follow the Pull Request Workflow when contributing code into your Open Source repositories.
- Milestone 1 [Initial model to predict internet availability on Brazilian schools, based on information from GIGA (Backend and Frontend)]
-
Quarter 2
- Milestone 1 [Updated model to predict internet connectivity on Brazilian schools, based on information from GIGA, regional employability data, and additional data from external sources , (backend and frontend)]
- Acquisiton of data from additional sources
- Feature selection
- Model testing
- Model selection
- Data summarizing
- Update webpage
- Milestone 2 [Meeting Open Source Contractual Requirement]
- MUST have a OSI-approved license distributed with public source code repositories by end of Q2
- Create contributing guidelines for all Open Source repositories. Explain how someone makes a contribution to the projects. Add to documentation website created in previous quarter
- Create public tickets/issues that correspond to planned features and known bugs/problems with Open Source repositories
- Establish an Open Source quality assurance process. Explore unit testing frameworks for front-end/back-end software, if applicable. Document user stories and test cases for games, if applicable. Document data structures and algorithm decisions for data science, if applicable.
- Add either developer or user documentation to the Open Source documentation site. (Hint: Developer docs often include API docs, architecture or system state diagrams, or deployment guides)
- Identify a Code of Conduct for any public Open Source repositories. Upload it to public source code repositories. Create internal documentation for how to respond to a Code of Conduct report, if one were to be made.
- Milestone 3 [Communications and Branding]
- 1 image + caption per month to be shared on your social media channels
- Milestone 1 [Updated model to predict internet connectivity on Brazilian schools, based on information from GIGA, regional employability data, and additional data from external sources , (backend and frontend)]
-
Quarter 3
- Milestone 1 [Investigation of the social impact of connectivity]
- Data Acquisition
- Exploratory analysis of data
- Investigation of social impact of connectivity via machine learning models
- Exibition of results in the Web Page
- Milestone 2 [Communications and Branding]
- 1 image + caption per month to be shared on your social media channels
- Milestone 3 [Meeting Open Source Contractual Requirement]
- Advance Open Source quality assurance. Set up a Continuous Integration / Continuous Deployment (CI/CD) pipeline from source code repository. Set up checks or tests on new Pull Requests. Target 40% code coverage, if applicable
- Use a public project management board to track progress on public tickets/issues (e.g. Taiga, GitHub/GitLab Projects, JIRA, Trello, or similar)
- Advance Open Source quality assurance. Target 40% code coverage for unit tests, if applicable
- Review compliance against DPG criteria and address any gaps
- Milestone 1 [Investigation of the social impact of connectivity]
-
Quarter 4
- Milestone 1 [Tool for studying the social impact of connectivity in schools]
- Component for data acquisiton
- Component with the analytical models
- Component for use interface
- Update webpage
- Milestone 2 [Communications and Branding]
- 1 image + caption per month to be shared on your social media channels
- 1 blog post at end of quarter
- Milestone 3 [Meeting Open Source Contractual Requirement]
- Finalize Open Source documentation. User and developer documentation should be available
- Finalize Open Source quality assurance. Achieve 80% code test coverage, if applicable
- Create "Good First Issues" for bite-sized, low-commitment contributions for new developers to make to your source code repositories.
- Establish a public communication platform for the public to interact with project development team. (Suggested: UNICEF Innovation Fund community forum.)
- Growth planning, contextual analysis, and focused support with Open Source Mentor
- Milestone 4 [Cohort Product Development]
- Attend virtual graduation
- Initiate submmission for the DPGA for consideration
- Milestone 1 [Tool for studying the social impact of connectivity in schools]
4.1 Scope
- NodeJS APIs to extend functionality in the Platform
- File-based and code-based configuration
- APIs ("interfaces") to write and organize tests written in JavaScript or compile-to-JavaScript languages
- Command-line executable to run tests in a Node.js-based terminal environment
- API to run tests in a browser environment
- Internal test coverage for all of the above
- Documentation including (but not limited to):
- Website (https://unicef.jobzi.com) contents and design
- Test-writing and test-organizing APIs
- Command-line execution and options
- Browser-based execution and options
- Project User Concept
- Contribution guide
- General support for multiple levels of tests, including (but not limited to):
- Unit tests
- Integration tests
- Functional/end-to-end tests
- Operational readiness tests
- Tool configuration for project tests, build, documentation or website deployment
- Angular and additional frameworks (e.g Karma), if needed
- Third-party service integrations (e.g., bots, CI servers, SCM)
- Project-endorsed spaces for collaboration (chat rooms, mailing lists, forums, etc.)
4.2 Out-Of-Scope
- Use within unmaintained versions of Node.js
- Use within browsers not meeting a threshold decided upon by maintainers
- Certain classes of contributions:
- Bug fixes or enhancements without associated test coverage
- Features having limited general-purpose use (as determined by maintainers)
- Bug fixes which "break" more users than are affected by the bug itself, regardless of "correctness"
- Breaking changes to API without demonstrated need, especially those which would cause correct, currently-passing tests to fail
- Changes that significantly negatively impact performance without demonstrated need
- Code reviews, issue comments or pull requests which are dogmatic, demanding, or excessively critical as to discourage contributions by others
- Those which violate the Jobzi's [Code of Conduct]
5: Roles & Responsibilities
The roles and responsibilities of Unicef Schools Connectivity's maintainers are described in [CONTRIBUTING.md].
5.1: Project Operations & Management
Project operations and processes are described in [CONTRIBUTING.md].
5.2: Decision-making, Voting, and/or Elections
Jobzi uses a loose consensus-seeking process, described in [CONTRIBUTING.md].
6: Definitions
- UNICEF: https://www.unicef.org/
- GIGA Company: https://giga.global/
- CONTRIBUTING: https://github.com/Jobzi-Artificial-Intelligence/unicef-project/blob/master/CONTRIBUTING.md
- CODE_OF_CONDUCT: https://github.com/Jobzi-Artificial-Intelligence/unicef-project/blob/master/CODE_OF_CONDUCT.md