# Welcome! Welcome to the RIL Handbook! If you are a new starter, this page will help highlight some of the most important things you should know about working here. At Renaissance Innovation Labs, we find the smartest people, provide them with the right tools for success, and generate innovative solutions for individuals, industries and organizations. # Mission, Vision & Focus ## Our Vision {% hint style="success" %} Our singular vision is to build a company capable of redefining our society and communities for the better. {% endhint %} ## Our Mission {% hint style="success" %} Our mission is to move people forward through social, economic, and technological progress. We’re enabling a culture of orchestrated development that supports technology enthusiasts, aspiring entrepreneurs, and well-meaning individuals and organizations in the quest to redefine our society and communities for the better. {% endhint %} ## Our Focus {% hint style="success" %} We facilitate technological experiments from ideation to formation of business units, and translate solutions to enterprise. We find areas right for disruption by engaging diverse participants in open collaboration. These participants (innovators) are taken through a guided learning process that equips them with the requisite knowledge and skill for progress. Together, we’re able to engineer innovative prototypes and explore opportunities with contributors, mentors, and sponsors. We take on challenges too big for one organization by engaging diverse participants to create, elaborate, and prototype disruptive solutions. {% endhint %} # Values ## Our Values
🚀 Integrity and Trust In order to ensure we achieve our goals, we appreciate integrity as this builds trust.
♾️ Collaboration We understand the importance of working together to achieve common goals.
💪 Excellence and Quality We apply our expertise to ensure excellence in all endeavors, going above and beyond the normal
💻 Innovation We are always looking for new ways to solve problems.
🧑‍🤝‍🧑 Community We rise by lifting others, RIL focuses on having as many people with like minds and visions working with us as possible.
🪴 Growth Every member of our community is expected to show improvement as they spend time with us.
# What we do Our experienced team of experts are dedicated to providing top-notch solutions in areas such as application development, product analysis, cloud infrastructure, machine learning, design, branding, customer support, social media management, and strategic marketing.
💿 Product Lab Our team of experts utilizes cutting-edge technology and collaborative processes to prototype, iterate, and bring exceptional products to life.
🎨 Design Lab Unleash creativity and innovation in our Design Lab, where ideas come to life through stunning visuals and transformative experiences
👩‍🏫 Learn with RIL Our BootCamp connects young innovators and provides them with technological and business insights while collaborating on globally significant projects.
🏢 Innovation Workspace This initiative aims to attract and engage tech enthusiasts by offering them free access to our space. The goal is to use this opportunity to identify and integrate committed individuals into the Innovation Lab, fostering a community of innovators who actively work on impactful projects.
# Our Story ## 2019 Joseph, a visionary entrepreneur, saw an unsettling pattern in the place he called home in 2019. Despite the plethora of young minds with enormous potential, only a select few were fortunate enough to have access to opportunities that would foster their development and allow them to explore their creative ideas. Joseph decided to take action because he had a desire to make a difference. Out of this pressing need, our remarkable organization was born: Renaissance Innovation Labs (RIL). Our goal was to empower young talent and give them the tools and encouragement they need to reach their greatest potential. RIL embarked on a mission that would change lives and influence the future with the goal of encouraging innovation and building a healthy ecosystem for young minds. {% tabs %} {% tab title="We Gave Back" %} RIL collaborated with other like-minded tech communities in Port Harcourt the same year it was founded, recognizing the value of collaboration in pushing change. We collaborated on an amazing project: the international space apps challenge. This global event gave aspiring innovators and developers a forum to display their skills and ideas, with a particular emphasis on space-related concerns. {% endtab %} {% tab title="Collaboration" %} RIL collaborated with other like-minded tech communities in Port Harcourt the same year it was founded, recognizing the value of collaboration in pushing change. We collaborated on an amazing project: the international space apps challenge. {% endtab %} {% endtabs %} *** ## 2020 RIL's relentless commitment to revolutionizing the African tech space has led to ground-breaking inventions, the development of local talent, and partnerships that genuinely address the most pressing issues facing the continent. RIL has established itself as a key player in Africa's tech revolution by making investments in the continent's inventors, building alliances, and creating cutting-edge technologies. The organization envisions a future where technology plays a revolutionary role in uplifting communities and realizing Africa's full potential as it continues to push boundaries and explore new territories. Be a part of Africa's tech revolution right now by venturing with RIL on this inspiring journey. {% tabs %} {% tab title="Nurturing Local Talent" %} RIL is aware of the enormous potential of local talent to advance technology in Africa. RIL has built strong programs targeted at enabling and fostering African entrepreneurs through strategic investments. These programs, which include training seminars, mentorship programs, and scholarships, allow people to advance their education and contribute to the expansion of the tech sector. {% endtab %} {% tab title="Excellence" %} One company stands out in the bustling environment of Africa's tech industry for its unwavering commitment to modernize the sector with disruptive innovations and solutions. We’ve become a change agent, spending extensively on nurturing local talent, encouraging collaborations, and generating ground-breaking products that address Africans' genuine needs. {% endtab %} {% endtabs %} *** ## 2021 Our fellowship program was launched in 2021 with the intention of promoting creativity and developing young minds. We gave these brilliant individuals a platform to realize their potential and have a positive effect in their respective fields through an intense training program. Our fellowship program gave students access to industry experts as well as technical training, allowing them to learn from seasoned professionals. Their success was built on a special blend of instruction and mentoring. The accomplishments of our graduates clearly demonstrate the success of our fellowship program. Several of these young innovators are now working for major international partner organisations. {% tabs %} {% tab title="Our Pride " %} In 2021, we embarked on a groundbreaking journey to empower young innovators through our fellowship program. We gave extensive training and essential tools to over 25 young people in order to combine and nurture their skills. We are proud of their achievements today, as they lend their skills to international partner organizations. {% endtab %} {% tab title="Transforming Industries" %} In addition to our fellowship program, we concentrated on developing ground-breaking products that tackle contemporary issues. These innovative solutions are transforming numerous sectors and bringing about significant change. {% endtab %} {% endtabs %} *** ## 2022 Our focus was perked up to accommodate our vision; “To be the center of activities for the technology community in Port Harcourt, Rivers State and Nigeria, driving innovation and community development in all areas of the modern world.” . We were keen on seeing our vision through by seizing our core values. * Collaboration * Community * Integrity & Trust * Growth * Innovation * Excellence & Quality {% tabs %} {% tab title="Motion Design Exp" %} The year paced up rather quickly and we had our first event in June. Motion design experience(MDX) which was held on the 30th of June was a partnered event with the motion design community in Port Harcourt. As one of the biggest tech events in Port Harcourt this year, here’s what some of the attendees had to say about it. {% endtab %} {% tab title="Summer Class" %} RILearn's commitment to nurturing tech talents extends beyond professionals. In 2022, through our Kids in Tech programs, RILearn has ignited the passion for technology in 11 young teens and children. These engaging and educational initiatives provide a safe and supportive environment for youngsters to explore coding, robotics, and digital creativity, empowering them to become the innovators of tomorrow. {% endtab %} {% tab title="Bootcamp" %} At the heart of RILearn's success lies the transformative RILearn Bootcamp. Designed for aspiring professionals, this intensive program provides hands-on training, equipping participants with cutting-edge tech skills and real-world experience. With an impressive track record of 15 successful graduates in 2022, the bootcamp has become a launchpad for tech enthusiasts, propelling them towards rewarding careers in the industry {% endtab %} {% tab title="React Meetup" %} The React Event organized by RILearn is a gathering of web development enthusiasts. With keynote speakers, interactive workshops, and networking opportunities, this event provides participants with insights into the world of React and empowers them to build scalable and interactive web applications. React Event has become a must-attend occasion for developers looking to stay at the forefront of web development {% endtab %} {% tab title="RIL Discuss" %} Recognising the need for professional growth and continual learning, RILearn established RILdiscuss, a vibrant online community. RILdiscuss is a platform for tech enthusiasts to network, share insights, and have meaningful conversations. Members gain access to industry experts, mentors, and a plethora of tools, fostering a professional growth and cooperation atmosphere. RIL has made a lasting impact on the tech talent market with our extensive RILearn programs, fun tech events, and vibrant online communities. With a track record of accomplishment, RIL continues to empower people of all ages and backgrounds and open the door for a better, more creative future. {% endtab %} {% endtabs %} *** ## 2023 2023: Laying the Foundation for Community and Innovation In 2023, Renaissance Innovation Labs focused on fostering community collaboration, encouraging innovation, and introducing young minds to technology: {% tabs %} {% tab title="Bootcamp/Understudy " %} Successfully planned and executed two boot camp cohorts with participants seamlessly transitioning into internship and understudy programs within the organization. We had 6 registered participants for each cohort. We also had some out-of-season participants who paid for individual sessions. {% endtab %} {% tab title="Summer Class" %} Hosted the second edition “Kids Can Tech” Summer Class focusing on Front-End Engineering and Product Design. Notably, parents demonstrated commitment with positive reviews and promised to return their children for advanced classes. A total of 9 kids participated in the program. {% endtab %} {% tab title="RILDiscuss" %} In collaboration with the PR department, we planned and hosted five (5) Twitter space conversations with an average attendance of 80, that engaged the tech community through insightful discussions, attracting numerous tech enthusiasts, fostering a sense of community and connecting experts and newbies. {% endtab %} {% endtabs %} {% tabs %} {% tab title="Advanced Class" %} Conducted an advanced class on React and Test Driven Development, enhancing the skills of participants and keeping the PH React community updated on cutting-edge technologies. {% endtab %} {% tab title="Community Collaboration" %} Established partnerships with three (3) tech communities to foster collaboration and knowledge sharing. This led to us hosting the meetups for open-source writing. Worthy of note is our presence at major tech events in the city. {% endtab %} {% tab title="Tech Founders Meetup" %} We hosted an ecosystem-building meetup that brought together key stakeholders in Port Harcourt’s tech space to discuss growth, challenges, and opportunities for collaboration. It strengthened local connections and sparked new partnerships. {% endtab %} {% endtabs %} PRODUCTS {% tabs %} {% tab title="Le Pole" %} The successful development and deployment of LePole marked a milestone for our team. This project showcased our commitment to innovation and our ability to deliver cutting-edge solutions. The positive feedback received from clients reaffirms our dedication to producing high-quality software that meets and exceeds customer expectations. {% endtab %} {% tab title="Headless HR" %} This was a project born out of an in-house problem we faced, we developed an internal tool which we had been using. We created a public version of the project for others who had similar issues. The project is still in use and has received some positive feedback. {% endtab %} {% tab title="Booking Widget" %} The introduction of the Booking Widget has proven to be a valuable addition to our product suite. This tool enhances scheduling efficiency for our clients, offering a user-friendly solution that streamlines appointment bookings. We aim to have this work as a service tool for users or sell the project for the right price. {% endtab %} {% endtabs %} INHOUSE TRAINING Trainings were organized in-house to improve the skills and processes of the team, among these are: Test-driven development, Agile project development, Advanced JavaScript and Typescript training. *** ## 2024 Expanding Training and Strategic Partnerships: Building on the momentum of 2023, we scaled our impact in 2024 by launching more structured training programs and entering into larger ecosystem partnerships: {% tabs %} {% tab title="Tech Bootcamp" %} We trained 12 participants across Web Development, Product Design, and Data Analysis. The program combined practical training with mentorship, enabling participants to build portfolio-ready projects. {% endtab %} {% tab title="Understudy Program" %} Through three batches, we mentored early-stage tech enthusiasts by assigning real projects, organizing practical sessions, and strengthening their soft skills. Some participants secured jobs and freelance opportunities upon completion {% endtab %} {% tab title="TerraExpo Partnership" %} We partnered with TerraExpo to host Africa’s largest AI and Drone event. With hundreds of attendees, this event positioned Port Harcourt on the map as a growing hub for emerging technologies and reinforced our role as ecosystem enablers. {% endtab %} {% endtabs %} *** ## 2025 Deepening Inclusion, Access, and Empowerment: This year has been focused on empowering underrepresented groups, offering inclusive access to innovation, and fostering community-led growth: {% stepper %} {% step %} Strategic Partnership We partnered with She Code Africa to co-host their International Women’s Day (IWD) celebration and collaborated with Techrity on a tech mentorship initiative. These partnerships strengthened support systems for women and early-stage tech talents. {% endstep %} {% step %} Our Own International Women’s Day Event We organized a dynamic IWD event that brought together 32 women, featuring partners like Droomwork, She Code Africa, and Techrity. It deepened community ties, provided empowerment-focused sessions, and offered a safe and joyful space for growth, learning, and networking. {% endstep %} {% step %} Free Space to Innovate Initiative We opened our lab to the public, offering free access to electricity, internet, and workspace. This initiative supported over 20 people, freelancers, students, and creators, many of whom have shared positive feedback on how this support helped them work better and faster. {% endstep %} {% endstepper %} # Meet the Team! {% hint style="success" %} We are a team of strong result-oriented individuals who believe in innovation and tackling problems we face in society today one line of code at a time {% endhint %} ## Joseph Akintolayo 👋 Executive Chairman, CEO ![](https://1273691976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2Jhm6EX5lOXlhMqPc1YT%2Fuploads%2FWyhJsjteB6ZTAuGJCW0l%2Fjoseph.webp?alt=media\&token=247e7438-1db7-48ba-9df2-510af1169b05) ### Bio {% hint style="info" %} Founder, CEO | Renaissance Innovation Labs | Deposits — I build ethical products that solve complex problems in Fintech, InsurTech & Social Enterprise. {% endhint %} ## Shammah Nei 👋 Managing Director ### Bio {% hint style="info" %} Shammah Nei is a First Class graduate of Microbiology, at the University of Port Harcourt. Having helped teams create products ranging from static sites, and e-commerce platforms to transport apps and others, occupying front-end developer roles in various tech firms and working as a lead front-end developer and CTO for multiple projects. Using ReactJs, NextJs, as well as other technologies. Currently working as Director for two tech companies, leading the teams in both technical and management roles. Also volunteers as a mentor to beginner and junior developers and teenagers, helping them do better academically and training those interested in the tech world to start a career. {% endhint %} ## Ajie Bliss Isioma Adaego 👋 Chief of Operations ### Bio {% hint style="info" %} Strategic and impact-driven Chief Operations Officer at Renaissance Innovation Labs with a multidisciplinary background spanning operations management, human resources, program management, project delivery, and product development. Experienced in building scalable operational systems, leading cross-functional teams, managing innovation programs, and driving organisational growth through people, processes, and technology. Bliss brings a strong foundation in talent strategy, business operations, stakeholder management, and execution frameworks, with proven experience improving operational efficiency, launching initiatives, developing teams, and implementing systems that support sustainable growth. Passionate about building high-performing organisations by aligning people, products, and processes with business objectives.
{% endhint %} ## Lydia Odji 👋 Program/Partnership Manager
### Bio {% hint style="info" %} Lydia O. Odji is a Communications and Programme Management professional with over three years of experience coordinating impactful initiatives across the innovation, education, and nonprofit sectors.\ As a Programmes Associate at Renaissance Innovation Labs, she leads programme planning, stakeholder engagement, strategic communications, and partnership coordination to ensure successful project delivery and community impact. Lydia has extensive experience developing communication materials, managing events, facilitating workshops, and building relationships with partners, beneficiaries, and community stakeholders. A confident public speaker, she has empowered over 400+ secondary school students through leadership and career development sessions and is passionate about using effective communication and well-executed programmes to drive sustainable social change. {% endhint %} ## Chidera Prince Basil 👋 Brand & Product Manager
### Bio {% hint style="info" %} "Chidera Prince Basil is a Brand and Product Designer with over five years of experience helping organizations build brands, design digital products, and communicate their ideas effectively. He studied Petroleum Engineering at the Federal University of Technology, Owerri (FUTO), and has built a career at the intersection of design, technology, and business. His experience covers brand identity, product design (UI/UX), marketing design, motion graphics, and visual communication across industries including technology, healthcare, education, logistics, fintech, Web3, real estate, and social impact. He has worked with startups and growing organizations to create products, campaigns, and experiences that have reached users across multiple countries. As PR and Communications Lead at Renaissance Innovation Labs, Chidera leads the organization's brand and communications efforts, helping showcase its programs, build strategic partnerships, and engage communities through technology and innovation. He is passionate about using design to solve real problems, simplify complex ideas, and create products and experiences that people genuinely enjoy using." {% endhint %} ## Michael Eyitayo 👋 Engineering Lead/Backend Developer
### Bio {% hint style="info" %} I am a software developer with web knowledge in systems architecture and infrastructure experience, I actually started coding with my cellphone back in 2018, before I could eventually afford a laptop. I posses the ability to learn, unlearn and re-learn. I am also continuously learning and improving my skills as I hope to grow in the DevOps role, learning technologies likes, Docker and Kubernetes. {% endhint %} ## Ayanfe Daniel 👋 Frontend Developer
### Bio {% hint style="info" %} Frontend Engineer with 4+ years of experience building responsive, high-performance web applications using React, Next.js, Vue.js, and TypeScript. Passionate about clean code, scalable systems, and delivering excellent user experiences. {% endhint %} # Company Standard ## Company Policies ➲ **Anti-Discrimination Policy -** We Frown at Discrimination of any sort. We promote an environment where everyone is seen as equal, despite your Tribe or Belief. ➲ **Anti-harassment Policy -** Endeavor to Always maintain proper decorum and conduct yourself in a manner that contributes to operation, effectiveness, productivity, safety, and a harmonious work environment. Any sort of Harassment, would result in immediate termination of appointment. ➲ **Work Hours, Attendance and Leave Policy -** {% hint style="info" %} Work resumes by 9:00a.m and closes by 5:00 pm Mondays through Friday which amounts to 8 hours a day and 40 hours a week. \ If for any reason you would be Late, a prior notice should be given to the Human Resource Manager, and if for any reason you would be absent, an official email should be sent to the HRM, stating the reason for your absence. {% endhint %} {% hint style="danger" %} Any recurring lateness or absence without due permission, would result in a severe punishment from the Management. Endeavor to Sign In and Out Daily. Any Staff in this Category is expected to prepare a well documented letter/mail seeking approval and reasons for Leave and expected return date. E-mails should be sent to and CC: Head of Department and - The Director RIL. {% endhint %} ➲ **Health and Safety Policy -** You must; work within a healthy and safe workplace. No smoking and drinking of alcohol during work hours. Avoid every act or practices that may be hazardous to your colleagues and the environment. Say no to Unsafe Acts and Unsafe Practices. In a case of Emergency or Outbreak, all Staff are expected to calmly proceed through the nearest exit, and assembly at the Muster Point(The Gate), and await further instructions. ➲ **Employee Conduct and Performance -** We carry out a Monthly Performance Appraisal for both Personnel and Managers appraisal. ➲ **Immediate Employment Termination -** An employees contract would be terminated immediately in the case of Consistent Insubordination, Theft, Harassment. ➲ **Conflict Resolution & Complaint Procedure -** Every complaint, should be forwarded to the HRM who in turn is expected to provide solutions and resolutions to any sort of conflict or complaint. ➲ **Requisition and Approval -** When in need of anything, one is expected to write a requisition mail, stating the need and purpose. \ The mail is to be sent to Until Approval is given, the request is void. ### ➲ **Accepted Holidays**
S/NoHolidayDateDescription
1New Year's Day1 JanuaryCommemorates the beginning of the calendar year.
22 Working Days, usually Friday and MondayEasterEaster commemorates the resurrection of Jesus from the dead. The highest church attendance happens on Easter. Like Christmas, it has become a widely celebrated secular holiday, and customs observed by both Christians and some non-Christians include egg hunting, the Easter Bunny, and Easter parades.
3Ramadan DayAprilBeginning of Ramadan
4Workers' Day1 MayCommemorates Workers' labor movement internationally.
5Eid-UL-FitrMayEnd of Ramadan
6Democracy Day12 JuneCommemorates the return to Democracy in Nigeria.
7Eid-AL-AdhaJulyThe day is celebrated to commemorate the sacrifice of Ishamel by Abraham.
8HijraAugustIslamic New Year
9National Independence Day1 OctoberCommemorates the Independence of Nigeria from Britain in 1960
10Christmas Day25 DecemberChristian holiday commemorating the birth of Jesus.
11Boxing Day26 DecemberChristian holiday commemorating the day after Christmas.

