| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ||||||||||||||||||||||||||
2 | Company name: | Company X (Blockchain Cohort) | ||||||||||||||||||||||||
3 | ||||||||||||||||||||||||||
4 | Timeline | Tasks | Budget (ETH) | Expected Changes/Targets | Signs of Success | Key Personnel Responsible | ||||||||||||||||||||
5 | What are the major milestones you will achieve with the UNICEF Innovation Fund investment? Which activities do you need to do to achieve each milestone? Adjust the number of milestones and activities for each quarter as needed. | What will be different once the activity is done? (Provide specific numbers where possible.) | What will you measure/look at to assess if you completed the activity? And whether you achieved your desired outcome? Please specify the numeric values of your desired outcomes [ie.number of users]. Each activity must have at least one. | Which team member is responsible for each task? Refer to the funding agreement for the definition of 'Key Personnel" and who can be included on this list. | ||||||||||||||||||||||
6 | Quarter 1 | 4.4303 | User tests | |||||||||||||||||||||||
7 | Milestone 1 | Team expansion preparation | 0.3819 | |||||||||||||||||||||||
8 | Activity 1 | Frontend refactoring and migration to framework Nextjs. | Rendering and SEO optimization. Code modularization to prepare scalability. | Functionality with new framework is the same or improved as on previous version. | ||||||||||||||||||||||
9 | Activity 2 | White paper draft. | The whitepaper draft is available in the landing website. | The whitepaper draft is available in the landing website | ||||||||||||||||||||||
10 | Activity 3 | Onboarding documentation with best practice examples for new team members. | Document available on the team drive with onboarding info | Document available | ||||||||||||||||||||||
11 | ||||||||||||||||||||||||||
12 | Milestone 2 | ROSCA business logic implementation | 1.9096 | |||||||||||||||||||||||
13 | Activity 1 | Definition of the ROSCA basis rules. This includes registration process, payment and widthraw days and late payment management. | The ROSCA rules available in the landing website. | Rules available | ||||||||||||||||||||||
14 | Activity 2 | Basis rules coding on the smart contract. | 100% of the defined rules are coded into a function on the smart contract. | 100% of the defined rules | ||||||||||||||||||||||
15 | Activity 3 | Smart contract unit testing. | Code and functinality verificaton. | 80% coverage | ||||||||||||||||||||||
16 | Activity 4 | Frontend: Show the cards related to the only to the functions that the user will use at each stage of the round to avoid reverted transactions. | The user will be prevented from excecuting functions that may result in revert or dispay an alert on Metamask. | The user will not be able to excecute 80% of functions that may result in revert | ||||||||||||||||||||||
17 | Activity 5 | Frontend: Display information so the user knows the status of the round (current turn, user's turn, payment dates and widthraw dates). | 100% of the variables are displayed on the frontend | 100% of the variables are displayed on the frontend | ||||||||||||||||||||||
18 | Activity 6 | Frontend: Add connect wallet botton. | The page is displayed even though there is no wallet connected. Connect button is displayed | Button implemented | ||||||||||||||||||||||
19 | Activity 7 | Frontend: add sidebar with admin functions. | All of the admin functions are added to a sidebar only visible by admin. | 100% of admin functions added to the sidebar | ||||||||||||||||||||||
20 | Activity 8 | Front end unit testing. | Code and functionality verificaton. | 80% coverage | ||||||||||||||||||||||
21 | Activity 9 | Run acceptance test. | High level functionality verification. | Passed test | ||||||||||||||||||||||
22 | Activity 10 | Create feedback survey. | Create form for testers to give feedback | Form available | ||||||||||||||||||||||
23 | Activity 11 | Run user trial | User trial of 5 rounds with 4 to 6 users each (20-30 users total) | min. 20 users | x | 20 | ||||||||||||||||||||
24 | Activity 12 | Define backlog according to user feedback | Backlog defined and available in Jira (or equivalent). | min. 5 issues in backlog | ||||||||||||||||||||||
25 | ||||||||||||||||||||||||||
26 | Milestone 3 | Blockchain strategy | 0.4582 | |||||||||||||||||||||||
27 | Activity 1 | Review gasless transactions implementation options. | Review options. | Get a quantified score for each option in order to decide | ||||||||||||||||||||||
28 | Activity 2 | Define strategy to cover gas fees with low impact to user to improve onboarding of non crypto users | Explore options to cover the costs of gas(fees, donations...) | min. 2 options documented | ||||||||||||||||||||||
29 | Activity 3 | Review 3rd generation blockchain options | Compare blockchains available. | Get a quantified score for each option in order to decide | ||||||||||||||||||||||
30 | ||||||||||||||||||||||||||
31 | Milestone 4 | Security audits | 0.4584 | |||||||||||||||||||||||
32 | Activity 1 | Manual Smart contracts security analysis. | Identify smart contract vulnerabilities. With support of Blockchain Academy Chile | Vulnerabilities identified and added to backlog | ||||||||||||||||||||||
33 | Activity 2 | Smart contracts Testing coverage. | Make shure most of the functions are evaluated on the unit tests | Testing coverage 80% | ||||||||||||||||||||||
34 | Activity 3 | Frontend code quality analysis. | Identify frotend vulnerabilities | Vulnerabilities identified and added to backlog | ||||||||||||||||||||||
35 | Activity 4 | First round audit report analysis | Quality verification | Report available | ||||||||||||||||||||||
36 | Activity 5 | First round audit fixes. | Ensure quality | 50% of findings fixed | ||||||||||||||||||||||
37 | ||||||||||||||||||||||||||
38 | Milestone 5 | Cohort Product Development | 0.0000 | |||||||||||||||||||||||
39 | Activity 1 | Attend virtual technical product development session. | The team will get guidance to develop a useful and helpful product. | 75% of the team to attend event. | ||||||||||||||||||||||
40 | ||||||||||||||||||||||||||
41 | Milestone 6 | Communications and Branding | 0.3819 | |||||||||||||||||||||||
42 | Activity 1 | 2 image + caption per month to be shared on social media channels | Show the product we are developing to possibe users and possible testers. | 6 image + caption min. shared on social media, track the information thrown and use it to reach more communities. | ||||||||||||||||||||||
43 | Activity 2 | 1 blog post at the beginning of the quarter | Share with blockchain and entrepenuership communities the objective of our development and the support received by UNICEF. | 1 blog post - Track the comments on the post, collect information that helps to build a better product and to consider improvements. | ||||||||||||||||||||||
44 | Activity 3 | Landing page data analysis | Import data on the landing page to get to know our possible testers and users. | Demographic information. | ||||||||||||||||||||||
45 | ||||||||||||||||||||||||||
46 | Milestone 7 | Meeting Open Source Contractual Requirement | 0.8403 | |||||||||||||||||||||||
47 | Activity 1 | 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. | Licensing strategy defined. | Licence applied to repository. | ||||||||||||||||||||||
48 | Activity 2 | 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). | The development enviroment is clearly defined so others can contribute. | Readme available in public repository. | ||||||||||||||||||||||
49 | Activity 3 | Create a public Open Source documentation with a corresponding public source code repository. Use automation tools to set up automatic deployments of HTML documentation site from public source code repository (e.g. with Continuous Integration). | Ensure the good use of the public repository. | Documentation site is available, 10% of documentation available. | ||||||||||||||||||||||
50 | Activity 4 | 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. | Code and functinality verificaton. | One unit testing implemented | ||||||||||||||||||||||
51 | Activity 5 | 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. | Ensure the good use of the public repository. | Code of conduct available in repository | ||||||||||||||||||||||
52 | Activity 6 | Follow the Pull Request Workflow when contributing code into your Open Source repositories. | The updates are done in a systematic way | Pull requests | ||||||||||||||||||||||
53 | ||||||||||||||||||||||||||
54 | Quarter 2 | 4.7358 | 6 | |||||||||||||||||||||||
55 | Milestone 1 | Multiple round management | 1.8332 | |||||||||||||||||||||||
56 | Activity 1 | Code factory pattern smart contract with a function that returns the users created rounds. | This will allow users to create a round defining size and saving amount. Also the smart contract allows the user to get the addresses of their created rounds. | The factory pattern smart contract is able to create rounds and return users created rounds | ||||||||||||||||||||||
57 | Activity 2 | Factory pattern unit testing. | Code and functionality verificaton. | 80% coverage | ||||||||||||||||||||||
58 | Activity 3 | Code the dapp home page to interact with the factory pattern smart contract. | Allow users to interact with the factory pattern smart contract. | A round can be created from the frontend | ||||||||||||||||||||||
59 | Activity 4 | Enable the function for viewing created rounds on the home page. | Display the created rounds. | The users created rounds can be viewed in the frontend | ||||||||||||||||||||||
60 | Activity 5 | Enable round access through a URL related to the smart contract addres of each round | The users will be able to acces the round they are participatin in through this URL | All rounds can be accessed through a unique URL | ||||||||||||||||||||||
61 | Activity 6 | Home page unit testing | Code and functionality verificaton. | 80% coverage | ||||||||||||||||||||||
62 | Activity 7 | Implement a backend to store users, rounds and e-mails. | This is a preparation for notifications and regulatory compliance. | The data in the backend is equal to the smart contract | ||||||||||||||||||||||
63 | Activity 8 | Run acceptance test. | High level functionality verification. | Passed test | ||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | Milestone 2 | Notification handling | 0.7638 | |||||||||||||||||||||||
66 | Activity 2 | Enable e-mail notifications for payment date reminders. For the test the notifications may be sent manualy | This will help us test the type of notifications the users require. | 80% of payment notifications are sent | ||||||||||||||||||||||
67 | Activity 4 | Run acceptance test | Passed test | Passed test | ||||||||||||||||||||||
68 | Activity 5 | Create feedback survey | Create form for testers to give feedback | Form available | ||||||||||||||||||||||
69 | Activity 6 | Run user trial. | Test with 50-100 users, some of the users may be the same as in previous test. | min. 50 users | x | 50 | ||||||||||||||||||||
70 | Activity 7 | Define backlog according to user feedback | Backlog defined and available in Jira(or equivalent) | min. 5 issues in backlog | ||||||||||||||||||||||
71 | ||||||||||||||||||||||||||
72 | Milestone 3 | Blockchain strategy | 0.3055 | |||||||||||||||||||||||
73 | Activity 1 | Create user documentation to explain the process to add tokens to the wallet | This will help with the onboarding | User guide available | ||||||||||||||||||||||
74 | Activity 2 | Explore tokens to be used on the dapp(native token, stablecoin, own token...) | Evaluate token options according to the selected bloxkchain. | Token definition for each stage. | ||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | Milestone 4 | Security audits | 0.6111 | |||||||||||||||||||||||
77 | Activity 1 | Manual Smart contracts security analysis | Identify smart contract vulnerabilities. With support of Blockchain Academy Chile | Vulnerabilities identified and added to backlog | ||||||||||||||||||||||
78 | Activity 2 | Smart contracts Testing coverage. | Make shure most of the functions are evaluated on the unit tests | Testing coverage 80% | ||||||||||||||||||||||
79 | Activity 3 | Frontend analysis quality code. | Identify frotend vulnerabilities | Vulnerabilities identified and added to backlog | ||||||||||||||||||||||
80 | Activity 4 | Second round audit report analysis. | Quality verification | Report available | ||||||||||||||||||||||
81 | Activity 5 | Second round audit fixes. | Ensure quality | 65% of findings fixed | ||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | Milestone 5 | Meeting Open Source Contractual Requirement | 0.8403 | |||||||||||||||||||||||
84 | Activity 1 | MUST have a OSI-approved license distributed with public source code repositories by end of Q2. | Licensing defined for open source use of our solution. | Licensing approved. | ||||||||||||||||||||||
85 | Activity 2 | Create contributing guidelines for all Open Source repositories. Explain how someone makes a contribution to the projects. | Ensure the good use of the public repository. | Contribution guidelines available in repository | ||||||||||||||||||||||
86 | Activity 3 | Create public tickets/issues that correspond to planned features and known bugs/problems with Open Source repositories. | Make the planned improvements known to the community | 90% of the open activities in the backlog available on public project management tool | ||||||||||||||||||||||
87 | Activity 4 | Use a public project management board to track progress on public tickets/issues (e.g. Taiga, GitHub/GitLab Projects, JIRA, Trello, or similar). | Enable feedback from the community | Tool to manage public tickets/issues set up. | ||||||||||||||||||||||
88 | Activity 5 | 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.) | Provide technical information to other users/developers so they can make use of the solution. | Documentation of current features available | ||||||||||||||||||||||
89 | Activity 6 | Advance Open Source quality assurance. Target 15% code coverage for unit tests, if applicable. | Code and functinality verificaton. | min. 15% of unit tests performed | ||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | Milestone 6 | Communications and Branding | 0.3819 | |||||||||||||||||||||||
92 | Activity 1 | 2 image + caption per month to be shared on your social media channels | Let communities know the product we are developing and share improvements made on the first quarter | 6 image + caption min. shared on social media - recollect user information and data analysis | ||||||||||||||||||||||
93 | Activity 2 | 1 blog post at the beginning of the quarter | Share with users the objective of our product bringing up topics related to entrepreneurship, fintech, new developments | 1 blog post - track the comments on the post, collect information that helps to build a better product and to consider improvements | ||||||||||||||||||||||
94 | Activity 3 | Landing page and social media data analysis | Use the data recollected on the 1st quarter to connect with a new social media or channels to share information | 1 new channel/social media/forum to share the product | ||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | Quarter 3 | 4.7358 | 6.2 | |||||||||||||||||||||||
97 | Milestone 1 | Blockchain strategy | 0.6111 | |||||||||||||||||||||||
98 | Activity 1 | Integrate the selected token (if applicable). | Create smart contracts of add existing token | Dapp functions with the selected token | ||||||||||||||||||||||
99 | Activity 2 | Integrate gasless transactions(if applicable). | The onboarding for users new to crypto is improved | No gass is charged to the user | ||||||||||||||||||||||
100 | ||||||||||||||||||||||||||