# Disciplinary Measures 1. Consequence Matrix #### Process
OFFENSEFIRST TIME OFFENSESECOND TIME OFFENSETHIRD TIME OFFENSE
Poor time keeping (lateness to work and meetings)Verbal warningVerbal warningQuery
Late submission of Daily Reports and Missing DeadlinesVerbal warningWarning MailQuery
Unauthorized absenteeism from work without PermissionVerbal warningWarning LetterQuery
Poor performance and nonchalant attitude to workVerbal Counseling and WarningQueryTermination
Signing documentation, committing the organization to obligation without approvalQueryTermination of Contract-----
Refusal to comply to RIL policiesWarning letterQueryTermination
Assault( physical, verbal)SuspensionDismissal-----
Sexual harassment, any kind of sexual act and pornographic practice in the officeDismissal----------
Divulging confidential informationDismissal----------
Theft, Dishonesty, Fraud, Falsification (reports, finances, signatures/documents)Dismissal----------
Facing disciplinary hearing for more than three offenses in one calendar yearSuspension without PayDismissal-----
Committing an act outside of work which could adversely affect the performance of the contract of employmentDismissal----------
Willful damage of company’s assetsPayment of company’s assetPayment of company’s assetTermination
Making false statements/ providing false information on employment.Summary of Dismissal----------
# Meetings ### ☕️ Monday Meeting - 9a.m Its part of RIL's Culture to have a One(1) Hour Virtual meeting every Monday. The Aim of the meeting is for Team Members to share updates on Previous week's dealings ranging from Performance updates and Management goals to Products Update, Public Relations/Marketing, Programs Management and Facility Management. This meeting is followed up by documentation shared on the Slack Channel #### 🤝 Tuesday General Stand-up - 9:15a.m The Programs and Public Relations teams have a general stand-up every Tuesday from 9:15a.m to 10a.m. The meeting is focused on providing updates on ongoing programs, public relations and communications activities, upcoming events, assigned tasks, deadlines, challenges, and priorities for the week. #### 💻 Tuesday Product Team Stand-up - 10a.m The Product Team has a virtual stand-up every Tuesday from 10a.m to 10:30a.m. The meeting is focused on product development updates, assigned tasks, progress, blockers, priorities, and upcoming deliverables. #### 👥 Wednesday Intern Check-in - 1p.m The Product Team has an intern check-in every Wednesday at 1p.m. The check-in is focused on reviewing the progress of Product Team interns, their assigned tasks, learning activities, challenges, and areas where support or guidance is required. #### 👥 Wednesday Intern Check-in - 2p.m Interns working with other RIL teams have their respective intern check-in every Wednesday at 2p.m. The check-in is used to review assigned tasks, monitor progress, provide feedback, address challenges, and ensure that interns are properly supported within their respective teams. ### 🎲 Managers Meeting These meetings holds every Thursday(1pm) Virtually. ### 🤝 Product Team Stand-up The Team meet Virtually on Mondays and Fridays for product team sync #### 🎳 First Friday - Hack and Chill The first Friday of every month is dedicated to "Hack and Chill." Hack n Chill is aimed at creating a stronger bond among team members through games, collaborative activities, brainstorming sessions, and challenges that encourage teamwork, creativity, and problem-solving. #### 🤖 Second Friday - AI Lab Workshop The second Friday of every month is dedicated to the AI Lab Workshop. The AI Lab Workshop provides an opportunity for team members, innovators, and the wider RIL community to learn, experiment, and develop practical solutions using artificial intelligence and emerging technologies. #### 💡 Third Friday - Innovation Day The third Friday of every month is dedicated to Innovation Day. Innovation Day provides an opportunity for team members and the RIL community to explore ideas, discuss emerging technologies, identify real-world problems, and develop innovative solutions. #### 🚀 Fourth Friday - Demo Friday The fourth Friday of every month is dedicated to Demo Friday. Demo Friday provides an opportunity for team members, interns, innovators, and project teams to demonstrate products, prototypes, projects, and solutions they have been working on. The session also provides an opportunity for feedback, knowledge sharing, and continuous improvement.
# Feedback and Reporting Cycles **Feedback Cycles and Reporting Procedures** To enhance our productivity and ensure continuous improvement, Renaissance Innovation Labs is implementing a structured feedback and reporting system. This system is designed to provide regular check-ins, facilitate timely feedback, and ensure accountability for all team members. Below are the detailed guidelines for the feedback cycles and reporting procedures. **1. Two-Day Feedback Cycles** **Overview:** We will implement a two-day feedback cycle to maintain a high level of productivity and ensure that tasks are progressing as planned. This means that every assigned task will be reviewed every two days, rather than weekly. This will help in identifying and addressing issues promptly, providing constructive feedback, and making necessary adjustments in a timely manner. **Schedule:** * **Mondays, Wednesdays, and Fridays**: Feedback sessions and demos will be conducted on these days. **Process:** * **Task Assignment**: Tasks will be assigned and communicated to team members. * **First Check-In (T+2 Days)**: Two days after the task is assigned, a check-in will be conducted to review progress and provide feedback. * **Second Check-In (T+4 Days)**: Another review and feedback session will be conducted two days after the first check-in. * **Continuous Cycle**: This cycle will continue, ensuring regular feedback and adjustments. **2. Demos and Reports** **Demos:** * **Purpose**: Demonstrations (demos) allow team members to showcase their progress and receive direct feedback from supervisors and peers. * **Schedule**: Demos will take place on Mondays, Wednesdays, and Fridays. * **Content**: During demos, team members should present their current progress, highlight any challenges faced, and discuss next steps. **Reports:** * **Daily Reporting**: Team members are required to submit daily reports on their activities and progress. This ensures transparency and allows for real-time monitoring of tasks. * **Content of Daily Reports**: Daily reports should include: * Tasks completed * Ongoing tasks * Any blockers or challenges * Plans for the next day **3. Daily Reporting** **Purpose**: Daily reporting ensures continuous communication and keeps all team members aligned with the project goals. It also helps in identifying and addressing issues promptly. **Procedure**: * This channel is dedicated to brief, daily organizational updates to improve visibility, accountability, and alignment across teams. 1\. Purpose of the Channel\ Share daily work updates, key progress, blockers, and outcomes. * Provide leadership and teams with a quick snapshot of what is happening across the organization. * Reduce unnecessary meetings and repeated status requests. 2\. What to Post\ What was worked on today * Key outcomes or progress made * Any blockers or support needed 3\. What NOT to Post * Casual chats, jokes, or unrelated conversations * Long explanations or debates (take those to DMs or relevant project channels) * Sensitive, confidential, or personal matters 4\. Formatting Standards * Use bullet points for clarity * Tag relevant teams or individuals only when necessary * Avoid large attachments; share links instead 5\. Accountability * Updates should be honest, specific, and measurable where possible. * Vague updates such as *“worked on tasks”* should be avoided. **4. Accountability and Follow-Up** **Responsibility**: It is the responsibility of each team member to adhere to the feedback cycle and reporting schedule. Consistent and timely updates are crucial for the success of this system. **Follow-Up**: Supervisors will follow up on feedback and ensure that necessary actions are taken. This includes: * Addressing any blockers or challenges reported by team members * Providing additional support or resources as needed * Ensuring that feedback is incorporated into the ongoing work #### Conclusion Implementing these structured feedback cycles and reporting procedures will help Renaissance Innovation Labs maintain high productivity, ensure timely adjustments, and foster a culture of continuous improvement. Adherence to these guidelines is essential for the success of our projects and the growth of our team. # Communication Channels ➲ Slack Slack is used for: * Internal-only communication and announcements impacting all team members * Company newsletters and team updates * Asynchronous team standups, questions, and quick collaboration * Informal communication 🔴 Please do not use or add emoji to Slack that are of a political, religious or of a sexual nature, and also ensure that your notification is turned on at all times, and respond to Tags and Comments Promptly. ➲ Email ➲ Trello Use link to View How to work with Trello. [Working With TRELLO](/collaborating/communication-channels/working-with-trello) ➲ Jira # Working With Trello Below are Steps and Rules that guide operations on RIL Trello Workspace. ### Steps The Board Contains 3 and 6 Basic Board Columns for Management and Engineering Teams Respectively. For Management Staff, the Board Columns Includes; To Do, Doing and Done. For Engineering Team, the Columns Includes; Backlog, To Do, Doing, Code Review, Testing #### BACKLOG: * Possible things that can be added or done, features that can be implemented. * This is the staging area where specs should get fleshed out. * No limit on the list size, but should be reconsidered if it gets long. #### TO DO: * A list of Tasks and Activities to be Carried within a Week. * Tasks Should be Added Every Monday to the Cards on this Column * Each Card should have a description explaining the task and expected outcome * One or More Persons can be assigned to a card to ensure efficient delivery #### DOING: * Ongoing Tasks should be moved to the Doing Column. * Each User is not allowed to have more than 2 Cards in Progress. * All Users should have at least one item in this state. * Any Ongoing Task should be deleted from the To Do column * There should be a Timeline attached to each Card in this column * Task Here can be broken into bits especially where a checklist is applicable. * Documents, Designs, Links, Videos can be attached here for reference purpose. #### CODE REVIEW * This list is for items in code review. * When a task has gotten approval, it moves off to Testing. * If there are too many cards here, we should break off from other tasks to get code review done. #### TESTING * Cards come here after being code reviewed, and we're in a place for QA and fixing things QA finds. * Design review also happens at this stage #### DONE * Completed Task. * Only Team Lead for Product Team is expected to Push a Task to the Done Column. Links to the completed Task should be attached to the Done Column. ### Notes: * Any Urgent Task added should be recorded and the date of addition should be noted. * Blockers should be reported before EOD in a checklist Format. * Cards should be updated by EOD. * All communications should be done on Slack with Link to the card attached for reference. * Any Task Carried over to the Next week, should be reported to the Team Lead and such task Must be completed on the Tuesday of the Next Week. * The Menu Bar contains an Activity Log stating time and Name of a User that makes a change, and the time the changes was made. Everything is Monitored
# Product Quality Standard To ensure that all projects meet high standards of quality, Renaissance Innovation Labs will adhere to the following quality standards. These standards cover various aspects of project development, from planning and execution to testing and delivery. #### Quality Standards **1. Project Planning and Management** * Clear Objectives: Each project must have well-defined objectives and scope. * Detailed Planning: Develop comprehensive project plans that include timelines, milestones, resource allocation, and risk management. * Stakeholder Involvement: Engage stakeholders throughout the project lifecycle to ensure their requirements and feedback are incorporated. **2. Requirements and Specifications** * Comprehensive Requirements: Gather and document functional and nonfunctional requirements in detail. * Client Approval: Obtain client approval on the requirements and specifications before proceeding with development. **3. Design Quality** * User-Centric Design: Ensure UI/UX designs are user-friendly, intuitive, and meet client expectations. * Consistency: Maintain consistency in design elements across the project. * Accessibility: Adhere to accessibility standards to make the product usable by people with disabilities. **4. Code Quality** * Coding Standards: Follow industry best practices and coding standards for maintainability, readability, and scalability. * Code Reviews: Conduct regular code reviews to identify and fix issues early. * Documentation: Provide thorough documentation of the codebase, including comments and explanations. **5. Development Process** * Agile Practices: Implement agile methodologies (e.g., Scrum, Kanban) to ensure iterative development and continuous improvement. * Version Control: Use version control systems (e.g., Git) to manage code changes and maintain history. **6. Testing and Quality Assurance** * Test Planning: Develop a comprehensive test plan that outlines the testing strategy, tools, and schedule. * Automated Testing: Implement automated testing for unit tests, integration tests, and regression tests. * Manual Testing: Perform thorough manual testing to validate functionality, usability, and performance. * Bug Tracking: Use bug tracking systems to log, prioritize, and resolve issues. * Performance Testing: Ensure the application performs well under expected load conditions. * Security Testing: Conduct security assessments to identify and mitigate vulnerabilities. **7. Documentation** * Technical Documentation: Provide detailed technical documentation for developers, including system architecture, APIs, and database schemas. * User Documentation: Create user manuals, guides, and help resources to assist end-users. * Project Reports: Maintain comprehensive project reports, including progress updates, test results, and final deliverables. **8. Client Interaction and Feedback** * Regular Updates: Provide regular updates to clients on project progress, milestones achieved, and any issues encountered. * Feedback Integration: Actively seek and incorporate client feedback throughout the project lifecycle. * Client Satisfaction: Strive to exceed client expectations in terms of quality, timelines, and communication. **9. Delivery and Deployment** * Quality Checks: Conduct final quality checks before project delivery to ensure all requirements are met. * Deployment: Follow best practices for deployment, including pre-deployment testing and post-deployment monitoring. * Training and Support: Provide necessary training and support to clients during and after deployment. **10. Continuous Improvement** * Post-Project Review: Conduct post-project reviews to identify lessons learned and areas for improvement. * Best Practices: Document and share best practices within the team to enhance future projects. * Professional Development: Encourage continuous learning and professional development for team members. # Project Documentation Structure The comprehensive documentation aims to provide a detailed account of each mini-project undertaken by Renaissance Innovation Labs. This documentation serves as a tool for internal review, client presentations, and marketing purposes. #### Components of Comprehensive Documentation **1. Project Overview** * Project Title: Name of the mini project. * Project Duration: Start and end dates. * Project Team: Names and roles of team members involved. * Objectives: Clear and concise description of the project's goals. * Scope: Detailed explanation of the project's scope, including what is included and excluded. **2. Project Plan** * Timeline: Gantt chart or timeline showing key milestones and deadlines. * Milestones: List of significant milestones and deliverables. * Resource Allocation: Breakdown of resources (time, personnel, tools) allocated to the project. * Risk Management: Identified risks and mitigation strategies. **3. Requirements** * Functional Requirements: Detailed description of the functionalities the project is supposed to deliver. * Non-functional Requirements: Performance, usability, reliability, and other non-functional requirements. **4. Design Documentation** * System Architecture: High-level overview of the system architecture. * UI/UX Designs: Wireframes, mockups, and design specifications. * Database Design: ER diagrams and schema definitions if applicable. * API Documentation: Detailed documentation of any APIs developed or used. **5. Development Process** * Development Methodology: Description of the development methodology (e.g., Agile, Scrum) used. * Sprint Planning: Details of sprint plans, including sprint goals and backlogs. * Code Repository: Links to the code repository and instructions for accessing the code. * Technical Specifications: Detailed specifications of the technologies and frameworks used. **6. Testing and Quality Assurance** * Test Plan: Description of the testing strategy and plan. * Test Cases: Detailed test cases and expected outcomes. * Testing Tools: List of tools used for testing. * Bug Reports: Documentation of bugs found and resolved during testing. * QA Reports: Summary of QA findings and final QA approval. **7. Project Outcomes** * Final Deliverables: Description of the final deliverables provided to the client or for internal use. * Performance Metrics: Key performance indicators (KPIs) and metrics used to measure the project's success. * Client Feedback: Summary of feedback received from the client or end-users. **8. Lessons Learned** * Challenges Faced: Description of any challenges encountered during the project. * Solutions Implemented: How the team addressed and overcame these challenges. * Best Practices: Best practices identified during the project that can be applied to future projects. **9. Marketing Case Study** * Executive Summary: Brief summary of the project and its outcomes. * Visuals: High-quality images, screenshots, and other visuals showcasing the project. * Client Testimonials: Quotes and testimonials from the client or end-users. * Project Impact: Description of the project's impact on the client or end-users. **10. Appendices** * Additional Documentation: Any additional documentation, such as meeting minutes, emails, or other relevant communications. References: List of references and resources used during the project. # Product/Feature Life cycle ### Purpose {% hint style="info" %} This document serves as a guide to the step-by-step process through which a project goes from the idea phase to implementation. It details the specific assignments, corresponding assigned roles, as well as the workflow analysis. {% endhint %} ### Scope {% hint style="info" %} This SOP covers the end-to-end process from idea proposals to planning and all through to completion of the projects. The details within will help to maximize productivity and ensure strict compliance to standard. {% endhint %} ### Responsibilities * **Executive Chairman:** Final decision maker, Budget approval. * **General Manager:** Ensures smooth running of personnel and activities required to keep up with project success. * **Product Manager:** In charge of coordinating several products, and aligning with RIL objectives * **Project Manager:** Directly responsible for coordinating the different phases of a project. * **Chief Technology officer:** Tasked with ensuring the most suitable technologies and tools are used in implementing any project. * **End User:** Prospective customer or product user. #### 1. **SPECIFIC PROCEDURE** * Project Initialization * Project Planning * Project Execution * Project Testing * Project Closing #### PROCEDURE BREAKDOWN Initialization: * To determine a product or new feature to be adapted, the product team has to ensure that it solves a consumer/user challenge. * The product manager carries out discussion and surveys with the end users in order to ascertain the problem that requires a new feature or product solution. * From the result of the above, the proposed solution is determined by the product team, and a product strategy is developed. * The product manager then goes ahead to create a Product Requirement Document (PRD) and User stories * Based on the user stories, detailed responsibility and action plan for developers are determined. * The product designer then creates the necessary wireframe and a high fidelity prototype * The product team comprising of the product manager, designers and at least a member of the engineering team sits to make sure the High-Fidelity Prototype solves the intended problem Planning * Approvals are obtained from the entire board and stakeholders comprising (Exec. Chair, GM, Product Manager, Project Manager, CTO, and end user). * On the approval, the Project manager is expected to come up with the roadmap, development technical requirement and budget. {% hint style="warning" %} ***In the advent of a change in User requirement, or halt in product/feature, the Process begins again from Initialization.*** {% endhint %} * The Project manager must make sure that all changes made during the planning phase go through the initiation process Project Execution * The project is broken down into epics, then user stories are assigned to the members of the Engineering team * Weekly sprints will be created for the project detailing tasks to be completed by each team member * Members of the project team are expected to use Trello in updating their progress on the project. Trello also serves as a tracking tool for the Project Manager. * Members of the project team are also expected to use Slack for their daily standups * Project reviews will be conducted on Mondays and Retrospectives will be conducted on Fridays * The Project manager is to create weekly progress reports based on updates on Trello. This report would be used by the Product Manager and other members of the board to track project success. Project Testing * Project testing is to be carried out by the stakeholders. (A testing committee if available or the GM, CTO, members of the product team and end user), to ensure it solves the actual problem It was intended to solve. * The product team ensures that the product/feature meets the requirements stated at the initialization and planning phases. * On entire stakeholder approval, the product/feature may be deployed or mass produced. {% hint style="warning" %} ***In the event that a product/feature isn’t approved, the product team determines changes to be made and forwards them to the project manager who specifies “who does what” in the engineering team.*** {% endhint %} Project closing * Ensure all documentation is put in place to ensure easy reference when necessary. # Wireframe/Design ### Wireframe Design Guidelines #### How do you create ubiquitous designs and be device ### agnostic? Here’s how to do it: 1. Treat my mobile designs as if designing for mobile web--Use an artboard width of 375, which works for most modern iPhone models and Android. 2. Manage the screen shape of the iPhone X and iPhone 11 by telling the dev team to just extend the header background color to the top. 3. Only use gestures that are universal, e.g. tap, swipe, press and hold. Focus on the best user experience regardless of OS. 4. Use SVGs for all icons and logos so that they look great on any screen resolution. 5. Use navigation and menu structures that are universal and not too OS specific. # Infrastructural System ## RIL IT Infrastructure System > **Purpose:** > > To adopt and implement a robust IT infrastructure/system that supports our core business and lay the ground for Renaissance Innovation Labs’ IT Infrastructure/System policy formulation. > > NOTE: > > This document contains recommendations for Server Infrastructure, Technology Stack, Product Development Methodology, Communication Management and Project Management. > > **1.0 Server Infrastructure** > > A Virtual private server (VPS) from one of the leading cloud computing service providers on a pay as you use package. The security of the server will be provided by the VPS service provider. The server will run the most recent stable Ubuntu distribution. The server will run a Docker engine. With Docker containers the server will be able to serve different applications with different technology stacks and frameworks without having to install individual software technology on the server. > > ![https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a94004f9-9478-4aa8-881d-32abd2104f1c/image2.png](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a94004f9-9478-4aa8-881d-32abd2104f1c/image2.png) > > Server Infrastructure with Docker architecture > > Source: **2.0 Technology Stack** > Our technology and application stack will be open to accommodate a wide variety of technology requirement of clients adopt will be project/product specific supported by Docker containers to provide self contained deployable application stacks. However, for our in-house competency development we would place emphasis on the MEAN and MERN stacks. The following are some recommended core technologies for specific project/product types **2.1 Mobile apps** ReactNative **2.2 Web apps/Progressive Web Apps** MongoDB, ExpressJS, ReactJS, and NodeJS (MERN Stack) **2.3 Application Program Interfaces (APIs)** NodeJS and ExpressJS PHP **3.0 DevOps** The Product Development Methodology recommended is *DevOps* **3.1 Tracking and Version Control** > GitLab community edition will be used as source repository management system and version control system to manage project source code and implement Continuous Integration (CI) and Continuous Delivery (CD). The choice of GitLab is based on private repositories for client projects. **3.2** **Cloud Computing** We would be using AWS for cloud computing and Continuous Delivery (CD) [Tech Stack](https://www.notion.so/e362924689b748ea8ec0f7c878c163cf) > **4. 0 Communication Tool** > > We would mainly use Slack for project communication. Other communication channels/tools can be used where a client specifies. > > **5.0 Project Management Tool** Jira & GitLab Issue Tracker would be used for now # Design Process ### How To Approach UI/UX Design? UI/UX Design is a part and parcel of the product development process. It is what decides the future or success of our product. The best approach for a successful UI UX design is by combining the structure, content, and the user experience in a certain way, so that it enables your business to accomplish the goals. Follow a user-centric approach, in the UI UX Design process. Adopting the strategy enables you to develop simple, intuitive, and engaging micro-moments which thrills the end-users. Thus, creates a push factor that makes you stand out from the crowd!. ### Steps of UI/UX Design Process The UI/UX Design Process is a methodology that, if followed, allows you to polish your user interfaces to be the best one possible for your business. If this process is not followed, then it may end up in a situation where you need to keep redesigning ourselves every time! The entire UI/UX design process can be divided into 5 phases. 1. Product Definition Product Definition is the first phase involved in the user design process. The team responsible for this will collect the user requirements based on their business environment. It’s very much essential because understanding about the real scope of the product and their existence happens in this phase. 2. Research The research is the most crucial element for a designer. The designing team studies how the present system works for the current client proposal. The three main functions at this stage are: * Have an understanding of the competition. * Making a thorough study of your existing domain. * Going through competitor strategy to test outcomes. The Research process should also involve an understanding of the latest UI/UX trends, design principles, and guidelines. 3. Analysis In this phase, make use of the things collected in the Research phase. With the help of the information received, create hypothetical personas, and experience maps. Hypothetical Personas: Creating hypothetical scenarios help the designers to know about the various persons who will be the users of your product. It allows depicting the realistic representation of the ultimate product. The design team can figure out how it is going to look like after delivery. Experience Maps: Experience maps show the user flow within your final product. All these are done using visual representations through proper interactions with the client in the product definition phase. 4. Design In the design process, we finally end up giving life to ideas that we have collected in the above three steps. It’s time to work on the final graphics now. The design team will execute the final design in this phase. The significant outcomes of the designing phase are: **Sketching:** The designing phase begins with sketching. The designers usually make hand made sketches to visualize the concept with simple terms. The UX/UI designers can stick to a particular option after the sketching process. **Creating wireframes:** A wireframe is a visual structure that depicts the page hierarchy and the elements in the product. A wireframe is a low-fidelity way of showing a design. It’s the graphic representation of an app or a website containing the most essential elements and the content. A wireframe is considered as the backbone of the product. It’s also called the skeleton of the design. It’s mostly about the overall look of the final product. **Creating Mockups:** A mockup is a visual way of representing a product. While a wireframe mostly represents a product’s structure, a mockup shows how the product is going to look like. As opposed to a wireframe, a mockup is either a mid or high-fidelity display of design. A mockup helps you make final decisions regarding a product’s color schemes, visual style, typography. With a mockup, you can allow yourself to experiment with the visual side of the product to see what looks the best. Here again, you can ask your potential users for feedback and make the necessary changes right away. This will save you way more time than getting back and making adjustments to the UI after you have launched the product. **Creating Prototypes:** Prototypes concentrate on the feel of the UI/UX product that one is designing. It’s more about the interaction experience. Prototypes give you the effect of a simulator. **Creating Design Specifications:** Design specification includes user flow and task flow diagrams. It depicts the overall working and the style requirements of the UI/UX product. It describes the processes and graphical elements to create amazing user experiences. 5. Validation (Testing) Testing is the phase that determines the overall quality of the end- product. The testers make notes of the things that have to be improved and send them back to the respected team for correcting the errors. Key testing questions: **User Testing:** Do users need my app? **Usability Testing:** Can users use my app? While evaluating your final product, there are certain factors that one needs to keep in mind. They are as follows: * Is the system user-friendly? * Is it flexible and easy to operate? * Does it solve the customer’s issue? * Is it credible and attracts the users to come back every time they need our service? ### Conclusion For creating amazing UX/UI interfaces, one requires to follow a systematic and organized approach. A UI/UX design process strategy will help you in achieving the same. The entire design team will be playing their part in the process. This is one of the best ways to retain our existing customers and attract new ones in this highly competitive world. # Development Stages The purpose of this document is to serve as a guide during the execution of RIL projects to avoid chaos. The product development stages are listed based on the kinds of products. ### SOFTWARE PRODUCT 1. Analysis 2. Wireframe Design 3. UI/UX Design 4. Front End Development 5. Database Design and Backend Development 6. Server Setup(Staging and Production) and Deployment 7. Quality Assurance 8. Go Live/Release #### **Analysis** > The team involved will analyze the product to be developed, gather and analyze the business requirements of the product (BRD), and discuss with every stakeholder involved to understand the software requirement of the product and their activities. This stage of the product is primarily the work of every project stakeholder. > > **Docs:** 1. Competitive Analysis - **Project Manager** 2. Product Strategy (Vision) - **Project Manager** 3. Product Requirement Document (PRD) - **Project Manager** 4. Roadmap - **Project Manager** 5. Project Scope and Implementation Plan - **Project Manager** ### Wireframe Design > Wireframes are an important part of building a software product as they are the foundation on which to begin building. They present a clear summary of the page layout, format, information architecture, user flow, and intended behaviors. All these pieces of information are key for other software product stakeholders. This stage of the product is the work of the Product Designer. 1. User Goals *(as needed)* 1. Definition 2. Examples 3. Potential Persona Development 2. User Task Flows (Action Level) 3. Wireframes (lofi representation) 4. Interface Design (visual design representation) 5. Prototypes (interactive representation) #### Delivery Methods > There are three applications that are used in conjunction with developing the assets to document the human experience. Those applications are: 1. Adobe XD/Figma - Used to execute documents related to (user goal, task flows, wireframes and interaction design) 2. Adobe XD/Figma Invision/Principle (TBD) - Used to construct interaction prototypes to demonstrate product design to stakeholders, investors and potential users > Asset Ecosystem Development > > 1. Create project within abstract to house and manage assets > 2. Create project buckets within abstract (pattern libraries, product innovation, sprints specific, sketch resources) > 3. Create Pattern Library > 4. Create components > 5. Start with Sprint and create sprint specific sketch files to be built > 1. IA > 2. VD > 3. Prototype ### **UI/UX Design** > Before the product is built, there has to be a visual image and feel of what the product is set to look and feel like. This is where the UI/UX Design comes in. The team involved will look through the necessary documents from the previous stages, set up a design system and develop the UI with UX flow using the recommended design tools. > > **Docs**: (make a folder per project/client) > > 1. Information Architecture - **Product Designer** > 2. Visual Design - **Product Designer** > 3. Breakpoints (maximum 1920 down to less than 576) - Mobile forward approach > 4. Style Guide-- Standards and Guidelines (Type, CTA, Library) - **Product Designer** > 5. Design Guidelines - **Product Designer** > 6. User Stories and Journey Map (User Flow) - **Product Team** > 7. User Guides and FAQs - **Product Team** **Frontend Development** > The team involved will develop the UI and Implement the UX flow using the recommended technologies from the Development unit. > > This frontend must be on the git repo with the suffix ‘\_fe’ to note that it's just the front end code > > * **Technology Selection**: > * Choose the appropriate frontend technologies and frameworks (e.g., React, Angular, Vue.js). > * Decide on the necessary tools and libraries for development (e.g., Bootstrap, Material-UI). > * **Development**: > * **Coding**: Write clean, maintainable code to implement the UI/UX designs. > * **Responsive Design**: Ensure the application works well on various devices and screen sizes. > * **Interactivity**: Implement interactive elements such as buttons, forms, and navigation. > * **Integration**: > * Integrate the frontend with backend services and APIs. > * Ensure seamless communication between the frontend and backend components. > * **Testing**: > * **Unit Testing**: Test individual components for functionality and performance. > * **Integration Testing**: Test the integration between frontend components and backend services. > * **Usability Testing**: Conduct tests to ensure the application is user-friendly and meets UX standards. > * **Cross-Browser Testing**: Verify the application works consistently across different browsers and devices. > * **Optimization**: > * Optimize the code for performance, ensuring fast load times and smooth interactions. > * Minimize and compress assets like images, CSS, and JavaScript files. > * **Deployment**: > * Deploy the frontend application to a staging environment for final testing. > * Once approved, deploy the application to the production environment. > * **Maintenance**: > * Monitor the application for any issues or bugs post-deployment. > * Provide ongoing support and updates to improve performance and add new features. **Database Design & Backend Development** > **1. Planning and Requirements Analysis** > > * **Define Requirements**: Understand the project requirements, including the desired functionalities, data flow, and integration needs. > * **Technology Stack**: Decide on the technology stack (e.g., programming languages, frameworks, databases) based on the project needs and scalability considerations. > > **2. System Architecture Design** > > * **Architectural Patterns**: Choose appropriate architectural patterns such as MVC (Model-View-Controller), MVVM (Model-View-ViewModel), or microservices. > * **Database Design**: Design the database schema, including tables, relationships, and indexing strategies. > * **API Design**: Plan the API endpoints, request/response formats, and authentication mechanisms. > > **3. Setup and Configuration** > > * **Development Environment**: Set up the development environment with necessary tools, libraries, and frameworks. > * **Version Control**: Configure version control systems (e.g., Git) for source code management. > > **4. Database Management** > > * **Database Setup**: Install and configure the database management system (DBMS). > * **Data Modeling**: Create data models based on the database schema. > * **Data Migration**: Plan and execute data migration strategies if dealing with existing data. > > **5. Server-Side Logic Implementation** > > * **Coding**: Write server-side code to handle business logic, data processing, and communication with the frontend. > * **API Development**: Implement RESTful or GraphQL APIs for data exchange between the client and server. > * **Authentication and Authorization**: Implement user authentication and authorization mechanisms. > > **6. Integration and Testing** > > * **Integration**: Integrate various components, such as third-party APIs, payment gateways, and other services. > * **Unit Testing**: Write and run unit tests to ensure individual components function correctly. > * **Integration Testing**: Perform integration testing to verify that the components work together seamlessly. > * **Load Testing**: Conduct load testing to assess the application’s performance under stress. > > **7. Deployment** > > * **Server Configuration**: Configure servers and deploy the backend code to the production environment. > * **Continuous Integration/Continuous Deployment (CI/CD)**: Set up CI/CD pipelines for automated testing and deployment. > > **8. Monitoring and Maintenance** > > * **Monitoring**: Implement monitoring tools to track server performance, uptime, and error rates. > * **Bug Fixes and Updates**: Continuously fix bugs, update the system, and optimize performance. > > **9. Documentation** > > * **API Documentation**: Create comprehensive documentation for the APIs. > * **Technical Documentation**: Provide detailed documentation on the system architecture, data models, and development processes. **Server Setup and Deployment** > The team involved will setup the server needed to host the project and there must be 2 environments (staging and production). > > Any deployment of the project for any environment to the server must be via git. > > The staging environment must be connected to git via CI/CD > > **Docs**: Doc with links to the different environment and must be in the Devops folder of the Engineering Department - **Devops Team** > > 1. **Quality Assurance** > > The team involved will test the product online across all environments, decide the new version based on the changes and other criteria and conclude if the product is good to go Live and if YES, inform the devops unit to send it live. > > Version all the docs prepared > > **Docs** > > 1. Testing Documentation - **QA Team** > 2. **Go Live/ Release** > > The team prepares the final release report and launches the product. > > **Docs:** > > 1. Final Release Report - **Devops Team** ## **USER INTERFACE/USER EXPERIENCE** The UI/UX Design Process is a methodology that, if followed, allows you to polish your user interfaces to be the best one possible for a product. If this process is not followed, then it may end up in a situation where you need to keep redesigning product screens every time! The entire **UI/UX design process** is divided into 5 phases; * Product Definition * Research * Analysis * Design * Validation #### **1. Product Definition** Product Definition is the first phase involved in the user design process. The team responsible for this will analyse the user needs and ensure that it aligns with the goal of the product. This is a very essential phase because understanding the scope of the product happens in this phase. #### **2. Research** Research is the most crucial element for a designer. The designing team studies how the present system works for the current client proposal. The three main functions at this stage are: * Have an understanding of the competition. * Making a thorough study of your existing domain. * Going through competitor strategy to test outcomes. The Research process should also involve an understanding of the latest UI/UX trends, design principles, and guidelines. #### **3. Analysis** In this phase, make use of the things collected in the Research phase. With the help of the information received, create hypothetical personas, and experience maps. * Hypothetical Personas: Creating hypothetical scenarios help the designers to know about the various persons who will be the users of your product. It allows depicting the realistic representation of the ultimate product. The design team can figure out how it is going to look after delivery. * Experience Maps: Experience maps show the user flow within your final product. All these are done using visual representations through proper interactions with the client in the product definition phase. #### **4. Design** In the design process, we finally end up giving life to ideas that we have collected in the above three steps. It’s time to work on the final graphics now. The design team will execute the final design in this phase. The significant outcomes of the designing phase are: **Sketching:** The designing phase begins with sketching. The designers usually make hand made sketches to visualize the concept with simple terms. The UX/UI designers can stick to a particular option after the sketching process. **Creating wireframes:** A wireframe is a visual structure that depicts the page hierarchy and the elements in the product. A wireframe is a low-fidelity way of showing a design. It’s the graphic representation of an app or a website containing the most essential elements and the content. A wireframe is considered as the backbone of the product. It’s also called the skeleton of the design. It’s mostly about the overall look of the final product. **Creating Mockups:** A mockup is a visual way of representing a product. While a wireframe mostly represents a product’s structure, a mockup shows how the product is going to look like. As opposed to a wireframe, a mockup is either a mid or high-fidelity display of design. A mockup helps you make final decisions regarding a product’s color schemes, visual style, typography. With a mockup, you can allow yourself to experiment with the visual side of the product to see what looks the best. Here again, you can ask your potential users for feedback and make the necessary changes right away. This will save you way more time than getting back and making adjustments to the UI after you have launched the product. **Creating Prototypes:** Prototypes concentrate on the feel of the UI/UX product that one is designing. It’s more about the interaction experience. Prototypes give you the effect of a simulator. **Creating Design Specifications:** Design specification includes user flow and task flow diagrams. It depicts the overall working and the style requirements of the UI/UX product. It describes the processes and graphical elements to create amazing user experiences. #### **5. Validation (Testing)** Testing is the phase that determines the overall quality of the end- product. The testers make notes of the things that have to be improved and send them back to the respected team for correcting the errors. Key testing questions: **User Testing:** Do users need my app? **Usability Testing**: Can users use my app? While evaluating your final product, there are certain factors that one needs to keep in mind. They are as follows: * Is the system user-friendly? * Is it flexible and easy to operate? * Does it solve the customer’s issue? * Is it credible and attracts the users to come back every time they need our service? # Project Types ### **SUMMARY** At Renaissance Innovation Lab, we believe that Learning is simply not enough; one must actively practice what is learned for better application of knowledge and skill. These projects are; Management Project and External Project. This document describes each of these Projects in detail, their project Development stages, and guidelines for every stakeholder involved in each of the above projects and serves as a guide for RIL’s project manager(s) in the execution of any RIL project from the initiation phase to the close of project (closure) phase, describing all that is expected of the Project Manager. The activities listed in this document are coordinated by the office of the Project Manager. ### **PROJECT TYPES** **Management project** Management projects as the name implies are projects proposed by RIL’s Management. These projects are usually experimental and if they do exceptionally well, goes live and becomes a product of its own independent of RIL. **When Management has decided on the next project to take on, they are expected to;** * Conduct a feasibility analysis, come up with a BRD (Business requirement Document) and submit the document to the Project Manager for review and further discussion. **Upon Submission, the Project Manager is expected to;** * Review the document and determine that RIL has the resources and time to execute the project as at when due. * Establish Project Authorities. * Identify all stakeholders in the projects and their interests/roles. * Identify project objectives and the practical measures to meet them * Establish the mode of communication for all stakeholders. * Create a PRD for the project and distribute to all stakeholders. * Discuss with every stakeholder to identify the resources, tasks and deliverables needed to execute the project. * Determine the methodology for the project’s execution. * Document an activity log/roadmap with tasks/activities and deliverables, owners, dependencies, etc. taking into account the need for stages and checkpoints. * Generate other necessary documents in line with the chosen methodology. * Share the Roadmap with stakeholders to get their views and opinions about deliverables and if need be, make necessary changes. * Determine a start date and an end date. * Execute Project. **External Project** External projects are projects contracted to RIL for execution. External Projects are not the same as Management Projects. While Management Projects are proposed by management, they are experimental whereas External Projects are not. **Before an external Project outsourced to RIL is accepted;** * Extensive discussions between RIL’s management and the company outsourcing their project must be had to determine what the Objectives of the project are, the deliverables expected from the project, etc. * It is the duty of the Company outsourcing their project to conduct feasibility studies and produce a BRD (Business Requirement document) that will be reviewed by the Project Manager alongside RIL’s management. * The Project Manager must determine that RIL has the resources to undertake the external project (time, person(s), etc.). **Upon accepting to take on the external project, the Project Manager must;** * Establish Project Authorities. * Identify all stakeholders in the projects and their interests/roles. * Identify project objectives and the practical measures to meet them * Establish the mode of communication for all stakeholders. * Create a PRD for the project and distribute to all stakeholders. * Discuss with every stakeholder to identify the resources, tasks and deliverables needed to execute the project. * Determine the methodology for the project’s execution. * Document an activity log/roadmap with tasks/activities and deliverables, owners, dependencies, etc. taking into account the need for stages and checkpoints. * Generate other necessary documents in line with the chosen methodology. * Share the Roadmap with stakeholders to get their views and opinions about deliverables and if need be, make necessary changes. * Determine a start date and an end date. * Execute Project. **OTHERS:** * External projects must be in line with RIL’s vision ### **PROJECT ACCEPTANCE GUIDELINES** A Project Manager knowing when to take on a project is crucial for the success of each project and the efficiency of the management of said projects. In taking on projects in RIL, the following factors should be considered; #### **Project Hierarchy** When faced with a lot of project proposals on your table, the project Manager must give time and resources to the projects according to this Hierarchical list; 1. External Projects. 2. Management Projects. #### **Opportunity Cost** If a proposed project is lower in the hierarchical table, it is the Project Manager’s duty to analyze the Opportunity cost of the said project and make a decision based on their analysis. Factors to consider when analyzing the opportunity cost are; 1. Monetary gain 2. Success rate of the Project 3. Global recognition of the Lab due to the success of the Project 4. The social capacity of the Project Owner in the Tech Space 5. The Project Owner’s value to the Lab. #### **Available Resources** > Before taking on a project, the project Manager must ensure that the Lab is equipped with the necessary resources for the execution of the project. These resources are as follows; > > 1. **Available People to take on the job:** During the project’s analysis, the Project Manager must ensure that the people who’s skills and experiences are needed for the job are not already tasked and overwhelmed with a project. If tasked with other projects, it is the Project Manager’s duty to identify if the Proposed project is higher in the hierarchical list or if the opportunity cost of the proposed project is greater than the project currently being worked on. This way People can be reassigned to more important projects and made to pause the other projects being worked on. > 2. **Hardware & Software:** Before accepting a project, it is the Project manager’s duty to identify the hardware and software resources needed to execute the project, to know if the Lab has access to the needed resources or if the Lab can afford to acquire these resources in time to execute the project. > 3. **Cost & Budget:** When analyzing the project and determining the budget, project’s whose budget exceeds the Lab’s financial capabilities are to be held off until such a time when the Lab can fund it or get a sponsor to fund it. # Project Ideas # Automated Vehicle Prototype with Preprogrammed Path PROJECT DOCUMENTATION For Automated Vehicle Prototype with Preprogrammed Path Following \ Prepared By: Shammah Nei Project Name: Automated Vehicle Prototype Date Prepared: 13/08/2024 ## 1. Project Overview Project Title: Automated Vehicle Prototype Project Duration: Four weeks Project Team: Project Manager - Shammah Nei Hardware Specialist - Emmanuel Enebili (Innovator) #### OBJECTIVES * To design and build a basic automated vehicle prototype that can follow preprogrammed paths. * To demonstrate the feasibility of low-cost automated vehicles using readily available components. * To create a foundation for further development in autonomous vehicle technology #### SCOPE * Development of an automated vehicle capable of following predefined paths. * Integration of basic obstacle detection using ultrasonic sensors. * Implementation of a simple control system using Arduino. * Basic testing in a controlled environment. ## 2. Project Plan * Timeline: 3 weeks Milestones: * Week 1: Component acquisition. * Week 2: Completion of vehicle chassis assembly and basic electronics. Completion of motor control and basic path programming. * Week 3: Integration of obstacle detection. * Week 4: Final testing, documentation, and project presentation Resource Allocation: * Hardware Components: Sourcing and assembly - Emmanuel Enebili * Software Development: Coding and testing - Emmanuel Enebili Risk Management: * Component Failure: Maintain a stock of spare components. * Power Issues: Use stable power supplies and check battery health regularly. * Programming Errors: Implement version control and thorough testing. Estimated Costs: * L298N Dual H Bridge DC Stepper Motor Driver: $3 - $5 (4,800 NGN - 8,000 NGN) * Arduino Uno: $10 - $25 (16,000 NGN - 40,000 NGN) * 4 Wheel Drive Robotic Car Chassis: $10 - $20 (16,000 NGN - 32,000 NGN) * HC-SR04 Ultrasonic Sensor: $2 - $4 (3,200 NGN - 6,400 NGN) * SG90 Servo Motor: $2 - $5 (3,200 NGN - 8,000 NGN) * Jumper Wire Set (Male to Female): $3 - $5 (4,800 NGN - 8,000 NGN) * Soldering Iron: $10 - $20 (16,000 NGN - 32,000 NGN) * Soldering Lead: $2 - $5 (3,200 NGN - 8,000 NGN) * Lipo Battery (4): $20 - $50 (32,000 NGN - 80,000 NGN) * 20W Hot Melt Glue Gun: $5 - $10 (8,000 NGN - 16,000 NGN) * Glue Candle Stick (2): $1 - $3 (1,600 NGN - 4,800 NGN) * SFM-27 Electronic Buzzer (1): $1 - $2 (1,600 NGN - 3,200 NGN) Total Estimated Cost: 110,400 NGN - 246,400 NGN ## 3. Requirements Functional Requirements: * The vehicle must follow a preprogrammed path accurately. * The vehicle should avoid obstacles detected by the ultrasonic sensor. * The system should allow for easy reprogramming of the path. * Power management should be efficient to maximize operational time. ## 4. Design Documentation System Architecture: * Control Unit: Arduino Uno * Motor Driver: L298N Dual H Bridge for controlling the motors * Sensors: HC-SR04 for obstacle detection * Power Supply: Lipo batteries * Actuators: DC motors and SG90 Servo Motor for directional control UI/UX Designs: * Basic user interface (if applicable) for entering and adjusting the vehicle's path. * LCD or LED indicators to show the vehicle's status (optional). API Documentation: * Not applicable for this basic prototype, unless integrating with external systems. ## 5. Development Process Development Methodology: * Agile Development Methodology with weekly sprints for iterative progress. Sprint Planning: * Sprint 1 (Week 1): Component assembly and initial system setup. * Sprint 2 (Week 2): Basic motor control and path programming. * Sprint 3 (Week 3): Sensor integration and obstacle detection. * Sprint 4 (Week 4): Final testing and adjustments. Code Repository: * Hosted on GitHub ([ril/hermes](https://github.com/Renaissance-Innovation-Labs/hermes)) * Repository includes code for motor control, path programming, and sensor handling. Technical Specifications: * Microcontroller: Arduino Uno with ATmega328P * Motors: 4 DC motors with L298N driver * Sensors: HC-SR04 ultrasonic sensor * Power: 4 x Lipo batteries, 7.4V 1000mAh * Control Software: C++ (Arduino IDE) * Chassis: 4-wheel drive with custom mounts for sensors and controllers ## 6. Project Outcomes Final Deliverables: * A fully functional automated vehicle prototype. * Source code and technical documentation. * Test reports and performance data. Performance Metrics: * Accuracy in following preprogrammed paths (within 5 cm deviation). * Obstacle detection and avoidance rate (95% success rate). * Battery life during continuous operation (1 hour minimum). * Client Feedback: TBD ## 7. Lessons Learned * Challenges Faced: TBD * Solutions Implemented: TBD * Best Practices: TBD ## 8. Real-Life Use Cases Warehouse Automation: * Use Case: Automated Guided Vehicles (AGVs) for transporting goods along predefined paths. * Benefits: Increases efficiency, reduces human labor, and minimizes errors. Smart Agriculture: * Use Case: Autonomous farming vehicles for tasks like planting, watering, or harvesting. * Benefits: Enhances precision, reduces manual labor, and increases productivity. Factory Floor Material Handling: * Use Case: Automated vehicles for moving raw materials or finished products between production stages. * Benefits: Streamlines production, reduces manual handling, and minimizes accidents. Automated Delivery Systems: * Use Case: Small autonomous vehicles for delivering goods within campuses or urban environments. * Benefits: Reduces the need for human delivery personnel, offers contactless delivery, and can operate 24/7. Healthcare and Hospital Logistics: * Use Case: Autonomous vehicles for transporting medical supplies, meals, or medications. * Benefits: Frees up healthcare staff, reduces contamination risk, and ensures timely delivery. Search and Rescue Operations: * Use Case: Autonomous vehicles for search and rescue missions in disaster areas. * Benefits: Operates in hazardous environments, covers large areas efficiently, and provides real-time data. Autonomous Surveillance and Patrolling: * Use Case: Vehicles for patrolling areas like military bases or industrial sites. * Benefits: Enhances security through constant monitoring, reduces the need for human guards. Educational Tools: * Use Case: Use in schools and universities as an educational tool for robotics and automation. * Benefits: Provides hands-on learning, fosters innovation, and helps understand complex concepts. Construction and Mining Operations: * Use Case: Vehicles for transporting materials or performing repetitive tasks. * Benefits: Enhances safety, increases efficiency, and allows precise control of machinery. Autonomous Cleaning Robots: * Use Case: Vehicles for cleaning large facilities like airports or shopping malls. * Benefits: Ensures consistent cleaning, reduces labor costs, and can operate unsupervised. Indoor Navigation Systems: * Use Case: Vehicles for guiding visitors in large buildings like airports or hospitals. * Benefits: Enhances visitor experience and reduces the need for staff. Automated Event Management: * Use Case: Vehicles for distributing materials, transporting equipment, or providing mobile kiosks. ## 9. Appendices * Additional Documentation:
# JDGEN Widget PROJECT DOCUMENTATION Prepared By: Chioma Otu Project Name: JDGEN Widget Date Prepared: 02/08/2024
## 1. Project Overview Project Title: JDGEN WIDGET (Job description generation) Project Duration: 1 week Project Team: * Chioma Otu - Frontend Developer Objectives: * The primary objective of JDGEN is to assist job recruiters and companies in generating accurate and tailored job descriptions for various roles they are hiring for. The widget aims to eliminate the common practice of copying and pasting job descriptions that may not fit specific roles, ensuring that the requirements and responsibilities listed are appropriate for the position being advertised. Scope: * Develop an embeddable widget powered by Open AI for generating job descriptions. * Ensure the widget provides accurate, role-specific descriptions based on user input. * Create a user-friendly interface for recruiters and companies to interact with the widget. * Test and deploy the widget within the specified timeframe. ## 2. Project Plan Timeline: * Week 1: Project kickoff, development, testing, and deployment. Milestones: * Day 1: Project initiation and requirement gathering. * Day 2: Development and documentation of the core functionality. * Day 3: UI/UX design and integration. * Day 4 - 6: Functionality (JDGEN functionalities and making the widget embeddable) * Day 7: Testing and deployment * Resource Allocation: Chioma Otu will handle frontend development, UI/UX design, and integration. Risk Management: * Identify potential technical challenges early and address them promptly. * Perform rigorous testing to minimize bugs and ensure stability. ## 3. Requirements Functional Requirements: * The widget must generate job descriptions based on user input. * The descriptions should be customizable and accurate for the specified role. * Users should be able to specify the level of experience required for the role. * The widget should have a user-friendly interface. * Integration of widget. ## 4. Design Documentation System Architecture: * Frontend: React.js for the widget interface. * API: Integration with OpenAI API for job description generation. * Deployment: Hosting on Vercel.. UI/UX Designs: * Simple and intuitive interface for easy user interaction. * Clear call-to-action buttons for generating and copying descriptions API Documentation: ## 5. Development Process * Development Methodology: * Sprint Planning: * Code Repository: * Technical Specifications: ## 6. Project Outcomes * Final Deliverables: * Performance Metrics: * Client Feedback: ## 7. Lessons Learned * Challenges Faced: * Solutions Implemented: * Best Practices: ## 8. Appendices * Additional Documentation:
# OUTYN PROJECT DOCUMENTATION Prepared By: Chioma Otu Project Name: Outyn Web Date Prepared: 31/07/2024 ## 1. Project Overview Project Title: Outyn Web (Date idea suite) Project Duration: 2 months Project Team: 1. Emmanuel Stephen - Project Manager 1 2. Chioma Otu - Frontend Developer 3. Adebayo Sukurat - Product designer 4. Perpetua Urama - Project Manager 2 Objectives: * The primary objective of the Outyn app is to enhance social interaction and enjoyment by providing a user-friendly platform that simplifies the organization and planning of outings and events. The app aims to streamline the thought process in picking out dates, places and monetary Scope: * The Outyn app includes developing web with features such as method to solve date ideas problem, chatting with Date Idea Expert ChatBot. ## 2. Project Plan * Timeline: June - July Milestones: * Project planning and design * Complete Web UI * Create data for outing ideas * Add ChatBot functionality Resource Allocation: * Open AI Key * Collaborative workspace * Risk Management: Nil ## 3. Requirements * Functional Requirements: * User can browse date ideas arranged alphabetically. * User can search through dates idea * User can interact with Chatbot AI and get customized date solutions * System Architecture: * UI/UX Designs: * API Documentation: ## 5. Development Process * Development Methodology: Nil * Sprint Planning: Brainstorming, research and implementation. * Code Repository: [Github](https://github.com/Renaissance-Innovation-Labs/drop-s1-outing-planner) * Technical Specifications: ## 6. Project Outcomes * Final Deliverables: The final deliverables for the Outyn web app includes a design featuring a user-friendly interface with key screens such as splash screen, home page, explore page, A-Z dates idea UI, Random Dates UI and search, Chatbot UI and functionality such as starter chat template, user input, get places: location and price range. * Performance Metrics: 80% * Client Feedback: ## 7. Lessons Learned * Challenges Faced: Adding Images to date ideas and places with DALLE or Google Places Api * Solutions implemented without images, DALLE has a rate limit of five image generation per minute. * Best Practices: Making use of a better model which can source the web for images ## 8. Appendices * Additional Documentation: # Post Notes PROJECT DOCUMENTATION \ Prepared By: Idogun Favour Project Name: Post Notes Date Prepared: 25th July 2024 ## 1. Project Overview Project Title: Post Notes Project Duration: Start date: 5th June 2024 End date: 28th June 2024 Project Team: * Shammah Nei, * Idogun Favour Objectives: * To create a solution that helps people share messages that are understood to foster healthy relationships. Scope: A web app where * Users can register and confirm email, * Send and receive pairing requests. * Send notes to the pairings, * Receive notes, * Get an ai generated analysis of the sentiments behind the note and next actions for both recipient and sender. ## 2. Project Plan Timeline: * Week 1: Talking about the project and sharing responsibilities. * Week 2: Sharing responsibilities and working * Week 3: Creating the web app framework and sentiment analysis * Week 4: Presentation of product Milestones: Week one to two were set aside for knowing the responsibilities and how to go about them as well as working on them. Week three to four were set aside for finishing the frontend and backend as well as preparing for the demo presentation. Resource Allocation: * Time spent: A duration of one month * Personnel: Shammah Nei and Idogun Favour * Tools: Supabase, React, Python Risk Management: ## 3. Requirements Functional Requirements: Users should be able to: * Users can register and confirm email, * Send and receive pairing requests. * Send notes to the pairings, * Receive notes, * Get an ai generated analysis of the sentiments behind the note and next actions for both recipient and sender. ## 4. Design Documentation System Architecture: To enable a working web application there was need to: * Create the frontend and backend using tools like react, supabase and python. * Write codes to build the frontend and backend of this application. * Ensure that accounts can be created. * Create a database for every new account. * Ensure pairing can be done between two or more available accounts on the app. * Carrying out sentiment analysis on the posts made. * Get ai generated suggestions on the post made, for the sender and receiver. UI/UX Designs: None available API Documentation: ## 5. Development Process * Development Methodology: DevOps Development Methodology * Sprint Planning: * Code Repository: * Technical Specifications: ## 6. Project Outcomes Final Deliverables: So during internal use, we were able: * Get the web app running by sending posts to ensure the app is viable. Performance Metrics: This was measured based off of: * Personal reviews * Customer satisfaction * Customer reviews * Client Feedback: The clients were able to attest to its viability as a working web application ## 7. Lessons Learned Challenges Faced: These included: * Non encodement of the code for sentiment analysis * Lack of communication Solutions Implemented: These included: * Encoding of the code * Ensuring proper communication in the course of the project. * Best Practices: Implementation of the solutions ## 8. Appendices * Additional Documentation:
# Connector PROJECT DOCUMENTATION Prepared By: Josephine Abel Project Name: Connector Date Prepared: 25-07-24 ## 1. Project Overview Project Title: Compatibility Test Project Duration: 14 days Project Team: * Josephine Abel, * Jedidiah Oton, * Emmanuel Wogundu, * David Aroh OBJECTIVES: \ This is a mobile app or tool designed to provide people with a thorough understanding of their compatibility across various aspects of their relationship. SCOPE\ It uses a detailed questionnaire to gather information about their communication styles, values, financial habits, life goals, and conflict resolution strategies. Based on the responses, the tool generates a compatibility score and offers personalized feedback to help people identify strengths and areas for improvement. ## 2. Project Plan * Timeline: 14 days * Milestones: Brainstorms sessions, content description, design and presentation. * Resource Allocation: * Risk Management: Nil ## 3. Requirements * Functional Requirements: User-friendly interface * Detailed questionnaire covering key aspects of relationships * Compatibility analysis algorithms * Personalized feedback and recommendations ## 4. Design Documentation * System Architecture: * UI/UXDesigns: * API Documentation: * Development Methodology: * Sprint Planning: **Sprint 1: Week 1** Day 1: Requirements and Initial Setup Tasks: * Finalize detailed requirements and user stories. * Set up version control (GitHub). Day 2-4: Design and Prototyping Tasks: * Create wireframes and mockups using Figma. * Review and finalize the UI/UX design. Day 5: Frontend Setup Tasks: * Set up the frontend environment with jsx. * Develop the basic layout and navigation. Day 6-7: Questionnaire and Scoring Algorithm Tasks: * Implement the questionnaire interface. **Sprint 2: Week 2** Day 8-9: User Profiles and Dashboard Tasks: * Develop user profile management for ability to share with partner. * Implement the dashboard to display compatibility results. Day 10: Integration and Testing Tasks: * Integrate frontend. * Perform unit testing on core functionalities. Day 11-13: Bug Fixes and Improvements Tasks: * Address bugs and incorporate feedback from UAT. * Optimize performance and refine UI/UX. Day 14: Deployment Tasks: * Prepare and deploy the app to a staging environment. * Perform final checks and deploy to production. #### Technical Specifications Deployment: * Environment: Vercel (Frontend) * CodeRepository: : Compatibility Scoring Algorithm: * Input: User responses to the questionnaire * Process: Compare responses against predefined criteria * Output: Compatibility score and detailed analysis Frontend: * Language: JavaScript * Styling: Vanilla CSS ## 6. Project Outcomes Final Deliverables: Compatibility Test App * Frontend web application. * User registration. * Questionnaire interface. * Compatibility scoring algorithm. * Displaying compatibility results. Performance Metrics: * User Registration Time. * Waiting for partner time. * Question completion rate * Response Time * Score check * Client Feedback: ## 7. Lessons Learned Challenges Faced: * Integration issues: No API provided * Adding JIX to the code * Setting timer to the splash screen Solutions Implemented: * Generated JIX from the figma link. Best Practices: * Clear Requirements: Ensure requirements are well-defined and understood. * Iterative Development: Develop and test in small, manageable increments. * Code Reviews: Regular code reviews to maintain code quality and catch issues early. * User Testing: Involve real users early to gather feedback and improve usability. * Documentation: Maintain comprehensive and clear documentation for both developers and users. ## 8. Appendices * Additional Documentation:
# Programs Processes RIL Programs Department Standard Operating Procedure. Outline: * Pre event/Program * During an Event * Post event/Program * Checklist NB: This document serves as a template and guide for RIL’s programs department. Modifications are made only with approval from the Director, after being vetted by the Programs manager. RIL programs differ in requirements and may be unique in nature. This document therefore provides a holistic guide on how to approach any program regardless of its peculiarity. Hence, edits may be made to suit a particular program, on the basis of a proper understanding of its context. I.e Details of this document are applicable in all cases where necessary, and deferred solely where inapplicable. ### Pre event/program 1.1 Program Proposal and Planning * Propose event/program * Define objectives * Outline goals and alignment to RIL vision * Research on existing similar programs * Determine all necessary criteria/resources required. 1.2 Program Development * Create program plan * Include and define all operations, stakeholders and outcomes. * Give detailed breakdown of all aspect of the program, duration, additives and/or USPs * Determine necessary steps organization and participants must take. E.g. Registration, Data forms, Reporting structure, Event/Program needs, structure & setup. * Add success metrics and risks involved. 1.3 Resource Allocation * Create budget & Allocate resources (where necessary) * Submit/Share documentation with involved team members for approval/implementation. * Ensure all stakeholders are detailed on roles/responsibilities * Assign personnel to instruct, supervise, manage and support- as the case may be. * Secure required facilities and equipment, any other tool necessary. 1.4 Marketing and Promotion * Identify the target audience. * Work with PR and other departments where necessary. * Develop a marketing strategy, including branding and pricing. * Utilize multiple marketing channels and adjust based on performance. 1.5 Final program setup (physical/online) ### During an event/program 1.1 Program Execution * First step: Orient * Define reporting system * Ensure the program runs according to the program plan. * Close monitoring and control. * Effect change management where necessary * Observe and document * Create follow-up and feedback loops * Collect data * Capture moments. ### Post event/program 1.1 Feedback & Evaluation * Program overall review * Check for alignment with objective * Measure with success metrics * Define and allocate impact 1.2 Reporting * Create reports. * Organize and file all corresponding documents. * Templatize for future programs. Docs: Fill the questions [Things to consider when creating a new program (START HERE](https://docs.google.com/document/d/1LQAePzNUQ8uGQGbMed8-ieP-WeByw2WgAoLLIbIFAM0/edit)\ \
# Programs Schema ⚙️ PROGRAM MANAGEMENT SCHEMA & FLOW **Schema Overview**
StageCore DepartmentCollaborative DepartmentsPrimary Objective
1. Planning StageProgram ManagementPR/Marketing, Product Development, Facility ManagementDefine goals, concept, timeline, and logistics
2. Pre-Event StageProgram ManagementPR/Marketing, Facility Management, Product DevelopmentExecute plans, mobilize resources, and coordinate publicity
3. Event StageProgram ManagementAll DepartmentsDeliver program seamlessly and ensure participant satisfaction
4. Post-Event StageProgram ManagementPR/Marketing, Product Development, Facility ManagementCapture insights, analyze outcomes, report performance
### Collaboration Points: * Regular meetings: Weekly/bi-weekly interdepartmental meetings to discuss progress, address challenges, and plan ahead. * Shared communication platform: Use of slack channel for real-time updates, task management, and document sharing via google drive. * Cross-departmental teams: Formation of temporary teams for specific program needs (e.g., hackathon logistics, meetups). * Standardized processes: Clear and documented procedures for tasks like venue booking, participant onboarding, and online feedback collection. # Programs Department **ROLES & RESPONSIBILITIES**
StageResponsibilitiesTimeline
PlanningDefine objectives, develop project charter, create budget, identify partners, and assign departmental roles.4–6 weeks before event
Pre-EventMonitor readiness, ensure resource allocation, conduct risk assessment, finalize event schedule.2–3 weeks before event
EventSupervise execution, handle coordination among departments, manage guests, troubleshoot issues.Day(s) of event
Post-EventCollect reports, conduct debrief sessions, develop post-event evaluation and recommendations.Within 5–7 days after event
**CHECKLIST**
CategoryTaskCheckbox
ObjectivesDefine event goals and success metrics☑️
BudgetDraft and approve budget☑️
PartnershipsIdentify and confirm collaborators/sponsors☑️
ScheduleCreate full program timeline☑️
CoordinationWeekly inter-departmental meetings☑️
DocumentationCreate attendance forms, program briefs, run sheet☑️
Post-EventCollect reports, debrief, write post-event evaluation☑️
# PR/Marketing **ROLES & RESPONSIBILITIES**
StageResponsibilitiesTimeline
PlanningDevelop communication strategy, design media/publicity plan, define target audience.4–6 weeks before event
Pre-EventLaunch promotional campaign, create media kits, manage social media and press relations.2–3 weeks before event
EventCoordinate press/media coverage, manage branding materials, live social media updates.During event
Post-EventPublish recap content, share photos/videos, E-Journal, track engagement analytics, and maintain media relationships.Within 5 days post-event
**CHECKLIST**
CategoryTaskCheckbox
BrandingDevelop event theme identity (logo, design)☑️
MediaCreate press release and invitation☑️
Social MediaRoll out campaign (pre-event hype)☑️
ContentPrepare promotional materials (flyers, videos)☑️
Event CoverageSet up media team, live stream, real-time updates☑️
Post-EventPublish thank-you posts, recap video, engagement analytics☑️
# Product Development Team **ROLES AND RESPONSIBILITIES**
StageResponsibilitiesTimeline
PlanningConceptualize program theme, develop materials (content, products, kits, or demos) aligned with objectives.4–5 weeks before event
Pre-EventFinalize product samples, presentations, or demo materials; coordinate with PM and PR teams.1–2 weeks before event
EventShowcase product/service, manage experiential engagement (demo booth, testing, presentation).During event
Post-EventGather user feedback, document insights for product improvement, and update repository.Within 7 days post-event
**CHECKLIST**
CategoryTaskCheckbox
ConceptAlign theme with event goal☑️
DesignCreate supporting materials (slides, product kits, demos)☑️
TestingReview product/experience readiness☑️
ShowcaseExecute demo or presentation☑️
FeedbackGather participant insights☑️
ImprovementUpdate and iterate on learnings☑️
# Facility Management **ROLES AND RESPONSIBILITES**
StageResponsibilitiesTimeline
PlanningInspect potential venues, estimate technical and logistics requirements (power, seating, safety, etc.).4–6 weeks before event
Pre-EventSet up venue, ensure utilities are functional, arrange signage, coordinate security and sanitation.1–2 days before event
EventOversee facility readiness, provide on-ground technical and maintenance support, manage crowd flow.During event
Post-EventSupervise clean-up, restore venue condition, document facility performance issues.Within 1–2 days post-event
**CHECKLIST**
CategoryTaskCheckbox
VenueConfirm venue and layout☑️
UtilitiesCheck lighting, sound, seating, AC, etc.☑️
SetupArrange signage, banners, logistics☑️
SafetyEnsure emergency and first aid readiness☑️
On-siteManage crowd control, cleanliness, and power☑️
ClosureClean-up, restore venue, submit report☑️
# Collaboration Flow **Program Manager**\ │ \ │---------**PR/Marketing (Publicity, Media, Brand)** \ │ │ \ │ └── Coordinates audience engagement + brand visibility \ │ \ │--------**Product Development (Program Content & Experience)** \ │ │ \ │ └── Designs the experience participants interact with \ │ \ │---------**Facility Management (Venue & Logistics)** \ │ \ └── Ensures smooth physical execution environment # AI Lab ### 1. Program Overview {% hint style="success" %} The RIL AI Lab is a structured, membership-based innovation program designed to enable builders, engineers, designers, and technologists to experiment, prototype, and ship AI-powered solutions. \ \ The Lab prioritizes outputs over instruction, systems over supervision, and visibility over certificates. Members work in monthly cycles to explore AI use cases, build functional demos, and showcase outcomes through a disciplined demo-driven cadence.\ \ This document defines the operating model, governance, tooling, and enforcement mechanisms required to run the program seamlessly with minimal manual oversight. {% endhint %} ### 2. Program Objectives Primary Objectives * Enable consistent AI experimentation and rapid prototyping * Produce portfolio-grade demos, tools, and workflows monthly * Identify high-performing builders for advanced RIL initiatives * Reduce coordination overhead through automation-first systems Secondary Objectives * Create a visible AI innovation culture within RIL * Build a reusable pipeline of ideas that can mature into products * Position RIL as a regional hub for applied AI innovation ### 3. Target Participants The AI Lab is designed for: * Software engineers * Data scientists * Product builders * Designers working with AI-enabled workflows * Technologists transitioning into applied AI {% hint style="warning" %} Pre-requisite: Participants must be capable of independent execution. The Lab does not provide foundational AI training. {% endhint %} ### 4. Membership Structure 4.1 Membership Tiers 1\. Builder Member (Core Tier) Access: * Monthly AI problem prompts * Weekly demo sessions * Shared AI tools and service credits * Community channels and repositories Obligations: * Minimum of one demo submission per month * Participation in at least two weekly demo session Fellow (Advanced / Invite-Only) {% hint style="warning" %} Eligibility:\ Consistent high-quality outputs\ Peer recognition and facilitator endorsement {% endhint %} Additional Benefits: * Increased AI tool credits * Leadership of mini-projects or themes * Priority consideration for paid RIL work * Public recognition through RIL channels ### 5. Program Cadence The AI Lab operates on a fixed monthly cycle with mandatory weekly demos built into the cadence. This structure ensures continuous progress, visibility, and accountability without ad‑hoc follow‑ups. Week 1 – Prompt Release & Kickoff * 3–5 AI problem prompts released * Members may select a prompt or propose a custom project * Custom proposals require async approval * Members signal intent to demo during the month Week 2 – Build + Weekly Demo Session * Independent build period * Weekly catch‑up demo & insights session * Members may demo early progress, experiments, or pivots Week 3 – Build + Weekly Demo Session * Continued build period * Weekly catch‑up demo & insights session * Focus on refinement, learnings, and blockers Week 4 – Demo Week & Close‑Out * Final weekly demo & insights session * Formal demo showcase (60–90 minutes) * Evaluation, scoring, and documentation {% hint style="info" %} Monthly Participation Requirement\ 1\. Each member must complete a minimum of two (2) weekly demos per month\ 2\. Demos may occur in any weekly session within the cycle\ 3\. Failure to meet the minimum demo requirement results in loss of eligibility for awards, tool access, and renewal into the next cycle {% endhint %} End of Month * Innovator of the Month selection * Public showcase and write‑ups * Tool access reset and cycle restart ### 6. Weekly Demo & Insights Sessions The AI Lab runs weekly catch‑up demos and insights sessions to maintain momentum, accountability, and shared learning without introducing heavy coordination overhead. * Frequency: Weekly * Duration: 45–60 minutes Format: * 3–5 member demos (5 minutes each) * 10–15 minutes of shared insights (patterns, tools, failures, wins) * Live screen-sharing only (no slide decks) Purpose: * Surface progress early * Encourage peer learning through real builds * Identify promising ideas and blockers quickly Rules: * Fixed day and time each week * Attendance is tracked automatically * Members must demo at least once per month * Two missed sessions in a month results in loss of eligibility for awards and tool access in the following cycle ### 7. Tooling & Infrastructure 7.1 Community & Communication Slack 7.2 Project Tracking * Notion workspace * Standardized member project templates * Automated status tracking 7.3 Code Repositories * Central GitHub organization * One repository per member per month * Standard project scaffolding provided 7.4 Demo Submissions * Centralized submission form * Automated demo agenda generation * Submission windows enforced programmatically ### 8. Automation & Enforcement The AI Lab is governed by systems, not manual follow-up. Automated Processes * Scheduled prompt publishing * Demo sign-up and slot allocation * Attendance and submission tracking * Tool credit usage monitoring * Eligibility checks for awards and renewal Enforcement Rules * No demo submission → no renewal * No repository → no recognition * Repeated inactivity → automatic removal All enforcement actions are system-triggered and non-negotiable. ### 9. AI Tools & Resource Access The Lab provides shared access to a rotating set of AI tools, which may include: * Large language model APIs * Vector databases * Agent frameworks * Search and data ingestion tools Usage Policy: * Credits are capped per member * Usage is monitored * Abuse results in automatic access revocation ### 10. Recognition & Incentives Innovator of the Month * Awarded based on: * Technical execution * Originality * Practical relevance * Demo quality Benefits: * Public feature across RIL platforms * Certificate of recognition * Additional tool credits * Priority access to paid RIL initiatives ### 11. Governance Model Roles & Responsibilities Program Manager * Owns program operations and reporting * Oversees automation and tooling AI Lab Lead * Facilitates demos * Releases prompts * Enforces program rules RIL Leadership * Strategic oversight * Monthly judging participation * Direction setting ### 12. Success Metrics The program is evaluated monthly using the following metrics: * Percentage of active members submitting demos * Number of shipped prototypes * Tool usage efficiency * Member retention beyond two cycles * Number of projects graduating into RIL initiatives {% hint style="danger" %} Failure to meet benchmarks over two consecutive cycles triggers a program review. {% endhint %} ### 13. Review & Iteration {% hint style="success" %} This document is reviewed quarterly. Program structure, tooling, and incentives may evolve based on data and outcomes. {% endhint %}
# Kids Code Club(KCC) ### 1. Introduction > The Kids Code Club (KCC) is an initiative of Renaissance Innovation Lab designed to introduce children and teenagers (ages 8–16) to innovation and technology in a fun, engaging, and structured way. Through hands-on learning, creativity, and collaboration, the Club aims to empower young learners with the skills, confidence, and curiosity needed to thrive in the digital future. \ > \ > As part of our mission to democratize access to technology education, we are expanding the Kids Code Club into secondary schools across the state, creating a vibrant network of young innovators equipped to lead the next wave of digital transformation in Africa. ### 2. Vision > To build a community of creative problem-solvers and young innovators who understand, build, and leverage technology to create solutions for their communities and the world. ### 3. Mission > To provide early exposure to digital literacy, coding, and design thinking, helping students develop a growth mindset, computational thinking, and innovation-driven habits through practical learning experiences. ### 4. Objectives of the Expansion ### The expansion of the Kids Code Club into secondary schools aims to: 1. Integrate tech education into school environments in an accessible and engaging way. 2. Equip students (ages 10–16) with foundational knowledge in coding, robotics, and design thinking. 3. Foster collaboration between schools and tech communities, enabling mentorship and project-based learning. 4. Encourage innovation-led problem-solving among students through challenges, hackathons, and demo days. 5. Identify and nurture young tech talents early, bridging the digital skills gap in underserved communities. ### 5. The Kids Code Club Model The New Kids Code Club will operate as an in-school program, depending on each school’s schedule. Each Club will be guided by trained facilitators and mentors from Renaissance Innovation Lab, using a curriculum designed to blend creativity, logic, and real-world applications. #### Program Components * Coding Fundamentals: Learning programming basics through visual and interactive platforms like Scratch, Blockly, and Python. * Robotics and Hardware: Introduction to robotics kits, sensors, and IoT concepts to bring code to life. * Design Thinking Workshops: Hands-on sessions teaching problem-solving, creativity, and product design. * Innovation Challenges: Monthly problem-solving tasks that allow students to apply their learning to community-based issues. * Showcase and Demo Day: An annual event where students present their projects and innovations. ### 6. Implementation Plan #### Phase 1 – Pilot Launch ( Q4 2025-Q1 2026) * Identify and onboard 3-5 partner secondary schools. * Train teachers or school ICT leads as Club Coordinators. * Set up digital learning kits (laptops, robotics kits, and internet access). * Launch the Kids Code Club curriculum and monitor progress. #### Phase 2 – Scale and Community Integration (Q2–Q3 2026) * Expand to 10 additional schools, creating regional hubs of learning. * Organize Kids Innovation Bootcamps and inter-school coding challenges. * Build a mentorship network connecting students to professionals and innovators. #### Phase 3 – Sustainability and Impact (Q4 2026 and Beyond) * Develop a student ambassador system for peer-to-peer learning. * Collaborate with government education boards and NGOs for broader reach. * Establish partnerships for funding, mentorship, and technology support. ### 7. Expected Impact * 500 students trained in coding and innovation within the first year. * Increased participation of young girls in STEM education. * Creation of a pipeline of young innovators and problem-solvers. * Strengthened partnerships between schools, communities, and the tech ecosystem. * Enhanced digital literacy across partner schools. ### 8. Partnership and Support Opportunities We aim to collaborate with: * Schools - to host and integrate the Club. * Tech Organizations & NGOs - to provide mentorship, tools, and training support. * Corporate Sponsors - to fund learning kits, laptops, and innovation grants for students. {% hint style="success" %} The expansion of the Kids Code Club represents a bold step toward shaping Africa’s digital future-one classroom at a time. By introducing technology and innovation to children early, Renaissance Innovation Lab aims to invest and build a generation that will not just consume technology but create it. {% endhint %}
# Game Lab #### Lab Overview The Game Lab is a creative and technical innovation program focused on game development, interactive media, storytelling, and simulation-based learning. It empowers young people to build games not just for entertainment, but for education, culture, and social impact. #### Objectives * Develop technical and creative skills in game design and development * Introduce participants to careers in gaming, XR, and creative tech * Use games as tools for learning, advocacy, and behavior change # Robotics Lab #### Lab Overview The Robotics Lab is a hands-on, experiential learning program designed to introduce tertiary learners to robotics, hardware engineering, automation, and applied STEM problem-solving. The lab bridges theory and practice, preparing young learners for future careers in engineering, AI, robotics, and deep tech. #### Objectives * Build early exposure to hardware and robotics innovation * Strengthen STEM confidence and problem-solving capacity among students * Create a pipeline into advanced tech learning pathways * Encourage participation of girls and underrepresented groups in robotics # Brand Guide {% stepper %} {% step %} ### User Guidelines Renaissance Innovation Labs brings together brains, methodology, and technology to address systemic challenges too big for just one organization to handle by engaging diverse participants in open collaboration to create, elaborate and prototype disruptive solutions. We are surprising and inspiring. In terms of design, this means more options and fewer rules, ultimately also a much larger and more vibrant range of expression and more power as a result. We are attached to multiple colors of the renaissance, and these colors can be applied to the sub-brands, but not to the logo and logotype itself. It is important to stay consistent with it. To communicate our brand in a unique way, every element of our visual identity has been chosen to strengthen the idea about Renaissance Innovation Labs and what it offers. Do not in any way, attempt to use the brand assets in ways that is not appealing to the brand and does not help us stay consistent. {% endstep %} {% step %} ### Icon If there is a message, our icon acts as an opening or a conclusion. In other cases, they can be placed anywhere and in any size (within the brand space). When displayed on print or on screens, it important to consider it nothing less than a powerful graphic symbol - plain, simple and with no special effects - just simply in black or white, which depends on the background. {% endstep %} {% step %} ### Logo Our logo is composed of our icon representing our openness and innovative thinking and logotype set in Open Sans. Our primary logo is the horizontal version, we do not have a stacked version. Please refrain from creating one. Logo (International Use) - In some cases, especially for international purposes, the logo is also a property of Philanthrolab and that version of the logo should be used. The logos can be used only by persons or companies who have been granted the right to do so by contractual agreement. Our logo works well on small sizes just as it works well on big sizes. Use the guideline for proper implementation. In the case of the international version, it doesn’t work well, as the text may end up becoming too small and not readable. {% endstep %} {% step %} ### Sub-Brands Use Cases These are any external brands created and offered by Renaissance Innovation Labs. Use the same amount of space on the logo, the typeface. Open Sans set at all caps with a tracking set at 240px {% endstep %} {% step %} ### Color White, Black, and Blue are our colors. We also have secondary colors based on the Renaissance Colors. These secondary colors are used mainly for sub-brands. {% endstep %} {% step %} ### Brand Colors White CMYK: 0/0/0/0 HEX: FFFFFF RGB: 255/255/255 Brand Colors Black CMYK: 74/64/61/79 HEX: 212120 RGB: 33/33/32 Blue CMYK: 81/51/0/0 HEX: 177AE5 RGB: 23/122/229 Secondary Colors Sky Blue CMYK: 71/21/0/0 HEX: 2EA3E5 RGB: 46/163/229 Blue Green CMYK: 69/0/23/0 HEX: 29BDCC RGB: 41/189/204 Green CMYK: 69/0/72/0 HEX: 29CC6E RGB: 41/204/110 **This can be used to support the color palette** CMYK: 55/41/37/21 HEX: 73797F RGB: 115/121/127 CMYK: 46/34/31/11 HEX: 8F9499 RGB: 143/148/153 CMYK: 36/25/25/5 HEX: ABAFB2 RGB: 175/175/178 CMYK: 25/18/17/1 HEX: C7C9CC RGB: 199/201/204 CMYK: 13/9/10/0 HEX: E3E4E5 RGB: 227/228/229 {% endstep %} {% step %} ### Typography Our choice of font is Open Sans, this is because it’s both legible and readable. {% endstep %} {% step %} ### Don'ts Don’t use any other color apart from White or Black on the logo. Don’t use any other color apart from White or Black on the logotype. Don’t set the logo or icon in a containing shape. Don’t add gradients or any other form of effect on the logo. Don’t rotate the icon Don’t rotate the logo Don’t create a stacked version of the logo Don’t shrink the international version of the logo {% endstep %} {% endstepper %} [View PDF](https://drive.google.com/file/d/11Zm_Ydwu_vbBcKPbtVrvBV7GRUcd6wTE/view?usp=sharing) # Media Kit {% tabs %} {% tab title="Voice Style" %} Our brand's voice and tone serve as the verbal reflection of our visual identity. How we introduce RIL to our audiences significantly impacts their perception of us, potentially leading to the creation of brand advocates or the loss of a customer. **Voice** represents our distinct verbal character, which remains consistent with our brand. **Tone**, on the other hand, allows us to adjust our voice to suit different contexts. For instance, you may adopt one tone when out with friends and another when meeting with your boss. RIL adapts its tone to suit various interactions, including product UX, customer support, advertising, social media, and any other public-facing scenarios. The upcoming sections will cover some fundamental aspects of voice and tone. {% endtab %} {% tab title="User Guidelines" %} Renaissance Innovation Labs brings together brains, methodology, and technology to address systemic challenges too big for just one organization to handle by engaging diverse participants in open collaboration to create, elaborate and prototype disruptive solutions. \ We are boundless and inspiring. In terms of design, this means more options and fewer rules, ultimately also a much larger and more vibrant range of expression and more power as a result. We are attached to multiple colors of the renaissance, and these colors can be applied to the sub-brands, but not to the logo and logo type itself. It is important to stay consistent with it. To communicate our brand in a unique way, every element of our visual identity has been chosen to strengthen the idea about Renaissance Innovation Labs and what it offers. To communicate our brand voice and position to everyone. Do not in any way, attempt to use the brand assets in ways that is not appealing to the brand and does not help us stay consistent. {% endtab %} {% endtabs %} ## Social Media Guide {% hint style="success" %} IMAGES WITHOUT TEXT * Full-screen image consistent with RIL visual imager * Format 1500x1500px or any square * Use RGB color tone * The saturation of the image can be adjusted if needed * RIL logo not required in this type of image * This works for mostly Event images {% endhint %} # How we tell RIL Stories of Innovation
StepActivityResponsible RoleGoal
1Innovation Story ScoutingPR/Marketing LeadProactively identify internal projects, team members, or successful initiatives that exemplify Renaissance Innovation Lab's agenda.
2Content Plan DevelopmentContent CreatorCreate a storyboard/script outlining the narrative arc (Problem-Innovation-Impact). Identify required footage/imagery.
3Production/CaptureDesigner/Content Creator/LeadCapture, edit, and produce the video or image assets, ensuring high-quality production standards.
4Impact ReviewPR/Marketing LeadReview the content to ensure it clearly articulates the innovative value and is inspirational/educational.
# Brand Evangelism
StepActivityResponsible RoleGuideline
1Channel StrategyPR/Marketing ManagerDetermine the optimal platform for each piece of content (e.g., LinkedIn for thought leadership, Instagram for visual storytelling, X/Twitter for breaking news).
2Content SchedulingPR/Marketing ManagerSchedule posts using a consistent rhythm and peak audience times. Ensure cross-platform content is adapted, not merely duplicated.
3Engagement MonitoringPR/Marketing ManagerActively monitor comments, direct messages, and mentions. Respond to all non-spam/non-negative comments within 2 hours during business hours.
4Brand Evangelism

EVERYONE

Team members must share organizational achievements and key content from their personal/professional profiles (where appropriate) to amplify the message. Be the first source of positive news about the Lab.
# Measurement & Review
StepActivityResponsible RoleFrequency
1Performance TrackingPR/Marketing LeadTrack key metrics (Engagement Rate, Impressions, Click-Through Rate, Follower Growth) for all published content.
2Weekly/Monthly ReportPR/Marketing LeadCompile a report summarizing campaign performance, brand sentiment, and lessons learned.
3Quarterly Strategy ReviewPR/Marketing Lead & COOReview the past quarter's performance against the Innovative Agenda goals and adjust the SOP/Strategy as needed.
# Guideline 📦 PROCUREMENT PROCESS #### **1. Overview** The procurement process at Renaissance Innovation Labs ensures that all purchases and sales are conducted in a transparent, accountable, and well-documented manner. This process applies to both internal requisitions and external transactions involving clients or vendors. *** #### **2. Purchase Requests (Incoming Procurement)** When a team member or department identifies the need to purchase goods or services, the following steps must be followed: **Step 1: Obtain a Proforma Invoice** * The requester must first obtain a **Proforma Invoice** (an estimated quote) from the intended vendor or service provider. * The Proforma Invoice should include the item description, quantity, unit cost, total cost, vendor details, and validity period. **Step 2: Complete a Requisition Form** * The requester must fill out the company’s standard **Requisition Form**, providing clear justification for the purchase. * The **Proforma Invoice must be attached** to the requisition form as supporting documentation. **Step 3: Internal Review & Approval** * The requisition and attached invoice will be reviewed by the line manager or designated approving authority. * If approved, it will be forwarded to Finance/Operations for fund release and procurement processing. **Step 4: Procurement & Payment** * Upon final approval, the Finance or Procurement Officer will initiate the purchase and facilitate payment to the vendor according to the agreed terms. *** #### **3. Outgoing Transactions (Sales or Internal Transfers)** When Renaissance Innovation Labs sells or transfers items or services to clients or other stakeholders: **Step 1: Prepare an Internal Invoice** * The responsible team (e.g., Sales, Programs, or Admin) must prepare an official **Internal Invoice** detailing the item/service, pricing, and recipient information. **Step 2: Complete a Requisition Form** * A **Requisition Form** must be completed for documentation purposes and **the Internal Invoice must be attached**. **Step 3: Review & Dispatch** * The requisition will be reviewed and approved by management. * Once approved, the item or service may be dispatched, delivered, or executed. *** #### **4. Client Billing and Revenue Collection** In all cases where funds are to be collected from clients: * **An invoice must be issued to the client** before any request for payment can be made. * No verbal or informal payment requests are permitted. * Invoices must follow standard formatting and be approved by the Finance Team. *** #### **5. Notes & Compliance** * All procurement activities must align with Renaissance Innovation Labs' financial policies and budgetary controls. * Missing documentation (e.g., proforma invoice or requisition form) will delay processing and may result in non-approval. * All forms and templates are available on the internal drive or may be requested from the Operations Department. # FM SOP ## **STANDARD OPERATING PROCEDURE (SOP)** ### **FACILITY MANAGEMENT – RIL** *** ## **PURPOSE** This Standard Operating Procedure (SOP) establishes clear guidelines for managing all RIL facilities, ensuring efficiency, safety, cleanliness, and seamless support for daily operations *** ## **SCOPE** This SOP applies to: * The Facility Manager (FM) * Housekeeper(s) * Any staff requiring access, facility resources, or maintenance interventions * All RIL offices, labs, equipment, and utilities *** ## **ORGANIZATIONAL STRUCTURE & REPORTING** #### **Facility Manager** The Facility Manager is the **overall head of Facility Management** and is responsible for the maintenance, safety, and physical readiness of all RIL workspaces. #### **Housekeeper** * The Housekeeper **reports directly to the Facility Manager**. * The Facility Manager assigns tasks, supervises execution, and evaluates performance. *** ## **ROLES & RESPONSIBILITIES OF THE FACILITY MANAGER** #### **General Facility Oversight** The Facility Manager shall: 1. Ensure all facilities (office, lab) are clean, functional, and available for use. 2. Monitor environmental standards (cleanliness, power supply, water). 3. Conduct routine inspections and maintain a facility log. 4. Document and report facility risks, damages, or hazards. *** ## **ACCESS CONTROL MANAGEMENT** #### **Access Authority** * The Facility Manager is the **sole authority responsible for granting access and entry** into the Office and Lab. * This includes: * Opening and closing the facility * Issuing keys when authorized * Keeping record of all persons who enters the spaces *** ## **INTERNET PASSWORD & NETWORK SECURITY MANAGEMENT** #### **Password Ownership** * The Facility Manager is the **possessor and distributor** of the company’s internet/Wi-Fi password. * Password changes must be documented and communicated only to authorized users. #### **Distribution Guidelines** * Password is shared strictly to Registered Innovators and Staff. * Unauthorized sharing of internet credentials is prohibited. *** ## **REQUISITION & MAINTENANCE WORKFLOW** #### **Requisition Responsibility** Whenever the Facility Manager identifies the need to repair, replace, purchase, or upgrade any facility item, the following procedure applies: #### **Requisition Process** 1. **Identify Need:** FM inspects, confirms fault/requirement. 2. **Prepare Requisition Form:**\ The form must include: * Item/Service Requested * Category (Maintenance, Repair, Replacement, Consumables, Utilities) * Reason * Cost Estimate (with vendor quote attached if applicable) 3. **Submit to COO:** * FM sends requisition form to the COO for review and approval. 4. **Approval:** * Work cannot proceed without COO approval. 5. **Execution & Documentation:** * After approval, FM executes purchase or repair and submits evidence (receipt, photos, vendor invoice). 6. **Update Facility Log:** * FM records the completed action in the Facility Maintenance Log. *** ## **HOUSEKEEPING MANAGEMENT** The Facility Manager shall supervise housekeeping operations by ensuring: * The lab is to be cleaned 3 of 5 times Weekly * Weekly deep-cleaning routines * Timely waste disposal * Availability of cleaning supplies * Adherence to hygiene and safety standards * Reporting any facility irregularities immediately *** ## **DOCUMENTATION & REPORTING** The Facility Manager shall maintain the following documents: * Requisition Forms & Approvals * Facility Maintenance Log * Internet Password Distribution Log * Facility Report (weekly) All logs must be updated **weekly** and shared with the COO **monthly**. *** ## **COMPLIANCE & REVIEW** * All staff must comply with the access and facility usage rules stated in this SOP. * Violations must be reported immediately to the COO. * The SOP shall be reviewed every **12 months** or when operational needs change. *** # FM Role in Programs Execution The Facility Manager plays a critical role in all program stages: *** ### **PLANNING STAGE (4–6 weeks before program)** * Conduct facility and venue inspection to confirm suitability for the planned program. * Estimate technical and physical requirements (seating, power, lighting, equipment, accessibility). * Provide Program Manager with facility needs assessment. * Identify facility risks and propose mitigation. *** ### **PRE-EVENT STAGE (1–2 days before program)** * Set up the event space according to approved layout (chairs, equipment, banners, tables, signage). * Verify power supply, backup power, network readiness, air conditioning, and overall facility cleanliness. * Coordinate with security, housekeeping, and any external vendors. * Ensure all materials, tools, and utilities are in place and functional. *** ### **EVENT DAY DUTIES** * Arrive before the program team to open the facility. * Monitor facility readiness throughout the event. * Provide on-ground support for: * Power * Seating adjustments * Technical issues * Sanitation * Crowd flow and access control * Respond to emergencies (electricity, water, ventilation, safety issues). * Ensure restrooms, entrances, and common areas remain clean and operational. *** ### **POST-EVENT DUTIES (1–2 days after program)** * Lead clean-up and facility restoration to pre-event condition. * Conduct inspection for damages and prepare a report. * Document facility performance and share insight with Program Manager. * Update facility log for record-keeping. # Staff Welfare ### **PURPOSE** This SOP defines the company’s standards for engaging and supporting employees during major life events, celebratory, critical, or unfortunate. It ensures compassionate, consistent, and fair treatment across all staff. *** ### **SCOPE** Applicable to all full-time, Interns and understudy employees of RIL. *** ### **HR LEADERSHIP STRUCTURE** #### **Role of the COO** * The **COO currently doubles as the Human Resources Manager**, carrying responsibilities for both operational oversight and people management * All HR activities, engagement, welfare approvals, leave administration, condolence actions, and staff celebrations are executed under the **direct authority** of the COO. * Any welfare or HR-related request must therefore be routed to the COO for review, authorization, and action. *** ### **GENERAL GUIDING PRINCIPLES** 1. The company will maintain fairness, empathy, and professionalism in all welfare responses. 2. Because the COO serves as HR Manager, **all approvals, communications, and decisions are issued from the COO’s office**. 3. Confidentiality is mandatory when handling sensitive staff matters. *** ### **STAFF WELFARE CATEGORIES & COMPANY ACTIONS** ### **WEDDING (Staff Wedding)** #### **Company Actions** * Official wedding congratulatory letter sent by the COO * Financial gift approved and issued by the COO * Optional: Wedding gift package * Company representation at the wedding (delegation arranged by COO) #### **Leave** * 3–5 days of wedding leave upon approval by the COO #### **Process** * Staff notifies COO at least 4 weeks prior * COO approves welfare package and attendance plan *** ### **5.2 STAFF BIRTHDAY** #### **Company Actions** * Official birthday message from COO * Birthday Cake would be shared at the end of every month * Optional internal celebration #### **Process** * COO ensures HR staff manages the Birthday Calendar * *** ### **5.3 CHILD BIRTH (Staff or Spouse)** #### **Company Actions** * Congratulatory message from the COO * Baby Gift or Baby Cash Package #### **Leave** * Female staff: Maternity leave * Male staff: 7-14 days paternity leave, approved by COO #### **Process** * Staff informs COO immediately * COO documents and approves support *** ### **BEREAVEMENT – DEATH OF IMMEDIATE RELATIVE** #### **Immediate Relative Definition** Father, Mother, Sister, Brother, Spouse, Child #### **Company Actions** * Official Condolence Letter from COO * Condolence visit arranged directly by COO * Financial support or condolence package #### **Leave** * 1 month bereavement leave approved by MD #### **Process** * COO contacts staff within 24 hours * COO organizes delegation for visit or burial representation *** ### **DEATH OF EXTENDED FAMILY RELATIVE** #### **Company Actions** * Condolence message * Token support (optional) #### **Leave** * 3 day leave or compassionate extension *** ### **DEATH OF A STAFF MEMBER** #### **Company Actions** * Official announcement from COO * Company suspension of non-critical operations (if necessary) * Visit to the family * Funeral financial support * Company representation at the burial * COO leads next-of-kin documentation and benefits processing * Counseling or morale support for affected departments #### **Additional Actions** * Salary payout for the month * Staff voluntary contribution support * Departmental restructuring or role realignment *** ### **MEDICAL EMERGENCY OF STAFF** #### **Company Actions** * Hospital visitation by COO delegate * Possible medical support * Approved sick leave #### **Process** * Staff or family notifies COO * COO confirms and approves support *** ### **LONG SERVICE AWARDS** #### **At Milestones (3, 5, 7 Years)** * Appreciation message signed by COO * Recognition gift * Optional: Public acknowledgement at staff retreat or town hall *** ### **COMMUNICATION WORKFLOW** #### **When Event is Positive** * COO drafts or approves congratulatory communication * COO approves welfare package #### **When Event is Negative** * COO verifies information * COO prepares official condolence announcement * COO organizes visitation, support, and company representation *** *** ## **SOP COMPLIANCE & REVIEW** * All welfare actions and leave provisions require COO approval. * Violations, misuse, or false claims will be addressed through disciplinary processes. * The SOP will be reviewed annually or whenever leadership structure changes.