<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Bayo Olaleye on Medium]]></title>
        <description><![CDATA[Stories by Daniel Bayo Olaleye on Medium]]></description>
        <link>https://medium.com/@danielolaleyebgmail.com?source=rss-7959b600224a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kMSEeJHV9NPL8E0U6GUDDg.png</url>
            <title>Stories by Daniel Bayo Olaleye on Medium</title>
            <link>https://medium.com/@danielolaleyebgmail.com?source=rss-7959b600224a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:37:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danielolaleyebgmail.com/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[THRASHBETA]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/thrashbeta-a2e4ced46f31?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2e4ced46f31</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 12:45:02 GMT</pubDate>
            <atom:updated>2026-04-07T12:45:02.536Z</atom:updated>
            <content:encoded><![CDATA[<p>By Danel Bayo Olaleye</p><p><strong>Capstone Team: </strong>Team 1<br><a href="https://thrashbeta.vercel.app/"><strong>Live Web App</strong></a><strong><br></strong><a href="https://trashbeta.onrender.com/"><strong>Public API Base URL</strong></a><strong><br>Report Date: </strong>February 28, 2026<br><strong>Project: THRASHBETA (SMART WASTE MANAGEMENT AND REPORTING SYSTEM)</strong></p><h3>Table of Contents</h3><ol><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.anw9l5gghlps"><strong>Project Governance &amp; Team Roster</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.3lwx5zdovma0"><strong>Executive Summary</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.dgog51htplyh"><strong>The TrashBeta Story</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.zd30lwi88d5d"><strong>Integrated Project Timeline and Deliverables</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.d6frklvhzyzc"><strong>Chapter 1 — Project Initiation, Planning, and Governance</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.ccmmpjdchr1x"><strong>Chapter 2 — Data Intelligence, Research, and Decision Support</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.qcfmtwivi6l8"><strong>Chapter 3 — UI/UX Design, Human-Centered Research, and Product Experience</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.94x7erxl79v7"><strong>Chapter 4 — Frontend Engineering and Interface Development</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.gv70qt8hh6q0"><strong>Chapter 5 — Backend Architecture, Database Design, and API Workflows</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.4x8vyl2zxmj9"><strong>Chapter 6 — Cybersecurity Assessment (VAPT), Findings, and Remediation Plan</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.x5u4gzxnbrb0"><strong>Chapter 7 — Interaction &amp; Communication Audit (WhatsApp Logs)</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.3c0lkng8i8kk"><strong>Quality Management, Risks, Lessons Learned, and Recommendations</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.r15uhm9i2adm"><strong>Conclusion</strong></a></li><li><a href="https://docs.google.com/document/d/1Yf7-qawn53teoqI6jZYhfWc9FhWrG37R9mDZ5CACkK0/edit?tab=t.0#heading=h.3ac8wd3whyv7"><strong>Appendices and Resource Repository</strong></a></li></ol><h3>Project Governance &amp; Team Roster</h3><p>TrashBeta was delivered by a cross-functional team operating under a three-Project-Manager governance model. Execution was coordinated through weekly Google Meet reviews and a major general meeting every Sunday at 9:00 PM (WAT), which served as the formal handover window for milestone submissions and cross-team integration.</p><h3>Project Management</h3><ul><li>Daniel Bayo Olaleye- Project Manager</li><li>Christopher Udoka — Project Manager</li><li>Chinemelu Ikenna — Project Manager</li></ul><h3>Functional Team Leads</h3><ul><li>Data Analytics Lead — Adeniyi Oluwademilade</li><li>UI/UX Lead Product Designer — Abdulraheem Ramota</li><li>Frontend Engineer — Udo Anienamakan</li><li>Backend Engineer — Asiru Adedolapo</li><li>Cybersecurity Lead — Udenkwo Chinedum</li></ul><h3>Full Member List</h3><ol><li>Daniel Bayo Olaleye</li></ol><p>Project Manager</p><ol><li>Project Manager</li></ol><p>2. Christopher Udoka<br>Project Manager</p><p>3. Ikenna Chinemelu<br>Project Manager</p><p>4. Oluwademilade Adeniyi<br>Data Analyst</p><p>5. Abdulmalik Muhammed<br>Data Analyst</p><p>6. Mary Akinola<br>Data Analyst</p><p>7. David John<br>Data Analyst</p><p>8. Blessing Akpoveta<br>Data Analyst</p><p>9. Adewale Ojeniyi<br>Data Analyst</p><p>10. Angela Omughele-Michael<br>Data Analyst</p><p>11. Brightness Adasigwung<br>Data Analyst</p><p>12. Chinecherem Nwani<br>Data Analyst</p><p>13. Deborah Adebiyi<br>Data Analyst</p><p>14. Eniola Adelakun<br>Data Analyst</p><p>15. Ifeanyi Ozoh<br>Data Analyst</p><p>16. Joy Ikpeme<br>Data Analyst</p><p>17. Loveth Akowe<br>Data Analyst</p><p>18. Loveth John<br>Data Analyst</p><p>19. Mariam Matti<br>Data Analyst</p><p>20. Modupe Ayodele<br>Data Analyst</p><p>21. Odinakachi Nnuforole<br>Data Analyst</p><p>22. Olayinka Oladeji<br>Data Analyst</p><p>23. Omolade Sorunke<br>Data Analyst</p><p>24. Vivian Abbah<br>Data Analyst</p><p>25. Williams Obinna<br>Data Analyst</p><p>26. Ramota Abdulraheem<br>Product Designer</p><p>27. Adenike Ojedokun<br>Product Designer</p><p>28. Jennifer Ogwuche<br>Product Designer</p><p>29. Waris Taiwo<br>Product Designer</p><p>30 .Anienamakan Udo<br>Front End Engineer</p><p>31. Adedolapo Asiru<br>Back End Engineer</p><p>32. Ayomide Balogun<br>Cybersecurity Specialist</p><p>33. Chinedum Udenkwo<br>Cybersecurity Specialist</p><p>34. Morayo Adejumo<br>Cybersecurity Specialist</p><p>35. Raymond Okafor<br>Cybersecurity Specialist</p><h3>Executive Summary</h3><p>TrashBeta is a civic-tech, community-first waste reporting and coordination platform designed to close Nigeria’s waste “Silence Gap” — the recurring situation where citizens report environmental hazards yet receive no acknowledgement, no tracking, and no proof of action. Delivered as a Vephla University capstone product from December 1, 2025, to February 28, 2026, TrashBeta combines a resident-facing reporting experience, role-based dashboards for staff/agents and administrators, a secure backend API and database for workflow management, a data analytics layer that turns citizen reports into operational intelligence, and a cybersecurity assessment (VAPT) with prioritized remediation guidance.</p><h3>Validated outcomes from the research and build phases include:</h3><ul><li>301 waste-issue reports collected during a 13-day beta window; coverage expanded to 25 Nigerian states (target: 10).</li><li>82.1% of respondents expressed interest in using a dedicated reporting platform, confirming demand for a structured digital channel.</li><li>Lagos State accounted for 72.1% of reports; within Lagos, Alimosho (72 reports) emerged as the highest hotspot.</li><li>59.8% of reports were rated high/critical urgency (levels 4–5), evidencing real public health and safety risks.</li><li>Cybersecurity testing identified critical vulnerabilities (including privilege escalation and injection risks) with an immediate remediation backlog defined.</li></ul><h3>The TrashBeta Story</h3><p>TrashBeta began with a normalized reality across many Nigerian communities: waste piles growing for weeks, bins overflowing for days, drainage channels blocked until flooding forces attention, and residents repeating the same cycle — complain, wait, and move on. The breakdown is not that people do not report; it is that reporting is fragmented, untracked, and rarely generates feedback.</p><p>Existing channels — physical visits to local government offices, phone calls to Private Sector Participants (PSPs), social media tagging, or community leader escalation — create a fractured information layer. Authorities lack a single source of truth. Citizens lack visibility on progress. Service providers lack objective performance benchmarking. This is the Silence Gap: the gap between citizen voice and institutional action.</p><p>TrashBeta was designed as the missing feedback loop: a unified platform that captures reports with location context, assigns tracking IDs, supports role-based workflows for execution and oversight, and produces dashboards that answer operational questions — where is the problem, how severe is it, how long has it persisted, and what should be done next.</p><h3>Integrated Project Timeline and Deliverables</h3><p>Execution aligned with Vephla University’s phased capstone timeline. Each phase produced a concrete artifact, and on appointed Sundays, 9:00 PM handover transitioned focus from one workstream to the next.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*qnq_oNjBo3SCk00d.png" /></figure><h3>Chapter 1 — Project Initiation, Planning, and Governance</h3><p>The project was initiated to deliver a cross-functional digital solution that improves community waste reporting and operational accountability. Given the technical scope, delivery required coordinated execution across Data Analytics, UI/UX Product Design, Frontend and Backend Engineering, and Cybersecurity.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*99eoHfZ7k6WgL6VN.png" /></figure><h3>1.1 Governance Model</h3><p>TrashBeta operated under a three-Project-Manager model to distribute oversight responsibilities while maintaining centralized control. Team leads reported through a structured cascade (Members → Team Leads → Project Managers), enabling controlled escalation and dependency management.</p><h3>1.2 Scope Definition</h3><h3>In-scope deliverables included:</h3><ul><li>Web-based waste reporting platform with user registration and authentication.</li><li>Complaint submission workflow with location and media support (production design; beta constrained by tooling).</li><li>Role-based dashboards for residents, staff/agents, and administrators.</li><li>Task assignment, status tracking, and resolution monitoring workflows.</li><li>Analytics dashboards for hotspot detection, urgency and impact profiling, and engagement metrics.</li><li>Security and authentication validation through VAPT testing.</li></ul><h3>Out-of-scope deliverables (to protect timeline and quality) included:</h3><ul><li>Native mobile applications (Android/iOS).</li><li>Deep integrations with municipal legacy systems.</li><li>Advanced AI automation and hardware-based monitoring.</li></ul><h3>1.3 Working Cadence and Handover Discipline</h3><p>The team adopted a repeatable weekly rhythm. Major general meetings were held every Sunday at 9:00 PM (WAT) for cross-functional review, milestone sign-off, and formal handovers. Between handovers, teams coordinated continuously through WhatsApp for quick issue resolution, task confirmations, and sprint-level updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/0*bJXmFl0w9Jx--7qR.png" /></figure><h3>Chapter 2 — Data Intelligence, Research, and Decision Support</h3><p>The Data Analytics workstream validated demand, mapped hotspot concentration, quantified systemic failure patterns, and produced stakeholder-ready dashboards that convert citizen voice into actionable operational intelligence.</p><h3>2.1 Data Sources and Collection Window</h3><p>Primary data was collected through a structured Google Forms survey distributed via WhatsApp networks, Twitter/X, and university communities between December 19, 2025, and December 31, 2025 (13 days). Secondary data was mined from social platforms and news sources to triangulate the signal, resulting in verified hotspot logs and qualitative sentiment markers.</p><h3>2.2 Data Preparation and Modeling</h3><p>To enable robust querying and BI modeling, the raw export was standardized using Python (pandas) to rename columns into machine-readable formats. Geographic quality control was performed by cross-referencing LGA entries against a master list of 774 Nigerian LGAs, correcting misspellings and reducing ambiguity. A normalized, analytics-ready schema was produced (location dimensions + bridge tables for multi-select impacts and communication preferences), enabling accurate aggregation without row inflation.</p><h3>2.3 Headline Findings</h3><ul><li>Geographic concentration: Lagos State contributed 72.1% of all reports; within Lagos, the ‘Big Five’ LGAs dominated volume.</li><li>Alimosho hotspot: 72 reports; high chronicity with many issues persisting 6+ months, indicating structural capacity mismatch.</li><li>Festive failure: report spikes between Dec 24–28 highlighted predictable holiday-period operational collapse among PSPs.</li><li>Severity: 59.8% of reports rated urgency 4–5, reframing waste as a public health and safety emergency rather than an aesthetic complaint.</li><li>Trust deficit: 82.1% expressed interest in the platform, yet only 16.6% provided contact details and ~42.5% were willing to share photos — a clear barrier to verification that informed product design.</li></ul><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*1Heg86RTPA2MYboJ.png" /></figure><h3>2.4 Decision Support Outputs</h3><p>The team produced two multi-page Power BI reports for: (1) Problem scope &amp; overview; (2) Engagement and adoption readiness; (3) Operational intelligence (Critical Strike List) for dispatch prioritization. Measures were implemented using DAX, and the model was designed to support real-time expansion when integrated into the production platform.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*FfXMeclvWEPgIj73.png" /></figure><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*I31y5RO_ewUD_58R.png" /></figure><h3>Chapter 3 — UI/UX Design, Human-Centered Research, and Product Experience</h3><p>The UI/UX team applied a Human-Centered Design approach to ensure TrashBeta remains fast to use, psychologically safe for citizens, and operationally practical for staff/agents and administrators.</p><h3>3.1 Research Synthesis and Design Implications</h3><p>Quantitative insights from the 301-response survey and qualitative interviews confirmed the ‘Silence Gap’ and highlighted an ‘Anonymity Priority’ among users. The design response was a graduated trust model: reporting should be possible with minimal friction, while verification and follow-up information remain optional and incentive-aligned.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*5LrFWG9n5CMLVNiD.png" /></figure><h3>3.2 Core Personas and Role-Based UX</h3><ul><li>Resident (Tola, 28): report in under 60 seconds and receive WhatsApp/SMS updates.</li><li>Agent/Worker (Musa, 35): mobile-first task list, landmark context, and after-photos for proof of completion.</li><li>Admin (Director Kola, 50): dashboards for hotspot monitoring, PSP performance metrics, and assignment workflows.</li></ul><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*B6STLjbV2NvwfiLH.png" /></figure><h3>3.3 Information Architecture and Design System</h3><p>The sitemap was structured into three primary silos (Reporting, Execution, Oversight) with the Report action kept within one click from primary screens. A reusable design system was documented to support cross-team consistency and future scaling (components, badges, typography, and accessibility rules).</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*sGq71xnpBY2I_oyo.png" /></figure><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*NTX8h93OT3OoweFJ.png" /></figure><h3>Chapter 4 — Frontend Engineering and Interface Development</h3><p>Front-end implementation translated approved designs into a responsive, role-based web interface using HTML, CSS, and Vanilla JavaScript. The build prioritized compatibility, performance, and predictable navigation across desktop, tablet, and mobile devices.</p><h3>4.1 Implementation Highlights</h3><ul><li>Authentication and onboarding flows for role selection and access control.</li><li>Role-based dashboards (Admin, Worker, Resident) with consistent layout patterns.</li><li>Reporting interface for residents with structured inputs and user guidance.</li><li>Task management interfaces for workers with status updates and progress tracking.</li><li>Mobile responsiveness through media queries and a hamburger navigation menu.</li></ul><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*fE0NZoIrE-Q0JJFr.png" /></figure><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*H-rbq8wtZGMYnW3a.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*3vMFlI7rId1QSXTy.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/0*AoRUMe5yyZoXfDLL.png" /></figure><h3>4.2 Testing and Debugging</h3><p>Interfaces were tested across browsers and screen sizes to validate layout stability and navigation integrity. Common issues (broken paths, layout breaks on small screens, navigation state inconsistency) were resolved through iterative debugging and structure refactoring.</p><h3>Chapter 5 — Backend Architecture, Database Design, and API Workflows</h3><p>Backend services were implemented in Node.js and Express.js with MongoDB persistence, JWT-based authentication, bcrypt password hashing, and Cloudinary media storage. The architecture followed a modular layered structure (routing → middleware → controllers → services → database), supporting scalability and maintainability.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*aXaVaGBhZczGH5Oo.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*C46xrSLrjK7Db-J0.png" /></figure><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*BPM0wgRxx3SMzMV_.png" /></figure><h3>5.1 Core Backend Capabilities</h3><ul><li>User registration, login, OTP verification, and secure password reset flows.</li><li>Role-Based Access Control (resident, staff, admin) is enforced through middleware and resource ownership checks.</li><li>Report lifecycle management: create report → generate tracking ID → assign staff → update status → resolve.</li><li>Secure media upload pipeline with file type/size validation and externalized storage (Cloudinary).</li><li>Environment-based configuration and deployment readiness (Render).</li></ul><h3>5.2 Data Model Summary</h3><p>User and Report schemas were designed with validation and indexing strategies to support high-frequency lookup and auditing (unique email, sparse phone, indexed tracking IDs). The model supports one-to-many relationships between residents and reports and between staff and assigned reports, while administrators have global oversight.</p><h3>Chapter 6 — Cybersecurity Assessment (VAPT), Findings, and Remediation Plan</h3><p>A structured black-box Vulnerability Assessment and Penetration Testing (VAPT) was conducted on the public web application and API endpoints, aligned with OWASP guidance and NIST testing principles. Tools included Nmap, Burp Suite, Wireshark, Swagger UI, and VirusTotal.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /></figure><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*i-VjsCf9Q_CU6Rnv.png" /></figure><h3>6.1 Key Findings (Prioritized)</h3><ul><li>Privilege escalation risk: resident token could be abused to obtain administrator privileges (critical).</li><li>Injection exposure: endpoints susceptible to XSS and SQL injection patterns (high).</li><li>Information disclosure: verbose error messages and role detail exposure (medium).</li><li>Missing or inconsistent security headers; incomplete hardening posture (medium).</li><li>Operational UX risk: missing logout option increases risk on shared devices (medium).</li></ul><h3>6.2 Remediation Backlog (Immediate)</h3><ul><li>Enforce RBAC server-side on all sensitive endpoints; restrict role changes to admins only.</li><li>Implement strict server-side input validation, sanitization, and encoding; avoid reflecting untrusted input.</li><li>Standardize error handling to prevent information leakage; return generic authentication errors.</li><li>Apply security headers consistently (HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy) via Helmet.</li><li>Introduce explicit logout and token invalidation strategy (and a JWT blacklist if required at scale).</li></ul><h3>Chapter 7 — Interaction &amp; Communication Audit (WhatsApp Logs)</h3><p>To complement technical deliverables with a workplace-style engagement audit, the team analyzed WhatsApp communication logs from December 7, 2025 to February 25, 2026. Logs were extracted, cleaned, modeled, and visualized using Python (Jupyter), Excel, Power Query, and Power BI.</p><h3>7.1 Communication KPIs</h3><ul><li>Total messages processed: 2,722 across four groups.</li><li>General Group acted as a ‘Town Hall’ for announcements and cross-functional updates.</li><li>The Cybersecurity Team showed the highest intensity near deadlines (sprint behavior).</li><li>The Data Team showed steady long-term collaboration and technical coordination.</li><li>Weekend-heavy rhythm aligned with Sunday 9:00 PM general meetings and handovers.</li></ul><h3>7.2 Recommendations for Future Cohorts</h3><ul><li>Centralize links and documentation in a single resource hub (Notion/Drive) to reduce repetitive ‘where is the link’ requests.</li><li>Introduce short mid-week standups to reduce weekend load and compress feedback cycles.</li><li>Define minimum reporting expectations for solo roles (e.g., weekly status dailies) to improve transparency for non-technical stakeholders.</li></ul><h3>Quality Management, Risks, Lessons Learned, and Recommendations</h3><p>Quality was managed through phased submissions, PM-led scope control, and cross-team integration checks. Key risks included integration friction across modules, schedule pressure due to parallel workstreams, and security gaps uncovered during VAPT.</p><h3>Key Lessons Learned</h3><ul><li>Structured communication prevents drift: weekly reviews and recap notes improved accountability.</li><li>Clear WBS ownership reduces duplication and speeds up decision-making.</li><li>Early integration testing reduces late-stage debugging and rework.</li><li>Trust is a product requirement: privacy, anonymity options, and transparent status updates are not ‘nice-to-have’ features in civic tech.</li><li>Security is continuous: VAPT findings should drive a hardening sprint before any broader pilot.</li></ul><h3>Next Phase Roadmap (Suggested)</h3><ul><li>90-day pilot in Lagos ‘Big Five’ LGAs with photo + GPS capture, WhatsApp/SMS notifications, and dispatch workflows.</li><li>Partnership and MoU framework with relevant authorities/PSPs to enable response-time measurement.</li><li>Security hardening sprint to close critical findings and implement monitoring/logging baselines.</li><li>Expansion plan to additional LGAs/states based on engagement and operational readiness signals.</li></ul><h3>Conclusion</h3><p>TrashBeta demonstrates that Nigeria’s waste management crisis is not only a logistics challenge but also a data, coordination, and accountability challenge. By unifying citizen reporting, structured workflows, analytics dashboards, and security validation into one platform, TrashBeta converts community voice into dispatch intelligence and performance evidence. With targeted remediation of cybersecurity findings and a disciplined pilot in high-burden LGAs, the platform can evolve from a capstone prototype into stakeholder-ready civic infrastructure.</p><h3>Appendices and Resource Repository</h3><h3>Appendix A — Project Management Deliverables</h3><p><a href="https://drive.google.com/drive/folders/10cqJaQ256j0y2Mu-_rc8dsoASnlW9mN-?usp=drive_link">Folder Link</a></p><ul><li>Project Charter</li><li>Work Breakdown Structure (WBS) and assignments</li><li>Risk register and mitigation notes</li><li>Meeting evidence</li><li>Final PM report</li></ul><h3>Appendix B — Data Analytics Deliverables</h3><p><a href="https://drive.google.com/drive/folders/1gTgpkyXvMWK7fgZJ1mlUoknz-OhsTvkw?usp=sharing">Folder Link</a></p><ul><li>Primary dataset (CSV) and data dictionary</li><li>Secondary hotspot log and evidence pack</li><li>SQL queries, Python cleaning scripts, notebooks</li><li>Power BI dashboards (PBIX) + exported PDFs</li><li>Final Data Analytics technical report</li></ul><h3>Appendix C — UI/UX Deliverables</h3><p><a href="https://drive.google.com/drive/folders/11dX4LXiYA5NPmC2NXaWyi2ZP0T0ATNai?usp=drive_link">Folder Link</a></p><ul><li>Research synthesis (FigJam)</li><li>Survey/interview assets and transcripts</li><li>Personas, empathy maps, IA/sitemap, user flows</li><li>Wireframes (low to high fidelity)</li><li>Design system / style guide</li><li>Figma file and interactive prototype</li></ul><h3>Appendix D — Frontend Engineering Deliverables</h3><p><a href="https://drive.google.com/drive/folders/1xSrIO4gHwzHPoBvhKXLoNvNp1qYT9Hcr?usp=drive_link">Folder Link</a></p><ul><li>Source code repository link</li><li>Build/deployment notes</li><li>UI screenshots and testing evidence</li><li>Frontend technical report</li></ul><h3>Appendix E — Backend Engineering Deliverables</h3><p><a href="https://docs.google.com/document/d/1mB4-_aCqBCWaHqdtFeiGWK1Hgh1IYO4XUn7LXBTMmME/edit?usp=drive_link">Folder Link</a></p><ul><li>API documentation (Swagger/Postman)</li><li>Database schema and model documentation</li><li>Deployment notes (Render)</li><li>Backend technical report</li></ul><h3>Appendix F — Cybersecurity Deliverables</h3><p><a href="https://docs.google.com/document/d/1q1uiCIIKOGU9zgcmmwcRHOrKUjvx7Ww82ABqYW8Ij94/edit?usp=drive_link">Folder Link</a></p><ul><li>VAPT report</li><li>Tool outputs (Nmap, Burp Suite, Wireshark, VirusTotal)</li><li>Evidence screenshots</li><li>Remediation plan backlog</li><li>Scan proof videos</li></ul><h3>Appendix G — Interaction &amp; Communication Analysis Deliverables</h3><p><a href="https://drive.google.com/drive/folders/12cUf4zJH_EcB3Kt4xKKT8Rp_VHyKVVg9?usp=sharing">Folder Link</a></p><ul><li>WhatsApp export logs</li><li>ETL scripts and notebooks</li><li>Cleaned Excel dataset and Power BI report</li><li>Insights memo / final communication analysis report</li></ul><h3>Appendix H — Team Meeting Reports</h3><p><a href="https://docs.google.com/document/d/19H6SiNA7YFHzh6qCUM424VmfS9--3cN-WS4ZhwJ2p1Q/edit?usp=sharing">Folder Link</a></p><ul><li>Major general meeting attendance and agenda</li><li>Weekly handover notes and submission confirmations</li><li>Action items tracker</li></ul><p><a href="https://medium.com/tag/technical-report-writing?source=post_page-----4963bb8b9209---------------------------------------">Technical Report Writing</a></p><p><a href="https://medium.com/tag/project-management?source=post_page-----4963bb8b9209---------------------------------------">Project Management</a></p><p><a href="https://medium.com/tag/cross-functional-teams?source=post_page-----4963bb8b9209---------------------------------------">Cross Functional Teams</a></p><p><a href="https://medium.com/tag/web-app-development?source=post_page-----4963bb8b9209---------------------------------------">Web App Development</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2e4ced46f31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TEAM 3 CAPSTONE PROJECT
 TECHNICAL REPORT]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/team-3-capstone-project-technical-report-6c35e76d99e7?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c35e76d99e7</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Wed, 24 Sep 2025 08:47:34 GMT</pubDate>
            <atom:updated>2025-11-08T18:17:49.372Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>TEAM 3 CAPSTONE PROJECT<br> TECHNICAL REPORT</strong></h3><h4><strong>Verification of Fake Drugs, Products, and Drinks(MedCheck)</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dXhGXS60u7ee8iAk3eFSng.jpeg" /><figcaption>Product Check</figcaption></figure><ul><li><strong>Project Managers:</strong> Daniel Bayo Olaleye, Ogunjemilua Ojo.</li><li><strong>Start Date:</strong> JULY 23, 2025</li><li><strong>Completion Date:</strong> SEPTEMBER 24, 2025</li><li><strong>Project Type:</strong> WEBSITE DEVELOPMENT, (Verification Platform)</li><li><strong>Project Sponsors/Stakeholders:</strong> CAPSTONES and VEPHLA UNIVERSITY</li></ul><p>Being the text of the technical document for Team 3’s capstone project, submitted to Verification of Fake Drugs, Product and Drinks (Medcheck), Vephla in partial fulfilment of the certification of a Diploma in Project Management, a Diploma in Data Analysis, a Diploma in Product Design, a Diploma in Frontend Engineering, a Diploma in Backend Engineering, and a Diploma in Cybersecurity.</p><p><strong>Wednesday, September 24, 2025</strong></p><h4>My Role as Project Manager</h4><p>The simulation meeting with stakeholders took place on July 11, 2025, at 9:25 PM (WAT). During the session, extensive information and guidance were provided on how to develop project topic ideas that would best suit Team 3’s Capstone Project. Several teams were in attendance, including Data Analytics, UI/UX, Front-End, Back-End, and Cybersecurity.</p><p>The stakeholders gave a deliverables and timelines of each team on the simulation document. I was was given timeline on when to submit my project charter and the my Work break down structure, that was the first milestone to be achieved on my table as the project manager. I had my kickoff and brainstorming meeting on the 13th July 2025. This is the meeting introduction of team members took place and brainstorming on how to get a topic we can work on as a project, we concluded to go a topic that we can get data set on and a topic that can be relevant even after the project phase.</p><p>We Submitted three topics and among the three topic submitted one was approved which was Verification of fake Drugs, Products and drinks(Med check)</p><p>afterwards I prepared a project charter which comprise of the project phases, goals, objectives, timelines for each team, Milestones and the full information of my team members, while my co. PM prepared the work break down structure. The timeline given for the project charter and work break down structure was July 23-July 25 respectively. I submitted my deliverables on the due date and that was the first milestone.</p><p>We kept on having status update meetings, stand up meetings for proper execution, monitoring and evaluation of the project.</p><p>Hybrid methodology</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AkyfHLMS8Ql9pFfnY_5BZg.png" /><figcaption>Hybrid methodology</figcaption></figure><p>The hybrid methodology combines the strengths of different project management approaches, such as Agile and Waterfall, to create a tailored solution. This approach allows for flexibility, adaptability, and structure, making it ideal for complex projects with changing requirements. By integrating different methodologies, teams can leverage the benefits of each approach, enhance collaboration, and improve project outcomes. using this methodology i was able to mitigate potential risks during the project phase, and was able to meet up with timelines and milestones given by the stakeholders. Although the tasks were depending on themselves to make progress which was the water fall approach that is required then due to time constrain I introduced flexibility and iterativeness which is agile approach by collaboration i.e. the team leads of each team were instructed to communicate deeply and this is to help all the team to be actively working out their deliverable needed before the total output of the previous team get to them. this was the chain progression, Data team,-ui/ux team,-frontend engineer team.-backend engineer team,-cyber security team.</p><p>TOOL USED</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nf0ea_dlApa1yT3d" /><figcaption>Photo by <a href="https://unsplash.com/@hnhmarketing?utm_source=medium&amp;utm_medium=referral">Hunter Haley</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ol><li>Google Meet: This was used basically for our meetings and through this platform we were able to record all our meetings from the initial phase of the project to the closing phase.</li><li>Google mail: was also use in sending milestones to the stakeholders in order to avoid any form of external scope creep which may lead to rejection of deliverables.</li><li>Slack interface: This platform was used as a communication tool for the team, where meetings are been scheduled and personal messages to team members was sent as occasion arises.</li><li>WhatsApp Group: This platform helped in communication, sending information and making urgent announcements concerning meetings.</li></ol><h4>Challenges Faced</h4><p>internal Scope creep:</p><p>We had an internal scope creep from the front end team, who happens to be the leader of the team.. he absconded at the middle of the project. But I was able to mitigate the risk by rescheduling the task amongst other team members after informing the stakeholder about the scope creep.</p><p>Insight Gained</p><p>During the project phase i was able to mitigate an internal scope creep that came up at the middle of the project by the front end team lead who absconded at the middle of the project. I reached out to the stakeholders and restructure the team and followed up the task keenly in order for us to meet up with the deadline, and with such measure that i put into play we were able to meet up with all our deliverables.</p><p>Another insight gained is the ability manage large number of persons, i appointed team leads in each of the team which is the data analytics team, ui/ux team, front end team, backend team, and cyber security team. so i was able to manage these teams by relating directly with their leads and they give progress report in all our status update meetings.</p><h4>Project Phases</h4><p><strong>Initiation &amp; Planning Phase</strong></p><p>Conducted a <strong>kick-off meeting</strong> to align all team members on goals and responsibilities</p><p>Created the <strong>Project Charter</strong> and <strong>Work Breakdown Structure (WBS)</strong>, outlining deliverables, constraints, and assumptions.</p><p>Developed a timeline and stakeholder engagement plan.</p><p><strong>Project Execution</strong></p><p><strong>Data Analysis Phase</strong></p><p>Data collection and cleaning</p><p>Data Analysis, Visualization and Pattern recognition</p><p>Show KPIs (project deliverables)</p><p>Insight Generation</p><p><strong>Design Phase</strong></p><p>Conduct interviews and user research</p><p>User-Centered Design</p><p>Wire framing and Prototyping</p><p>User Flow Design</p><p>Feedback Mechanisms</p><p>Usability Testing</p><p><strong>Development Phase</strong></p><p><strong>Frontend Engineers</strong></p><p>Building User Interface</p><p>Implementing UI/UX Design</p><p>Client-Side Validation</p><p>Integrating APIs</p><p>Testing and Debugging</p><p>Backend Engineer</p><p>Server-Side Development</p><p>API Development</p><p>Database Management</p><p>Data Processing</p><p>Ensuring data integrity</p><p><strong>Testing &amp; Security (Cybersecurity Phase)</strong></p><p>Threat Assessment</p><p>Security Design</p><p>Data Encryption</p><p>Vulnerability Management</p><p>Incident Response</p><p>Security Awareness</p><h4>Closing Phase</h4><p><strong>Deployment &amp; Launch</strong></p><p>Feedback systems and communication dashboards were integrated to ensure continuous improvement.</p><p><strong>Key Stakeholders and Primary Audience</strong></p><p>For this project, the key stakeholders in order of priority are:</p><p>Vephla University: This is the body that awards the diploma certifications for a Diploma in Project Management, a Diploma in Data Analysis, a Diploma in Product Design, a Diploma in Front-End Engineering a Diploma in Backend Engineering, and a Diploma in Cyber security. They are also the owners of the project and to whom the project will be submitted.</p><p>Project Sponsors/Reviewers: These are the representatives of Vephla University who oversee the project team and give approval or certify that a project is fully delivered, i.e. the project has met the project goal, scope and deliverables.</p><p><strong>ABSTRACT</strong></p><p>MedCheck is a system designed to verify the authenticity of drugs, products, and drinks. It aims to combat counterfeiting by providing a reliable way for consumers to check if a product is genuine or fake. Using unique identifiers like QR codes or serial numbers, MedCheck verifies products against a database of authentic items. However, it is notable in Nigeria that Counterfeit drugs, products, and drinks pose a significant threat to public health, causing harm to individuals and undermining trust in the pharmaceutical industry. Current methods for detecting counterfeit products are often inadequate, and consumers lack a reliable way to verify product authenticity, However, With MedCheck, proactive solution to the growing problem of counterfeit goods would be solved and this will help protect public health, supports legitimate businesses, and builds trust in the products people use. By leveraging technology, MedCheck offers a proactive solution to the growing problem of counterfeit goods.</p><p><strong>Introduction</strong><br> Counterfeit products, ranging from life-saving pharmaceuticals to consumables like beverages and packaged goods, pose a grave and escalating threat to public health, consumer safety, and economic integrity worldwide. The World Health Organization (WHO) estimates that 1 in every 10 medical products in low- and middle-income countries (LMICs) is substandard or falsified, with the African region bearing the heaviest burden (WHO, 2017). In Nigeria alone, over 280,000 deaths annually have been attributed to the circulation of counterfeit pharmaceuticals, particularly anti-infectives and anti-malarials (NIPRD, 2021).</p><p>Beyond drugs, counterfeit food and beverage products have also infiltrated markets at alarming levels. The United Nations Interregional Crime and Justice Research Institute (UNICRI) reports that counterfeiting food and drink has become a growing segment of transnational organized crime, often involving adulterated or toxic ingredients, mislabeling, and fake expiration dates (UNICRI, 2021). In 2023, the National Agency for Food and Drug Administration and Control (NAFDAC) confiscated over ₦600 million worth of fake alcoholic beverages and soft drinks across multiple Nigerian states, signaling a crisis that extends well beyond pharmaceuticals (NAFDAC, 2023). These counterfeit consumables not only endanger lives but also compromise consumer trust, distort market competition, and result in substantial revenue losses for legitimate producers.</p><p>The Nigerian government reportedly loses over ₦200 billion (approx. $260 million) annually to counterfeit goods, including revenue leakage, healthcare costs, and reputational damage to local industries (Umeh, 2023). These challenges threaten to derail the nation’s progress toward Sustainable Development Goals (SDGs), particularly SDG 3 (Good Health and Well-being) and SDG 9 (Industry, Innovation, and Infrastructure).</p><p>In response, MedCheck is a web app verification platform developed to authenticate a wide range of products, including pharmaceutical drugs, beverages, and consumer goods. It assigns unique identifiers (QR codes, barcodes, or SMS-linked codes) to products, allowing users to verify authenticity instantly via a web application. A secure and centralized database houses information on manufacturers, batch numbers, expiration dates, and authorized distribution channels. MedCheck’s design incorporates blockchain technology to ensure data integrity, artificial intelligence (AI) for pattern recognition and anomaly detection, and Internet of Things (IoT) sensors to monitor real-time product movement within the supply chain.</p><p>MedCheck is a multi-stakeholder innovation, targeting consumers, manufacturers, distributors, and regulatory bodies. By providing end-to-end product transparency, it seeks to reduce counterfeiting, improve public health outcomes, ensure food and product safety, and restore consumer confidence in Nigeria’s increasingly vulnerable marketplace. Its deployment will help close regulatory gaps and create a digitally accountable ecosystem that supports both national policy frameworks and international commitments to health, safety, and commerce.</p><p><strong>Problem Statement</strong></p><p>Counterfeit products remain a persistent and dangerous problem in Nigeria and many other low- and middle-income countries. Pharmaceuticals, drinks, and everyday consumer items are routinely faked, mislabeled, or adulterated, resulting in life-threatening consequences for consumers and significant economic losses for legitimate manufacturers. Regulatory bodies struggle to enforce quality assurance due to fragmented supply chains, poor visibility, and a lack of real-time verification tools.</p><p>Preliminary studies and product sampling across multiple Nigerian states reveal that up to 98.6% of examined products including both drugs and consumables — are counterfeit, with some regions showing 100% fake product rates. These alarming figures highlight a systemic failure in supply chain integrity, regulatory enforcement, and public product awareness. Despite numerous interventions, counterfeiters continue to exploit open markets, weak traceability systems, and consumer ignorance.</p><p>This growing crisis calls for a comprehensive, technology-driven response that empowers consumers, manufacturers, and regulators to detect and deter counterfeiting in real-time. Without a scalable and transparent verification framework, the risks to public health, national security, and economic development will continue to escalate.</p><p><strong>Main Objective</strong></p><p>To develop and deploy a secure, web app with technology-driven verification system that authenticates pharmaceutical drugs, beverages, and consumer products in real time using unique digital identifiers and a centralized database in order to protect public health, combat counterfeiting, and enhance supply chain transparency for consumers, manufacturers, and regulatory authorities.</p><p><strong>Goals</strong></p><p>· Product Verification System: A robust system that enables consumers to verify the authenticity of pharmaceutical drugs, products, and drinks using unique codes or QR codes.</p><p>· User-Friendly Mobile App: A mobile app or website that allows consumers to easily verify product authenticity and receive alerts about counterfeit products.</p><p>· Centralized Database: A secure and centralized database that stores product information, manufacturing details, and distribution channels, providing transparency and accountability in the supply chain.</p><p>· Secure Authentication Mechanism: A mechanism that ensures the authenticity of products and prevents tampering or alteration of product information.</p><p>· Secure Authentication Mechanism: A mechanism that ensures the authenticity of products and prevents tampering or alteration of product information.</p><p><strong>Objectives</strong></p><p>· Empowered Consumers: MedCheck empowers consumers to make informed decisions about the products they purchase, promoting consumer safety and well-being.</p><p>· Protection of Public Health: MedCheck helps prevent the consumption of counterfeit or adulterated products, which can be harmful to health.</p><p>· Empowered Consumers: MedCheck empowers consumers to make informed decisions about the products they purchase, promoting consumer safety and well-being.</p><p>· Collaboration with Regulatory Bodies: MedCheck can facilitate collaboration between regulatory bodies, manufacturers, and consumers to combat counterfeiting.</p><p>· Reduced Counterfeiting: MedCheck’s verification system and alert mechanism can help reduce the prevalence of counterfeit products in the market.</p><p><strong>Scope of The Project</strong></p><p>The MedCheck project has a well-defined scope and out-of-scope, which helps to clarify its objectives and boundaries. Here’s a comprehensive explanation:</p><p>In Scope:</p><p>MedCheck focuses on verifying the authenticity of pharmaceutical drugs, products, and drinks through a robust system. The scope includes:</p><p>· Product Authentication: MedCheck verifies the genuineness of products, ensuring consumers receive authentic goods.</p><p>· Unique Coding: Products are assigned unique codes or QR codes for tracking and verification, making it harder for counterfeiters to produce fake products.</p><p>· Centralized Database: A database stores product information, manufacturing details, and distribution channels, providing a transparent and accountable supply chain.</p><p>· Consumer Verification: Consumers can verify product authenticity using a user-friendly mobile app or website, empowering them to make informed decisions.</p><p>· Alert System: MedCheck sends alerts to consumers and authorities about counterfeit products, ensuring prompt action is taken.</p><p>· Supply Chain Transparency: The system improves transparency and accountability in the supply chain, reducing the risk of counterfeit products entering the market.</p><p><strong>PRE-ANALYSIS PROCEDURES AND REPORT</strong></p><p><strong>DATA SET USED.</strong></p><p>For this project, one dataset was carefully selected to provide comprehensive insights that align with the objectives. Each dataset was instrumental in offering unique perspectives, contributing to a holistic understanding of the problem and potential solutions.</p><p><strong>WHY THESE DATA SETS</strong></p><p>To achieve the project’s objectives and address the problem statement, we prioritized datasets that could provide insights into key factors influencing authenticate pharmaceutical drugs, beverages, and consumer products.</p><p><strong>KEY INSIGHTS</strong>:</p><p>The Pre-analysis across eight Nigerian states, including Lagos, Abuja, Anambra, Kaduna, and Kano, revealed that 98.6% of sampled products including drugs and beverages were counterfeit, with several states such as Lagos and Kano recording a 100% fake product rate. This underscores a systemic regulatory breakdown and a widespread failure of traceability and authentication mechanisms across multiple product categories. The proliferation of fakes in both the formal and informal markets reflects deep vulnerabilities in the national supply chain system. Out of 500 products examined, 493 were confirmed fake, meaning 98.6% of the sample was counterfeit.</p><p>What it reveals:</p><p>· The prevalence of fake drugs is catastrophic, posing severe threats to public health.</p><p>· Counterfeiters have likely infiltrated supply chains, not just street-level distribution.</p><p><strong>IMPLICATIONS</strong>:<br> <strong>MedCheck</strong> enhances consumer safety and trust by enabling real-time verification of drugs, drinks, and consumer products. It improves supply chain transparency through unique product coding and a centralized database, helping detect and reduce counterfeit goods. While it doesn’t control manufacturing or regulatory enforcement, it supports faster response through alerts and reliable data, promoting collaboration among stakeholders for a safer, more accountable market.</p><p><strong>ANALYTICAL TOOLS</strong></p><p>Tools used in this data is Microsoft Power BI and Microsoft excel, dataset utilized in this analysis were in CVS Format</p><p><strong>DATA DICTIONARY</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*5_o4AZyoB2vRZ4tZ_4xtmg.jpeg" /></figure><p><strong>Methodologies.</strong></p><p>Microsoft Power BI was used for our analysis and the interactive visualizations which helps reveal critical patterns and gaps.</p><p><strong>Data Collection Process:</strong></p><p>Various sources was used to find the appropriate data set, the group of data analysts all contributed to the search of the datasets before it was narrowed down to 1 dataset that were relevant to the project.</p><p><strong>Data Cleaning Process:</strong></p><ol><li>It was checked for duplicate values to ensure there were no duplicates.</li><li>Data Type Changes: Adjusted the Value Naira data types of columns to appropriate formats (e.g., numeric, date, string) to align with their intended use.</li></ol><p><strong>PRE ANALYSIS DASHBAORD</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*unrunYAjSRSE4VYQdl8CWA.jpeg" /><figcaption><strong>PRE ANALYSIS DASHBAORD</strong></figcaption></figure><p>INTERACTIVE DASHBOARD</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*3H40MAAX_SD1Ywla9LOlzw.jpeg" /><figcaption><strong>INTERACTIVE DASHBOARD</strong></figcaption></figure><p><strong>Data Visualization</strong></p><p>For visualization in Power BI, we employed various chart types to effectively present the analysis. These visualizations were strategically selected to convey insights in an intuitive and visually appealing manner, making the data more accessible and actionable for stakeholders. We made use of Pie Chart, Donut Chart, Bar Chart, Clustered bar chart etc.</p><p><strong>Insights On Dataset</strong></p><ol><li><strong>Analysis of product type as contain in the dataset</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*SXOodvG8R_ds8KCFrRfX1w.jpeg" /></figure><p>The product type analysis reveals that counterfeit products in Nigeria cut across multiple sectors. Pharmaceuticals account for about 35% of fake goods, contributing to over 280,000 deaths annually. Food and beverages follow at 25%, with risks like methanol poisoning, while cosmetics and personal care items make up 15%, often containing harmful chemicals. Electronics and auto parts represent 10–12%, linked to fires and accidents, and children’s products add another 8%. These figures highlight a widespread consumer safety crisis, reinforcing the urgent need for cross-sector verification systems like MedCheck to restore trust and protect lives.</p><p>Tablets and capsules are the most common drug types in circulation, indicating they are the most widely consumed and, therefore, the most attractive targets for counterfeiters. Fake drugs are heavily concentrated in high-demand product types such as tablets, capsules, and syrups, suggesting counterfeiters prioritize products with high market turnover.</p><p><strong>2. Batch Number Verification</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/431/1*XdFm9BlWf3-mn3BZhqaRlQ.jpeg" /></figure><p>The Batch Number Verification Report shows that approximately <strong>65–70%</strong> of the products had no traceable batch number, indicating they were either completely fake or never passed through any official production system. Another 25–30% were confirmed as counterfeit, while only about 3–5% of the items were successfully verified as genuine. This highlights a critical traceability failure, where over 95% of products in circulation are either unverified or fake, underscoring the urgent need for strict batch tracking, enforcement, and consumer verification mechanisms.</p><p><strong>3. Fake Product Detection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*SGP3vATWiHIZIdX-WPq4eQ.jpeg" /></figure><p>The Fake Products Detection Report reveals a critical finding: 98.6% of the sampled products (493 out of 500) were confirmed to be counterfeit. This extremely high prevalence signals a public health crisis, exposing consumers to dangerous, ineffective medications and undermining trust in the healthcare system. With less than 2% of products verified as genuine, the data highlights the urgent need for verification systems, stricter enforcement, and supply chain transparency to protect lives and restore confidence.</p><p>The 98.6% fake rate shown in this chart is not merely a statistic, it represents thousands of lives put at risk daily, and it reinforces the critical role of digital verification tools, traceable supply chains, and inter-agency collaboration in reclaiming the integrity of Nigeria’s healthcare system.</p><p><strong>4. List of Manufacturer Companies</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*ytBY74QEBg_qqq1OqvfUTA.jpeg" /></figure><p>The manufacturer analysis shows that approximately 80–85% of the sampled products were linked to unverified, misspelled, or entirely fake manufacturer names, while another 10–12% had no manufacturer information at all. Only an estimated 3–5% of the products listed recognizable or traceable manufacturers. This high percentage of unverifiable origins highlights a deliberate strategy by counterfeiters to evade detection and accountability, reinforcing the urgent need for manufacturer registration enforcement, public verification databases, and digital labeling systems to protect consumers.</p><p>The chart confirms that lack of manufacturer transparency is a key tactic used in counterfeiting. When the origin is unverifiable, accountability becomes impossible. Consumers cannot rely solely on packaging labels to determine authenticity, especially when counterfeiters are mimicking or fabricating manufacturer information.</p><p><strong>5. List of Storage Type</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*20a6pNt23pWdyw8kXgS8xA.jpeg" /></figure><p>The storage type analysis shows that approximately 65–70% of sampled products were stored in open or informal settings such as roadside stalls, uncovered shelves, or kiosks conditions highly associated with counterfeit distribution. Another 15–20% were kept on floors or in exposed environments, increasing the risk of contamination and product degradation. Only about 10–15% of the items were found in covered or controlled retail displays. These figures suggest that over 80% of products are stored in unsafe, poorly regulated environments, reinforcing the link between counterfeit goods and substandard storage practices.</p><p>Unregulated storage environments serve as breeding grounds for counterfeit distribution, particularly in informal markets with minimal oversight. The lack of temperature control, exposure to weather, and poor hygiene associated with these storage types increases the risk of product degradation, even for originally genuine goods. Regulatory bodies should implement storage condition guidelines and inspection protocols, especially for pharmaceuticals, food items, and personal care products.</p><p><strong>6. Market Location Analysis</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*fnyZpnPItf2nEq7cAR69rg.png" /></figure><p>The Market Location Analysis shows that Port Harcourt accounted for the highest share of sampled products at approximately 35%, making it a major hotspot for counterfeit circulation, likely due to its port access and large informal markets. Kano and Lagos followed closely with 25% and 20% respectively, both known for their sprawling open markets where regulation is weak. Onitsha contributed about 12%, reflecting its role as a major wholesale hub in the Southeast, while Jos accounted for the remaining 8%, confirming that even smaller urban centers are affected. These figures underscore that counterfeit products are widespread across key trade cities, requiring targeted enforcement, border control, and location-specific verification strategies.</p><p>Port Harcourt, Kano, and Lagos should be considered high-priority enforcement zones, given their high product volume and risk profile. The presence of counterfeit goods in every city sampled reflects a national distribution crisis, not confined to any region or urban center. Entry points like Port Harcourt’s ports and Lagos’s major markets may serve as initial access routes for fake products, requiring stronger border and supply chain monitoring.</p><p><strong>7. Customers Review on Product.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/1*2tZphIOy2rLDQjAEVRwaoA.png" /></figure><p>The Report Notes chart reveals that 35% of the products had no manufacturer name, while 30% lacked a NAFDAC number, indicating regulatory non-compliance and likely counterfeiting. 20% showed label mismatches or printing errors, and 12% had no batch number, making traceability impossible. An additional 5–8% were expired, posing serious health risks. Alarmingly, only about 1–2% of the products were marked as verified or genuine, confirming that the vast majority of items examined failed basic authenticity and safety checks.</p><p>Absence of manufacturer names, NAFDAC numbers, and batch details confirms widespread non-compliance and intentional concealment within counterfeit operations. Label inconsistencies and expired goods increase health and safety risks, even for consumers trying to identify authenticity visually.</p><p><strong>CARDS USED FOR DATA INTERACTION</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*lEnr285WYoeFXK5I-rUHAA.png" /></figure><p><strong>Recommendations Based On Insights</strong></p><p><strong>i.</strong> <strong>Establish a National Product Verification System</strong></p><p>Develop and scale a centralized verification platform (like MedCheck) to cover all product sectors. Every approved item should have a unique, scannable identifier (QR code, serial number, or batch number) linked to a public database.</p><p>ii. <strong>Tightening Regulation and Monitoring of High-Risk Drug Categories</strong></p><p>Since tablets, capsules, and syrups had the highest number of fake products, regulatory agencies should increase surveillance, inspections, and quality control on these product types, especially at the manufacturing and distribution stages.</p><p>iii. <strong>Mandatory Batch Testing Before Market Release</strong></p><p>Pharmaceutical companies should be required to submit product batches for verification and certification before distribution. This can significantly reduce the volume of fake drugs entering the market.</p><p>iv. <strong>Public Awareness and Education Campaigns</strong></p><p>A comprehensive public sensitization strategy should be launched to educate consumers on the dangers of counterfeit drugs, how to identify suspicious products, and where to report them.</p><p>v. <strong>Create a National Database of Verified Drugs</strong></p><p>Establish a centralized, government-backed platform that lists approved and verified pharmaceutical products accessible to pharmacists, vendors, and consumers to help curb misinformation and wrong purchases.</p><p>vi. <strong>Stronger Border and Port Surveillance</strong></p><p>Increase border inspections and customs enforcement to block the importation of fake drugs, particularly in categories with high counterfeit rates.</p><p>vii. <strong>Strengthen Licensing and Accreditation of Drug Sellers</strong></p><p>Ensure that only registered and trained pharmaceutical vendors are allowed to sell medicines. Markets with unregulated sellers should be targeted for reform or closure.</p><p>viii. <strong>Enforce Product Traceability Laws</strong></p><p>Implement laws that require every drug package to be traceable, making it easier to track and identify the source of counterfeit drugs through the supply chain.</p><p>ix. <strong>Targeted Crackdown on Counterfeit Distribution Channels</strong></p><p>Based on the systemic spread of fake drugs across all categories, law enforcement agencies should be mobilized to disrupt known counterfeit networks, including arresting and prosecuting offenders.</p><p>x. <strong>Invest in Local Drug Manufacturing Capacity</strong></p><p>To reduce dependency on imported medicines (which are harder to monitor), governments should invest in local pharmaceutical manufacturing, ensuring better oversight and quality control.</p><p>xi. <strong>Periodic Market Surveillance and Sampling</strong></p><p>Regulatory bodies should routinely sample and test drugs from markets and pharmacies, especially for high-risk products, to monitor counterfeit trends and respond swiftly.</p><p>xii. <strong>Data-Driven Decision Making</strong></p><p>Establish a national counterfeiting intelligence unit that uses data from lab tests, complaints, and market trends to make informed enforcement decisions and policy recommendations.</p><p><strong>SUMMARY</strong></p><p>The Pre-Analysis dashboard reveals a national counterfeit crisis, with 98.6% of products (493 out of 500) confirmed as fake. Counterfeit goods span multiple sectors, including pharmaceuticals (35%), food and beverages (25%), cosmetics and personal care (15%), and electronics and auto parts (10–12%). About 95% of products had invalid or missing batch numbers, and 85% listed unverified or fake manufacturer names, while only 1–2% were verified as genuine. Additionally, over 80% of products were stored in unsafe, open environments, and cities like Port Harcourt (35%), Kano (25%), and Lagos (20%) emerged as high-risk counterfeit hubs. These figures highlight an urgent need for verification, regulation, and multi-stakeholder action to protect public health and restore consumer trust.</p><p><strong>JUSTIFICATION FOR THE HEALTH BRIDGE INITIATIVE:</strong></p><p>The MedCheck project is a necessary response to the alarming rate of counterfeit product circulation in Nigeria, where 98.6% of sampled goods including pharmaceuticals, beverages, cosmetics, and food, were found to be fake. With over 95% of products lacking valid batch numbers and 85% showing fake or unverifiable manufacturer names, consumer safety, public health, and supply chain integrity are under severe threat.</p><p>MedCheck directly supports SDG 3 (Good Health and Well-being) by protecting consumers from unsafe and ineffective drugs and products. Using digital tools like QR codes, blockchain, and AI, it aligns with SDG 9 (Industry, Innovation, and Infrastructure) by introducing modern infrastructure for product authentication and traceability. It empowers consumers to make informed choices, promoting SDG 12 (Responsible Consumption and Production), and enhances regulatory transparency in line with SDG 16 (Peace, Justice, and Strong Institutions).</p><p>By enabling real-time product verification, MedCheck strengthens institutional accountability, curbs illicit trade, and safeguards lives, making it not just relevant, but critical to national development and sustainable health systems.</p><p><strong>UI/UX DESIGN</strong></p><p>Link to Survey report and questions</p><p>Survey link: <a href="https://forms.gle/oTVGP5F4K6Tuyd8j8">https://forms.gle/oTVGP5F4K6Tuyd8j8</a></p><p>Survey report link: <a href="https://docs.google.com/spreadsheets/d/1Kv7m66gNR8lKoE05_Ifgs_dvmM0rMfZku2uXF8cIJXs/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1Kv7m66gNR8lKoE05_Ifgs_dvmM0rMfZku2uXF8cIJXs/edit?usp=sharing</a></p><p>MedCheck User Interview Questions</p><p>Link to invertview video: <a href="https://drive.google.com/drive/folders/1PIqoJhhT44BCQkVjUpuj5ncifK_jTlPa?usp=sharing">https://drive.google.com/drive/folders/1PIqoJhhT44BCQkVjUpuj5ncifK_jTlPa?usp=sharing</a></p><p>Name_________________</p><p>Gender:</p><p>Male</p><p>Female</p><p>Age range 18–24, 25–34, 35–44, 45–54, 55 or older</p><p>Location (country/region)</p><p>Occupation</p><p>1.Can you tell me a bit about your daily routine?</p><p>2.Have you ever worried that a product you or a loved one bought (like medicine, skincare, or food) might be fake, expired, or harmful?</p><p>Yes</p><p>No</p><p>Not sure</p><p>3. How do you currently check if a product is real or safe before buying or using it Possible options:</p><p>(I check the expiry date</p><p>I ask the seller</p><p>I look for a NAFDAC number</p><p>I scan a QR/barcode</p><p>I don’t check at all)</p><p>4. Have you ever used any method to verify a product’s authenticity (e.g., checking NAFDAC number or barcode)?</p><p>(Yes/No/I don’t know how to verify products)</p><p>5. If there was a website that could help you check if a product is real, what would be most important to you? (Choose your top 2 and why?)</p><p>(It’s quick and easy to use</p><p>It shows NAFDAC approval or warning</p><p>I can scan a barcode or enter a code</p><p>I can report fake products to help others</p><p>It gives safety tips and news)</p><p>6. What challenges might stop you from using a website like this?</p><p>7. How frequently do you think you would use MedCheck (weekly, monthly)?</p><p>8. Have you ever seen a warning about a dangerous or fake product (e.g., online, TV, NAFDAC)?</p><p>9. Would you feel confident using a website to check a product’s authenticity and will you trust a result from the said website? Why?</p><p>10. If you had one piece of advice for the team building MedCheck, what would it be?</p><p><strong>MedCheck Empathy Map</strong></p><p>Who is the user?</p><p>• Regular customers (purchasing medications, food, beverages, and cosmetics)</p><p>• Individuals with long-term conditions who require medicine</p><p>• Parents (purchasing goods for infants and children)</p><p>People who are concerned about their health; pharmacists and store owners</p><p>SAYS: The user’s actual words</p><p>• “I just want to confirm that this medication is authentic.”</p><p>• “I no longer have faith in the packaging.”</p><p>• “I worry cheap means fake, and prices are rising.”</p><p>• “How can I be sure that this cream is safe?”</p><p>• “How will I be notified promptly if NAFDAC recalls something?”</p><p><strong>THINKS (the user’s thoughts but not their words) • “Am I endangering my family or myself?”</strong></p><p>• “I don’t want to spend money on fake goods.”</p><p>• “Even reputable stores occasionally carry fakes.”</p><p>• “The government isn’t protecting us enough.”</p><p>• “I need an easy-to-use tool to verify authenticity.”</p><p><strong>SEES (What the user sees in their environment)</strong></p><p>• Shops stocked with goods from various brands</p><p>• Fake medications and consumables frequently have the same appearance as the real thing.</p><p>• News stories about phony or out-of-date goods</p><p>• Other people falling sick from fraudulent drugs</p><p>• Drugs that might or might not be reliable</p><p><strong>HEARS (What external factors affect the user)</strong></p><p>• A caution from friends and family: “Be careful, that drug might be fake.”</p><p>• NAFDAC/FDA health initiatives;</p><p>• Social media conversations over dangerous items;</p><p>• News headlines on medication recalls and seizures of counterfeit goods</p><p>• Physicians’ or pharmacists’ advice</p><p><strong>FEELS (pain spots and emotions)</strong></p><p>• Apprehensive: “What if I purchase the incorrect item?”</p><p>• Disappointed: “I am unable to determine which product is authentic.”</p><p>• Worried: “Safe medications are essential to my child’s survival.”</p><p>• Untrustworthy: “Confidentials can occasionally be found in even large retailers.”</p><p>• Hopeful: “I want a trustworthy method to be certain</p><p><strong>DOES (User actions/behaviors):</strong></p><p>• Purchases from markets, pharmacies, and internet retailers;</p><p>• Manually verifies package and expiration dates; Googles products or consults pharmacists for guidance; uses MedCheck (input NAFDAC number and scan barcode); reports fake goods when they are found; and provides family and friends with safety information.</p><p><strong>NEEDS OF THE USER</strong></p><p>• Instant notifications about recalls and counterfeit goods;</p><p>• A rapid and reliable verification tool (MedCheck app or website);</p><p>• A straightforward, user-friendly interface for scanning and verification;</p><p>• Comfort and assurance while making purchases; A mechanism for reporting vendors of fake goods</p><p><strong>User Personas</strong></p><p>User Persona 1: Debby– Human Resource Professional</p><p>Name: Ene Deborah Kalu</p><p>Age: 29</p><p>Gender: Female</p><p>Occupation: Human Resource Professional</p><p>Location: Abuja, Nigeria</p><p>Tech Proficiency: Moderate</p><p>Devices: Android smartphone</p><p>Goals:</p><p>Ensure her cosmetics and drugs are not counterfeit and safe</p><p>Stay informed on product recalls or banned items.</p><p>Report flagged/ fake or expired products.</p><p>Pain Points:</p><p>No good platform to check for flagged or expired products.</p><p>Limited trust in local pharmacies or street vendors.</p><p>How MedCheck Helps:</p><p>She can quickly verify products by scanning barcodes.</p><p>Receives alerts about harmful products on the market.</p><p>Provide a user friendly platform for checking products.</p><p>Can report any suspicious product</p><p>User Persona 2: Eze– Pharmacist and medical advisor on poisoning</p><p>Name: Eze Nwoye</p><p>Age: 33</p><p>Gender: Male</p><p>Occupation: Pharmacist</p><p>Location: Abuja, Nigeria</p><p>Tech Proficiency: High</p><p>Devices: Smartphone, Laptop</p><p>Goals:</p><p>Protect the society by only dispensing good medications.</p><p>Gain trust from customers through transparency.</p><p>Monitor product updates from regulatory bodies like NAFDAC.</p><p>Pain Points:</p><p>Difficulty tracking authenticity of large inventory batches.</p><p>Fear of unknowingly stocking counterfeit products.</p><p>Time-consuming manual product verification.</p><p>Most platforms don’t give details or good results on reported medications.</p><p>How MedCheck Helps:</p><p>Easily checks stock authenticity using batch verification.</p><p>Saves report history for audit trails.</p><p>Uses dashboard to view product alerts and warnings.</p><p>Gets detailed information on the drug scanned</p><p>User Persona 3: Blaise– Crypto Analyst</p><p>Name: Okoh Blaise Chukwunonso</p><p>Age: 22–34</p><p>Gender: Male</p><p>Occupation: Crypto Analyst</p><p>Location: Abuja, Nigeria</p><p>Tech Proficiency: Very High</p><p>Devices: Smartphone, Laptop</p><p>Goals:</p><p>Wants to buy products that are safe and good for use</p><p>Report suspect items found in local shops or online stores.</p><p>Pain Points:</p><p>Misinformation around counterfeit products is rampant.</p><p>Lack of a credible, easy-to-use verification platform, with no good interface.</p><p>How MedCheck Helps:</p><p>Provides a good interface and is easy to use that will be legit and credible.</p><p>Reports and tracks unsafe products in his area.</p><p>Verifies drinks, creams, and over-the-counter meds quickly.</p><p>User Persona 4: C– Pharmacist and drug marketer</p><p>Name: Chidebere Ejiofor</p><p>Age: 25- 34</p><p>Gender: Male</p><p>Occupation: Pharmacist and Drug Marketer</p><p>Location: Abuja, Nigeria</p><p>Tech Proficiency: High</p><p>Devices: Smartphone and laptop</p><p>Goals:</p><p>Ensure medications he sells are safe and trusted.</p><p>Prescribe safe medications to his patients</p><p>Improve customer confidence.</p><p>Pain Points:</p><p>No good process or platform for checking products.</p><p>No platform for offline mode.</p><p>Lack of detailed information on products on platforms.</p><p>How MedCheck Helps:</p><p>Simple scan-to-verify function saves time.</p><p>Gives detailed information on products that are reliable.</p><p>Offline mode will be accessible.</p><p>FigJam board snapshot, Sitemap</p><p>Figjam Link: <a href="https://www.figma.com/board/wsKb68TLo9Rpy0pAUCdWAC/Medcheck?node-id=31-2454&amp;t=vMLTQBkZgqZxUxxl-1">https://www.figma.com/board/wsKb68TLo9Rpy0pAUCdWAC/Medcheck?node-id=31-2454&amp;t=vMLTQBkZgqZxUxxl-1</a></p><p>Snapshoot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*LjzDYvxjUX7Lk3Wn5P_yyw.png" /></figure><p>Wireframes Mid-fidelity &amp; High-Fidelity</p><p>Mid-Fidelity Figma Links: <a href="https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=761-4253">https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=761-4253</a></p><p>Snapshoot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*jdENT7wOQZp6A2EL6aGHSQ.png" /></figure><p>High-Fidelity Figma Links: <a href="https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=0-1">https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=0-1</a></p><p>Snapshoot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*mmUN4Uh4fRBAxz5nneD-iQ.png" /></figure><p>Prototype (Figma link + screenshots)</p><p>Figma link: <a href="https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=0-1&amp;t=RA6ueKySGLu1QwMt-1">https://www.figma.com/design/ujQtjeG4zmDV8xoSzNGAHY/Team-Project-Capstone?node-id=0-1&amp;t=RA6ueKySGLu1QwMt-1</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*1KYbyydvqinLlpefM-QPlQ.png" /></figure><p>FRONT END ENGINEERS</p><p><strong>Introduction</strong></p><p>This project was developed as part of our CAPSTONE project. The aim was to create a website that allows users to verify if a product is authentic. Our team collaborated to design and develops an interactive, responsive, and user-friendly interface.</p><p><strong>Objectives</strong></p><p>· To create a clean and responsive website interface using HTML and CSS.</p><p>· To ensure smooth navigation between pages.</p><p>· To implement features that enhance user experience, such as dropdown menus and search bars.</p><p>· To ensure each page is linked to one another.</p><p><strong>Front-End Work</strong></p><p>As the front-end developer, we were responsible for implementing the user interface designed by the UI/UX team.</p><p>· We structured the web pages using HTML.</p><p>· Styled the layout, buttons, and navigation bar with CSS.</p><p>· Used little JavaScript (based on existing work) to make the navigation menu interactive (dropdowns and mobile toggle menu)</p><p>· Ensured that the website is <strong>responsive</strong> across devices using media queries.</p><p>· Collaborated with the backend team to set up environment servers, authentication security measures, connect forms and ensure smooth data flow.</p><p>Tools and Technologies Used</p><p>· <strong>HTML</strong> — to structure the webpages</p><p>· <strong>CSS3 / Flexbox / Grid</strong> — for styling and layout</p><p>· <strong>JavaScript </strong>— for interactivity</p><p>· <strong>VS Studio Code</strong> — for coding and editing</p><p>· <strong>GitHub</strong> — for collaboration and version control</p><p>· <strong>Live Server / Browser Developer Tools</strong> — for testing and ensuring it is displayed correctly</p><p><strong>MedCheck Dashboard/landing Page Frame</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*oOJJZelchmBpa1mX4cr2xg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Y5qHv177vBJlw85XpBC0wg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*rn2JAQRXikxepb1GE_sb2w.png" /></figure><p><strong>Challenges and Solutions</strong></p><p>· Challenge<strong>:</strong> The dropdown menu wasn’t responding on mobile view.</p><p>o Solution<strong>:</strong> Used JavaScript add Event Listener to toggle the menu visibility and adjusted CSS media queries. Js code was obtained from w3schools and stackflow.</p><p>· Challenge: The layout broke when resizing the window.</p><p>o Solution: Implemented CSS Flexbox and Grid to create a fully responsive layout.</p><p><strong>Conclusion</strong></p><p>MedCheck Website was brought to life with the use of web technologies: html, which is the foundation of the website and CSS, which is used to beautify the foundation and a little use of javascript to add interactivity to the website (dropdowns and doughnut chart). The project improved our teamwork and understanding of web technologies. We learned how to convert UI/UX designs into functional code and handle responsive design challenges.</p><p><strong>Live Website Link on Vercel</strong></p><p><a href="https://fake-drug-verification.onrender.com/"><strong>https://fake-drug-verification.onrender.com/</strong></a></p><p><strong>BACKEND ENGINEER</strong></p><p><strong>BACKEND STRUCTURE FOR MEDCHECK</strong></p><p>The MedCheck backend is the central system that verifies the authenticity of drugs, cosmetics and other products to protect consumers from counterfeits. It provides a secure and scalable platform that connects users to a trusted product database, ensuring transparency, accuracy and trust through real-time verification and strong API performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9kqd5falUsNAZJsN2Frakw.png" /></figure><p><strong>Key Achievements</strong></p><p>· <strong>Comprehensive RESTful API</strong> infrastructure built with Node.js and Express.js, enabling smooth communication between users, admins and verification services.</p><p>· <strong>User Authentication</strong> with JWT tokens, OTP verification and secure reset password.</p><p>· <strong>Drug Verification System</strong> that checks drug authenticity using <strong>NAFDAC registration numbers</strong> and database matching.</p><p>· <strong>Admin Management Features</strong> including CRUD operations for drug records and post, awareness post, and reports.</p><p>· <strong>Feedback and Reporting System</strong> allowing users to report suspicious drugs or share experiences.</p><p>In total, <strong>33 API endpoints</strong> were developed to cover authentication, verification, awareness, reporting and analytics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*oZLjBCzoDGKLhop5ukWjgw.png" /></figure><p><strong>Security &amp; Privacy</strong></p><p>Because MedCheck handles sensitive product data and user reports, strong security mechanisms were integrated from the ground up.<br> Key measures include:</p><p>· <strong>JWT-based authentication and email verification</strong> for secure access control.</p><p>· <strong>Password hashing with Bcryptjs</strong> to ensure user credential protection.</p><p>· <strong>Helmet, XSS-Clean and Mongo-Sanitize</strong> for HTTP and database protection.</p><p>· <strong>Rate Limiting</strong> to prevent brute-force attacks and API abuse.</p><p>· <strong>Environment variable management (dotenv)</strong> to secure credentials and configuration.</p><p>· <strong>Input validation and sanitization</strong> to protect against injection and cross-site attacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*CosbnqXkBOp2E1a_OIiUOA.png" /></figure><p>These safeguards collectively ensure that users’ information and product verification data are processed safely and confidentially.</p><p>Testing &amp; Quality Assurance</p><p>Reliability and accuracy are vital to the MedCheck mission. To ensure this:</p><p>· API endpoints were thoroughly tested using <strong>Postman</strong> for authentication, verification and CRUD operations.</p><p>· <strong>Unit and integration tests</strong> were performed on controllers and middleware to validate business logic.</p><p>· Continuous debugging and version control (Git/GitHub) maintained code stability.</p><p><strong>Challenges:</strong>Ensuring accurate verification of drug authenticity</p><p><strong>Solutions:</strong> Implemented a structured validation flow comparing NAFDAC registration numbers against a trusted dataset.</p><p><strong>Challenges: </strong>Protecting APIs from spamming and malicious use</p><p><strong>Solutions: </strong>Introduced <strong>Express-rate-limit</strong> and API key validation mechanisms.</p><p><strong>Challenges: </strong>File upload management for awareness and report images</p><p><strong>Solutions: </strong>Integrated <strong>Multer</strong> middleware with secure upload handling.</p><p><strong>Challenges: </strong>Maintaining database consistency</p><p><strong>Solutions: </strong>Optimized <strong>MongoDB schema design</strong> with proper indexing and reference-based relationships.</p><p>Each challenge strengthened the reliability, accuracy, and scalability of the backend system.</p><p><strong>Roadmap</strong></p><p>Looking forward, MedCheck aims to evolve its backend with more intelligent features:</p><p>· Integration of <strong>blockchain verification</strong> for immutable drug traceability.</p><p>· Implementation of <strong>machine learning</strong> to flag suspicious drug entries automatically.</p><p>· <strong>Microservice architecture</strong> for scalability and modular performance.</p><p>· <strong>Mobile API optimization</strong> for seamless mobile app integration.</p><p>· Expansion of the <strong>awareness and education module</strong> to reach a wider audience.</p><p><strong>Backend Design Conclusion</strong></p><p>MedCheck’s backend combines technology with public health protection, using secure APIs and structured data to fight counterfeit products. Its transparent, scalable and secure design builds user trust and supports a safer, more informed society.</p><p><strong>GitHub Repository:</strong><a href="https://github.com/Don-pizu/fake-drug-verification"> https://github.com/Don-pizu/fake-drug-verification</a></p><p><strong>Backend Deployed Link:</strong> <a href="https://fake-drug-verification.onrender.com/">https://fake-drug-verification.onrender.com</a></p><p><strong>CYBER SECURITY</strong></p><p>· <strong>Overview:<br> </strong>The analysis with Burp Suite, Nmap, Nikto was conducted as part of a cybersecurity review to assess the security posture of the “Fake Drug Verification” web application. The goal was to identify vulnerabilities, misconfigurations and risks, and to propose fixes before production deployment.</p><p>· <strong>Key Findings:</strong></p><p><strong>Network &amp; Port Exposure (Nmap)</strong></p><p>· The host<a href="http://fake-drug-verification.onrender.com/"> fake-drug-verification.onrender.com</a> resolves to multiple IP addresses (216.24.57.7 and 216.24.57.251) behind Cloudflare.</p><p>· Open ports detected:</p><p>· 80/tcp (HTTP) — Cloudflare HTTP proxy</p><p>· 8080/tcp (HTTP-alt) — Cloudflare HTTP proxy</p><p>· 443/tcp (HTTPS) — Cloudflare HTTP proxy</p><p>· 8443/tcp (HTTPS-alt) — Cloudflare HTTP proxy</p><p>· The presence of multiple HTTP(S) ports increases the attack surface.</p><p><strong>Web Server &amp; SSL/TLS (Nikto)</strong></p><p>· Server identified as Cloudflare; origin obfuscated but still leaks some headers.</p><p>· Valid TLS certificate issued by Google Trust Services (CN=WE1), cipher TLS_AES_256_GCM_SHA384.</p><p>· Uncommon headers found:</p><p>· origin-agent-cluster — non-standard header.</p><p>· rndr-id — reveals an internal identifier.</p><p>· x-render-origin-server — may disclose backend provider (“Render”).</p><p>· HTTP/3 / QUIC advertised but untested by Nikto, leaving a blind spot in scanning.</p><p><strong>Application Layer (Burp Suite)</strong></p><p>· Content Security Policy (CSP) headers detected but need manual verification for strictness (no automated issues flagged).</p><p>· No obvious high-risk vulnerabilities (SQLi, XSS) found in the quick automated checks, but manual testing needed to confirm.</p><p>· The application appears to rely heavily on client-side logic, which may expose API endpoints.</p><p><strong>2. Background and Objectives</strong></p><p>· <strong>Project Context:<br> </strong>This project aims to assess the security posture of the public web application <a href="https://fake-drug-verification.onrender.com/">https://fake-drug-verification.onrender.com/</a> which allows users to verify drug authenticity. The scope is limited to the public website.</p><p>· <strong>Objective of the Tool Use:</strong></p><p>· Nmap: Map open ports and services.</p><p>· Nikto: Automated vulnerability scan of web server.</p><p>· Burp Suite: Intercept and analyse HTTP requests/responses; test input fields.</p><p>3. Methodology</p><p>The assessment proceeded through the following phases:</p><p>· Reconnaissance: To find all visible endpoints, forms, parameters, sub-pages. Map site structure.</p><p>· Scanning:</p><p>· Port scanning (Nmap) to find open ports and services</p><p>· Web server scanning (Nikto) to detect outdated components, misconfigurations</p><p>· Manual Inspection/Testing with Burp Suite:</p><p>· Open Burp suite- Proxy- intercept requests from the browser to the site<br> Session and cookie handling: check flags like HttpOnly, Secure, SameSite</p><p>· Crawl the site (spider) to discover hidden parameters and endpoints</p><p>· Check security headers, cookie flags, and input validation</p><p>· Screenshot request/response</p><p>· SSL / TLS Review: To check certificate validity, support for weak ciphers, protocol versions (TLS 1.0, 1.1 etc.)</p><p>· Security Headers Review: check for Content Security Policy, X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security, etc.</p><p>3.1 Tool Configuration</p><p>· Nmap runs from Kali Linux with -sV -Pn options to detect service versions.</p><p>· Nikto configured to scan over HTTPS: nikto -h <a href="https://fake-drug-verification.onrender.com/">https://fake-drug-verification.onrender.com</a></p><p>· Burp Suite Community Edition with browser proxy configured to intercept all traffic to the target.</p><p>· Testing environment: Browser + Proxy + Interception.</p><p>· Scope limited to the public endpoints of the application.</p><p>Below are screenshots of each tool’s dashboard/configuration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*zmmw59Qz-85yDMP22o1y_A.png" /></figure><p><strong>Nmap dashboard/configuration</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*WCSnicY_5cmGGMAYmJroAA.png" /></figure><p><strong>Nikto dashboard/configuration</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*EixeMxQF4UvUCnPDlUngkw.png" /></figure><p><strong>Burp Suite dashboard/configuration</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*KG3PIjDtZoIps0pmlec_aA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*HNE1nCLv2PXVuyn47wkh-w.png" /></figure><p><strong>3.2 Execution Process</strong></p><p>· Mapped all accessible endpoints and features.</p><p>· Intercepted HTTP requests to test input validation and error handling.</p><p>· Performed passive and active checks for headers, authentication, and misconfigurations.</p><p><strong>3.3 Monitoring and Analysis:</strong></p><p>· Logged HTTP responses and looked for reflected input, error messages, or hidden directories.</p><p>· Checked for SSL/TLS strength and configuration details with testssl.sh/SSL Labs.</p><p>· Documented all findings with screenshots and saved raw tool outputs for appendices.</p><p><strong>4. Findings and Analysis</strong></p><p><strong>4.1 Indicators of Compromise (IOCs):</strong></p><p>· <strong>Detected IOCs:<br> </strong>During the assessment of <a href="https://fake-drug-verification.onrender.com,/">https://fake-drug-verification.onrender.com,</a> the following publicly visible indicators were observed:</p><p>· Domain/IPs: The site resolves to 216.24.57.7 and 216.24.57.251 (Cloudflare-proxied).</p><p>· Open Ports: 80 (HTTP), 443 (HTTPS), 8080 (HTTP-alt), and 8443 (HTTPS-alt) were accessible at the time of testing.</p><p>· Exposed Headers: x-render-origin-server (revealing Render as the backend host), rndr-id (internal identifier) and origin-agent-cluster (browser isolation setting).</p><p>· HTTP/3 Endpoint: Advertised via alt-svc header but untested.</p><p>· TLS Fingerprint: Certificate issued by Google Trust Services (CN=WE1) using TLS_AES_256_GCM_SHA384.</p><p>These indicators outline the network and application footprint visible externally and should be monitored or minimised to reduce reconnaissance opportunities for attackers.</p><p><strong>4.2 Vulnerability and Behavioral Analysis:</strong></p><p><strong>Combined Analysis of Nmap &amp; Nikto Results</strong></p><p><strong>Finding</strong></p><p><strong>Evidence (from Nmap/Nikto)</strong></p><p><strong>Risk &amp; Impact</strong></p><p>Recommendation / Mitigation</p><p><strong>Severity</strong></p><p>Open Ports — 80/tcp, 8080/tcp, 8443/tcp</p><p>Nmap shows: • 80/tcp open http? (Cloudflare HTTP proxy)• 8080/tcp open http-proxy• 8443/tcp open HTTPS (Cloudflare HTTP proxy)• 443/tcp open HTTPS (main site)</p><p>Multiple open ports increase attack surface. Attackers could test these for misconfigurations, HTTP smuggling, or caching issues.</p><p>Ensure unused ports are closed. If all are needed, apply strict firewall rules and TLS everywhere.</p><p><strong>Medium</strong></p><p>No Service Banners beyond Cloudflare</p><p>Nmap detected Cloudflare proxy but not the backend server type.</p><p>Cloudflare hides the backend, reducing direct exposure. This is good for security.</p><p>Continue to proxy traffic through Cloudflare.</p><p><strong>Positive</strong></p><p>Uncommon Headers Detected</p><p>Nikto shows:rndr-id headerorigin-agent-cluster headerx-render-origin-server headeralt-svc header advertising HTTP/3</p><p>Custom or uncommon headers can leak infrastructure information, aiding recon. x-render-origin-server reveals hosting provider.</p><p>Minimize or obfuscate headers revealing backend hosting (like Render). Review Cloudflare Worker/Origin settings to strip or generalize these headers.</p><p><strong>Medium</strong></p><p>SSL/TLS Config Good</p><p>Nikto reports TLS AES_256_GCM_SHA384 (modern cipher), issued by Google Trust Services.</p><p>Strong encryption prevents most MITM attacks.</p><p>Maintain current TLS configuration.</p><p><strong>Positive</strong></p><p>Nikto HTTP/3 Limitation</p><p>“Nikto cannot test HTTP/3 over QUIC” — the scan didn’t cover HTTP/3.</p><p>Some vulnerabilities may exist on HTTP/3 endpoints that weren’t scanned.</p><p>Run additional HTTP/3 scanning tools or disable HTTP/3 until fully tested.</p><p><strong>Informational</strong></p><p>No obvious outdated server components</p><p>Nikto did not list outdated Apache, PHP, etc. (because Cloudflare hides backend).</p><p>Good practice. But the backend still needs patching even if hidden.</p><p>Regularly patch the origin server even when behind Cloudflare.</p><p><strong>Positive</strong></p><p><strong>Penetration Testing on Burp Suite</strong></p><p><strong>Finding</strong></p><p><strong>Description &amp; Evidence</strong></p><p><strong>Risk &amp; Impact</strong></p><p><strong>Recommendation / Mitigation</strong></p><p><strong>Severity</strong></p><p><strong>Content Security Policy (CSP) allows unsafe-inline styles</strong></p><p>Response header: Content-Security-Policy: default-src ‘self’; … style-src ‘self’ https: ‘unsafe-inline’</p><p>Inline styles can be abused to inject malicious scripts or styles that bypass filters, increasing XSS risk.</p><p>Remove ‘unsafe-inline’ from style-src; move all inline styles to external stylesheets and use nonces or hashes for any required inline scripts/styles.</p><p><strong>Medium</strong></p><p><strong>Strict-Transport-Security (HSTS) enabled</strong> (Best Practice)</p><p>Strict-Transport-Security: max-age=31536000; includeSubDomains present.</p><p>Forces HTTPS for one year including subdomains — mitigates SSL stripping.</p><p>Continue maintaining and periodically reviewing HSTS policy.</p><p><strong>Positive</strong></p><p><strong>Cross-Origin Policies correctly configured</strong> (Best Practice)</p><p>Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Resource-Policy: cross-origin present.</p><p>Minimizes some cross-origin at it tacks such as XS-Leaks.</p><p>Continue maintaining these headers; review when adding new resources.</p><p><strong>Positive</strong></p><p><strong>X-Frame-Options header set</strong> (Best Practice)</p><p>X-Frame-Options: SAMEORIGIN present.</p><p>Prevents clickjacking attacks.</p><p>Maintain this header; test any legitimate iframes after deployment.</p><p><strong>Positive</strong></p><p><strong>X-XSS-Protection header disabled</strong></p><p>X-XSS-Protection: 0 disables browser’s legacy filter.</p><p>Although the header is deprecated, explicitly disabling it can trigger alerts in some scanners.</p><p>Omit the header entirely or use 1; mode=block if legacy browsers must be .</p><p><strong>Low</strong></p><p><strong>Server disclosure</strong></p><p>Headers: Server: cloudflare and X-Render-Origin-Server: Render reveal hosting stack.</p><p>Gives attackers reconnaissance information to tailor attacks against Cloudflare or Render.</p><p>Minimize server version disclosure by using generic server headers or security middlewares.</p><p><strong>Medium</strong></p><p><strong>No visible rate-limiting or CAPTCHA on verification endpoints</strong></p><p>Traffic inspection shows no rate-limit headers or anti-automation controls on /api/verify (or similar endpoints).</p><p>Could allow brute force, automated scraping or enumeration of valid drug codes.</p><p>Implement API rate-limiting, CAPTCHA, or token-based throttling to protect endpoints.</p><p><strong>High</strong></p><p><strong>X-Content-Type-Options present</strong> (Best Practice)</p><p>X-Content-Type-Options: nosniff present.</p><p>Blocks MIME-type sniffing, reducing drive-by attacks.</p><p>Maintain this header.</p><p><strong>Positive</strong></p><p><strong>4.3 Risk and Impact Assessment:</strong></p><p>· <strong>Risk &amp; Impact Summary for Nmap &amp; Nikto</strong></p><p>· Medium Risk: Multiple open ports (80, 8080, 8443) could be abused if misconfigured.</p><p>· Medium Risk: Infrastructure headers (x-render-origin-server) leak hosting provider details.</p><p>· Informational: HTTP/3 endpoint not scanned — potential blind spot.</p><p>· Positive: TLS is strong, Cloudflare proxying hides backend server software</p><p>· <strong>Risk and Impact Summary on Burp Suite</strong></p><p>· The most pressing risk is lack of brute-force protection on verification endpoints (High severity).</p><p>· Inline styles in CSP (Medium) and server disclosure (Medium) slightly increase the attack surface.</p><p>· Other headers (HSTS, X-Frame-Options, X-Content-Type-Options, Cross-Origin policies) are configured correctly and reduce risk.</p><p>5. <strong>Recommendations</strong></p><p><strong>5.1 Immediate Remediation Actions for Nmap &amp; Nikto:</strong></p><p>· Audit open ports — close 8080 or 8443 if not needed.</p><p>· Strip or generalize origin-disclosing headers at Cloudflare/Render level.</p><p><strong>Immediate Remediation Actions for Burp Suite</strong></p><p>· Add API rate-limiting and CAPTCHA/anti-automation on sensitive endpoints.</p><p>· Refine CSP to remove ‘unsafe-inline’ from style-src.</p><p><strong>5.2 Medium-Term Mitigation for Nmap &amp; Nikto :</strong></p><p>· Test HTTP/3 endpoints using tools supporting QUIC.</p><p>· Perform authenticated scans or internal tests directly on the origin server.</p><p><strong>Medium-Term Mitigation for Burp Suite</strong></p><p>· Mask or generalize server header values.</p><p>· Review header configurations quarterly.</p><p><strong>5.3 Long-Term Mitigation for Nmap &amp; Nikto</strong></p><p>· Maintain TLS best practices.</p><p>· Continue to update the backend regularly even though Cloudflare hides it</p><p><strong>Long-Term Mitigation for Burp Suite</strong></p><p>· Continue security testing after any new feature releases.</p><p>· Integrate automated security scanning in CI/CD pipeline.</p><p><strong>6. Conclusion</strong></p><p>· <strong>Summary of Findings:<br> </strong>The assessment of <a href="https://fake-drug-verification.onrender.com/">https://fake-drug-verification.onrender.com</a> using Nmap, Nikto, and Burp Suite demonstrates that the application is generally well-protected through Cloudflare proxying, strong TLS configuration, and a restrictive Content Security Policy (CSP). These measures significantly reduce direct exposure of the origin server and mitigate common classes of web-based attacks such as content injection and clickjacking.</p><p>However, the scans revealed several areas that warrant attention:</p><p>· Open ports (80, 8080, 8443) increase the attack surface and should be reviewed for necessity.</p><p>· Information disclosure through headers (e.g., x-render-origin-server, rndr-id) could aid attackers in fingerprinting the infrastructure.</p><p>· HTTP/3 (QUIC) endpoints remain untested, representing a blind spot in the security posture.</p><p>· While Burp Suite confirmed CSP, HSTS, and XSS protections are in place, misconfiguration or policy gaps (e.g., allowance of unsafe-inline) could still pose a risk if not continuously monitored.</p><p>Overall, the site demonstrates a moderate-to-strong security posture with effective shielding against common vulnerabilities, but improvements in port hardening, header sanitization, and HTTP/3 testing are required to reduce the risk of exploitation. Regular penetration testing, internal origin scanning (bypassing Cloudflare), and patch management remain critical to maintaining a secure deployment.</p><p><strong>Risk Posture:</strong></p><p>· <strong>Strengths:</strong> Cloudflare proxy, TLS 1.3 with modern ciphers, strict CSP, security headers.</p><p>· <strong>Weaknesses:</strong> Open ports, header information leakage, incomplete HTTP/3 testing.</p><p>· <strong>Overall: Medium risk</strong> — good baseline security, but requires proactive hardening and monitoring.</p><p>· <strong>Next Steps:</strong></p><p>· Review and Minimize Open Ports</p><p>· Verify whether ports 80, 8080, and 8443 are actually needed for production.</p><p>· If not, close or firewall them at the network or Cloudflare level to reduce exposure.</p><p>· Harden or Sanitize HTTP Headers</p><p>· Remove or obfuscate headers such as x-render-origin-server, rndr-id, and origin-agent-cluster where possible.</p><p>· Confirm that server version information is not exposed in error pages or responses.</p><p>· Conduct HTTP/3/QUIC Security Testing</p><p>· Because Nikto and other scanners currently cannot test HTTP/3, perform a manual review or use tools specifically built for QUIC to ensure no misconfigurations or vulnerabilities.</p><p>· Perform Internal Origin Scans</p><p>· If feasible, scan the origin server directly (bypassing Cloudflare) to identify any weaknesses hidden behind the proxy.</p><p>· Ensure patching of all backend services.</p><p>· Continuous Web Application Testing</p><p>· Schedule periodic OWASP Top 10 vulnerability testing (XSS, CSRF, SQLi, IDOR, etc.) with tools like Burp Suite Pro or manual testing.</p><p>· Verify that CSP does not allow unsafe inline scripts or overly broad sources.</p><p>· Enable and Monitor Security Logs</p><p>· Implement monitoring for suspicious requests, unexpected response codes, or spikes in traffic on all exposed ports.</p><p>· Integrate logs with a SIEM (Splunk, ELK, etc.) for better incident detection.</p><p>· Conduct a Formal Penetration Test</p><p>· Beyond automated scanning, commission a full penetration test to identify business-logic flaws and chained attacks that automated tools may miss.</p><p><strong>Appendix: Additional Data</strong></p><p>· Raw Logs and Tool Outputs:</p><p>Nmap Vulnerability Scan using Kali Linux on VMware</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*DtrcbEyb84PNetskiVR1xQ.png" /></figure><p>Nikto Scan using Kali Linux on VMware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*8m5ZElwvkehRpRl0U3Fgpg.png" /></figure><p>Burp Suite using Kali Linux on VMware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*7q6_3Z67Pz846_smifcm-Q.png" /></figure><p>Additional Visualizations and Screenshots:</p><p>SSL/TLS Configuration- to document weak ciphers or certificate issues, from the analysis you’ll see that for both IP the grade result shows A+</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*f1BuPzpBQNsULfzh-jIHLw.png" /></figure><p>Visualizations and Screenshots from analysis using Any run</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*4ANKn_JPDLi9EDFdCrKbAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*AhySTVuk2FmXwxXqK-BQRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*Salbu-LqO__iR1P6xoqp1g.png" /></figure><p>Visualizations and Screenshots from analysis using Virus Total</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*1n3ZnWmp8dsnJvKfbpMdxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*IPoJTVh9Q7lPlK58gFGklQ.png" /></figure><p>Conclusion</p><p>The MedCheck project has successfully developed and implemented a robust verification system for identifying fake drugs, products, and drinks. By leveraging cutting-edge technology and data analytics, MedCheck provides a reliable and efficient solution for consumers, healthcare professionals, and regulatory agencies to verify the authenticity of medicinal products and beverages.</p><p>This technical report captures an important milestone in the development of the Verification of fake drugs,drinks and products(Medcheck) platform. The work completed demonstrates how thoughtful design, strong technical foundations, and a clear sense of purpose can come together to create a system that is both functional and compassionate. From the user interface to the backend services, every element has been shaped with the safety, privacy, and trust of survivors in mind.</p><p>The team has shown remarkable dedication in addressing challenges, refining solutions, and ensuring that the platform is secure, reliable, and accessible.</p><p><a href="https://docs.google.com/document/d/1sRrxFLB5FQVsFMwUhXIsLOPaxuoszWX0LZRS7-qC0is/edit?tab=t.0">https://docs.google.com/document/d/1sRrxFLB5FQVsFMwUhXIsLOPaxuoszWX0LZRS7-qC0is/edit?tab=t.0</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*sl6iGdOD1SRJomz48di3uA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*pFnXCm36wIyfhFgKESSnog.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c35e76d99e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GLOBAL SCAMS AND FINANCIAL FRAUD ANALYSIS]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/global-scams-and-financial-fraud-analysis-6b1409281259?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b1409281259</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 10:17:35 GMT</pubDate>
            <atom:updated>2025-07-02T19:32:26.265Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>(TEAM 3 PROJECT TECHNICAL REPORT) </em></strong>By Daniel Bayo Olaleye</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x0qlO9GOjXqqHbai" /><figcaption>Scam and Fraud</figcaption></figure><h4>Project Overview</h4><p>Global scam and financial fraud involve deceitful practices to exploit individuals and organizations financially. These scams can take many forms, including phishing, identity theft, Ponzi schemes, and more.<br>Scammers often use technology to target victims worldwide. Financial losses can be significant, and victims may suffer emotional distress.<br>To protect yourself, stay informed about common scams, verify information, and report suspicious activities. This project analyzes global cyber scam incidents to identify trends, evaluate financial impact, and understand both victim and offender profiles. With cybercrime on the rise, this analysis seeks to empower stakeholders with data-driven insights for better decision-making in cyber risk management and fraud prevention.</p><h4><strong>Project Goals and Objectives</strong></h4><p>This project aims to identify regions, countries, and demographics affected majorly by different scam channels and scam types and develop effective strategies to minimize financial losses, strengthen internet controls, and educate such affected places and demographics to detect anomalies.</p><p>The objective is to analyze historical cyber scam data to:</p><ul><li>Identify trends in scam types and channels.</li><li>Assess the financial losses and recovery rates.</li><li>Understand the demographics of victims and profiles of offenders.</li><li>Generate actionable recommendations to reduce future risks.</li></ul><p>Cyber scams result in significant financial loss and emotional distress. Organizations and individuals often lack data-backed insights into the nature of these attacks. This analysis seeks to answer:</p><ul><li>Which scam types cause the highest losses?</li><li>What are the common characteristics of victims and offenders?</li><li>How effective are current defense mechanisms?</li></ul><h4>My Role as a Project Manager</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TXbs3TiFs6qHjCbJ" /><figcaption>My role as Project Manager</figcaption></figure><p>I led a data analytics Team through the full project life cycle, The Project life cycle started from the initiation phase, where the stakeholder kickoff meeting was held which was on the 23 of April 2025. The stakeholders gave the goals, objectives, deliverables and the timeline of the project which is for 4weeks. I opened a WhatsApp group and added all my team members for initial communication, afterward during the project we communicated using slack interface. Then fixed an onboarding meeting which was scheduled to take place on the 26th of May 2025.</p><p>Afterwards i went into deep research for two days on the project given and to know the Project Methodology to use in achieving the deliverables; “Global Scam and Financial Fraud Analysis” i designed the project <a href="https://docs.google.com/document/d/1a9U-QDBxUonSuOUZ9iQkXTfUfV4rruRuZH59wSNYCTA/edit?usp=sharing">charter</a> highlighted the goals, objectives deliverable, Scope, Timelines, Milestones, Project risk, risk mitigation strategies and the names of my team Members.</p><p>I Scheduled a meeting for 26th of April, GOOGLE MEET was used all through the project phase for meetings as agreed collectively which was in alignment with our organizational culture, and i created a meeting agenda Prior to the meeting which was forwarded to each member of the team in order to prepare their minds and for effective collaboration in the meeting. I had my Team kickoff meeting 26th of April 2025 with seven data Analyst, where proper introduction was made while we followed the meeting agenda, i presented my project charter and all the items on it which includes Project goals and objectives, Scope, deliverables, project risk and communication plan, was deliberated on collaboratively and necessary corrections were effected, then the Project chatter was forwarded to the Project Stakeholder for approval.</p><p>After the approval of the Project chatter i created a work <a href="https://docs.google.com/document/d/1ITF1cxde-gqCczQqpY6rv0EGaZnwoi0zDAkVe8tPP8I/edit?usp=sharing">break down structure</a> in an hierarchical and tabular order for the team to be able carry out task effectively and in order to work with timeline and to hit milestones, which i was able to submit before the deadline 30th of April 2025.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7anDtabF0KeP9l6Fg1oHg.jpeg" /></figure><h4>Planning Phase</h4><p>We had our second meeting on the 28th of April 2025. I explained the agenda for the day and then appointed Mr Ugonna Charles as the team head after getting a collaborative response from the team and his responsibility was to ensure the smooth running of the project and delegating responsibility(tasks) to the team using the work break down structure, then i made emphasis on the timeline, milestone, team work and how important to go through the simulation over and over again for clarity in the deliverables of the project. i instructed Miss Chidimma Esther to highlight the phases on the Work break down having the timeline and milestone in view which was done like this;</p><p><strong>Work Breakdown Structure</strong></p><p>Phase A: Data Sourcing — 29th April — 30th April 2025</p><p>Phase B: Duty Scheduling by DA team lead — 1st May 2025</p><p>Phase C: Data cleaning and Pre-Analysis — 2nd May — 4th May, 2025</p><p>Phase D: Data analysis, visualization and insight generation — 5th May — 10th May, 2025</p><p>Phase E: Dashboard creation and KPI generation — 10th May, 2025–15th May, 2025</p><p>Phase F: Reviews and corrections — 16th May, 2025–19th May 2025</p><p>Suggestions on how to acquire and choose the dataset for the analysis were shared, during which Mr. Ugonna noted that as the team leader, it becomes easier for the team to delegate and select the appropriate dataset once everyone has submitted their datasets. Additionally, using the work breakdown structure would assist in assigning different tasks to the Data Analysts, thereby speeding up and enhancing the project’s progress. Then i instructed the team to go in search of data set for the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FyhexTPX2lt03nRBRKsQ5w.jpeg" /><figcaption>Image of our meetings</figcaption></figure><p>We Had 9 status update meetings from the initiation phase to the final phase of the project where we were able to come up with the Data set, Project task, Kpi’s, Observations and recommendation, Dash board 1, Dash board 2, yearly trend of financial loss, scam type vs total loss, total financial loss country, number of attack by year, different mechanism effectiveness, region vs number of affected user, i.t knowledge level vs number of affected users, offenders type vs attack frequency, scam channels vs total amount recovered, the full documents can be found in this <a href="https://docs.google.com/spreadsheets/d/1wxdDG87h71LT43ETP4-XZSe5BWA3O69D/edit?usp=sharing&amp;ouid=111073839504828148881&amp;rtpof=true&amp;sd=true">link</a>.</p><h4>IN-ANALYSIS OBSERVATION</h4><p><strong>A. Yearly Trend of Financial Loss</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BX5YuR_c9IAbpTly_k0CEw.jpeg" /><figcaption>Yearly Trend of Financial loss</figcaption></figure><p>As at years between 2018–2019,the most financial loss due to global scams was $11,723,680,000 while the least financial loss was between 2000–2001 totaling to $715,330,000</p><p><strong>B. Scam Type vs. Total Financial Loss</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*XVAq12jWIU-hVlRcP4LXjw.jpeg" /><figcaption>Scam Type vs Total Financial Loss</figcaption></figure><p>Ponzi Scheme scam had the biggest financial loss amounting to $11,914,720,000, while lottery scam had the least financial loss of $2,554,670,000 in total.</p><p><strong>Total Financial Loss by Country</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*VmPTXoZ1whRl5sMuYH3vyg.jpeg" /><figcaption>Total Financial Loss by Country</figcaption></figure><p>The United States lost $20,644,010,000 to scams which happened to be the highest while Germany lost $822,360 which was the least.</p><p><strong>D. Number of Attacks by Year</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCH97Zz6vbcRH1CvhciyNA.jpeg" /><figcaption>Number of Attacks by Year</figcaption></figure><p>The highest financial fraud occurred in the year 2019 with 131 incidents, while 2006 recorded the least occurrence with just 3 incidents.</p><p><strong>E. Region/Continent vs. Number of affected users</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*1mQ1i0hm8UzVvy6YLlUuSQ.jpeg" /></figure><p>North America lost so much to financial scam as it has the highest number of affected victims, which is 269,129,885 while Oceania had the least affected victims totaling to 10,969,310</p><p>F.<strong> IT Knowledge Level vs Number of Affected Users</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*eyy8ws4OdBufT3NSG74zgg.png" /><figcaption>IT Knowledge Level vs Number of Affected Users</figcaption></figure><p>People with medium IT knowledge lost the most money which contributed to 38% of financial fraud</p><p><strong>G. Scam Channel vs. Total Amount Recovered</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*Y5Vr4d_OTHmO_g2_wCMmIQ.jpeg" /><figcaption>Scam Channel vs. Total Amount Recovered</figcaption></figure><h4>IN-ANALYSIS INSIGHTS</h4><p>1. Organizations can look into years with the least financial loss due to scams and implement those same policies in the years to come.</p><p>2. Organizations should promote more public education on fraudulent schemes.</p><p>3. The United States should enforce stricter cyber laws to reduce scams.</p><p>4. North America can look into continents with fewer scams and incorporate what they are doing into their systems.</p><p>5. Organizations can analyze 2019 scam trends to build preventive models to reduce scams.</p><p>6. The people with moderate IT knowledge should engage in more cybersecurity training</p><p>7. Strategies used to recover money stolen through email scams should be implemented in other scam channels.</p><p>8. Public awareness of common personal scams like impersonation and phishing should be increased to help users spot and avoid them.</p><p>9. Security models that go beyond Antivirus should be implemented to reduce scams</p><p><strong>Excel Dashboard 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnLHy56f1b4HqvuvKavcQQ.jpeg" /><figcaption>Excel Dashboard 1</figcaption></figure><p><strong>Excel Dashboard 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yArCXOJtOewMNlcnUzFHpg.jpeg" /><figcaption>Excel Dashboard 2</figcaption></figure><p><strong>Power Bi Dashboard 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*6Hz_6N_SdGb8F6NaNBb4vQ.jpeg" /><figcaption>Power Bi Dashboard 1</figcaption></figure><p><strong>Power Bi Dashboard 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*wxvV0z-qbyuSl69wm1k5sw.jpeg" /><figcaption>Power Bi Dashboard 2</figcaption></figure><p><strong>Power Bi Dashboard 3</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*FTMNEPlR5hbF1foXGWfYFQ.jpeg" /><figcaption>Power Bi Dashboard 3</figcaption></figure><p><strong>Power Bi Dashboard 4</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*FTMNEPlR5hbF1foXGWfYFQ.jpeg" /><figcaption>Power Bi Dashboard 4</figcaption></figure><h4>FINAL OBSERVATIONS</h4><p><strong>REGION</strong></p><p>1.North America seems to be the continent that has the most cases of scam in terms of affected users of about 269,129,885 users (over 20 years). Pre COVID (2018/2019) is the peak year for scam in this region, losing $11,723,680,000. The financial loss could be due to staggering numbers of user affected in this region.</p><p>2.Canada and The United States are the countries affected in South American region. Canada lost $4,794,160,000 while USA lost almost five times as Canada ($20,644,010,000)</p><p>3. Investment fraud contributed to the most financial loss in Africa while Ponzi Scheme is the most prominent type of scam in the Asia, Oceania, North and Southern America and European regions contributing about 51% compared to the global report</p><p>4. North America tends to recover more from financial loss with the use of Email ($8,858,650), the least being from SMS $1,224,200</p><p>5. Oceania is the continent with the least affected users 10,969,310, Australia being the only country from this region contribute to the total financial loss of $1,722,680,000.</p><p>6. Oceania is the least affected continent in terms of users, its observed that South America leads with the lowest financial loss of $1,638,860,000.</p><p><strong>IT KNOWLEDGE LEVEL</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yKH5Yf3IWEPy6fpD" /><figcaption>I.T KNOWLEGDE</figcaption></figure><p>1. Individuals with medium IT knowledge (261) are frequently the offenders in scams, while the syndicate with medium IT knowledge is the least (64). The same thing is reported for the low and high IT knowledge, although corporate insiders seem to be the lowest (33) and (39), respectively.</p><p>2. Ponzi scheme is obviously the most scam type of the three IT knowledge level: Low IT knowledge: $4,396,270,000 from Ponzi schemes; medium IT knowledge: $4,601,970,000 and High IT knowledge: $2,916,480,000</p><p>3. Online shopping fraud should not go unnoticed as it emerges second to Ponzi scheme</p><p>4. The number of attacks from a high IT knowledge standpoint: there has been a general increase but major consolidation in the number of attacks over the years, with 2019 being the peak year (43 attacks) and a drastic fall (15) in the number of attacks in the COVID year 2020. There has been a stable number until a fall in 2023, which might be due to the fact that there is not enough data recorded for 2023.</p><p>5. People with low IT knowledge contributes to a massive increase in attack in 2018 (42); number of attacks saw a slight fall in 2019 (36) with a massive plunge in numbers in 2020 (12)</p><p>6. The same trend happens to people with medium IT knowledge, as there is a fall in 2020.</p><h4><strong>OCCUPATION AFFECTED</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KoDoRKT2AScl_EgR" /><figcaption>OCCUPATION AFFECTED</figcaption></figure><p>1. An average of 548,763 victims are unemployed, 35% having a high IT knowledge level, 33% medium, and 32% low IT knowledge. As unemployed users are more affected to online shopping fraud, losing about $1,012,990,000.</p><p>2. Business owners seem to be more defrauded through business email compromise losing $2,792,130,000, with 38% of medium IT knowledge being defrauded, 33% high knowledge, and 29% with low knowledge.</p><p>3. The IT professionals tend to lose more money to Ponzi scheme fraudulent acts, losing $841,070,000 and only recovering $1,468,100 via email only.</p><p>4. The retired folks were more duped through the Ponzi scheme and online shopping fraud, losing $1,114,920,000 and $1,108,670,000, respectively. 2018–2019 is literally the year that the retired folks were more duped $1,067,400,000</p><p>5. Ponzi Scheme seems to be the most prominent scam inflicted on victims</p><h4><strong>FINAL RECOMMENDATIONS</strong></h4><h4>REGION</h4><p>1. Localize Scam Awareness Campaigns: Launch region-specific education campaigns (e.g in North America) through schools, workplaces, and media to teach people how to spot and avoid scams like Ponzi schemes and online fraud.</p><p>2. Invest in Regional Cybercrime Task Forces: Countries like the USA and Canada should invest in specialized cybercrime units with cross-border collaboration to investigate and shut down major scam networks.</p><p><strong>IT KNOWLEDGE LEVEL</strong></p><p>1. Tailored Cybersecurity Training: Provide mandatory cybersecurity training for individuals in high-risk knowledge groups, especially those with medium IT skills who may feel confident but lack a complete understanding of scam risks.</p><p>2. Gamified Learning for Low IT Users: Develop mobile-friendly apps or community programs that teach scam detection using real-world examples and interactive scenarios targeted at low IT literacy groups.</p><p><strong>OCCUPATION AFFECTED</strong></p><p>1. Online Safety Programs for the Unemployed and Retired: Partner with employment centers and retirement communities to offer free workshops on recognizing and reporting scams, especially online shopping and Ponzi schemes.</p><p>2. Secure Communication Tools for Business Owners: Promote the use of verified email platforms and encrypted communication tools to prevent business email compromise, particularly in small and medium-sized businesses.</p><h4>PROJECT METHODOLOGY</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvT6zTGPpSHl6Eluy0jp-A.jpeg" /></figure><p>Agile/scrum methodology</p><p>I used agile/scrum methodology because its iterative and flexible in nature and the nature of the project work given is also flexible. using the agile/scrum methodology i was able to work on different task at the same time and we were able to go on micro sprints for tasks to be accomplished in due time. and the Agile/scrum helped in mitigating risk and scope creeps internally and externally, we were able to update our dataset and the project at large at every point of need and this was only possible because i used the agile/scrum methodology.</p><p>TOOL USED</p><p>1.Microsoft excel: This was used by my data analytics team to clean up data, analyze the data by performing statistical analysis, data modeling, and forecasting. Micro Soft excel was also used for data visualization i.e creating charts, graphs, and dashboards to represent data insights, Micro soft excel was also used for generating report and summaries to communicate finding.</p><p>2. Google Meet: This was used basically for our meetings and through this platform we were able to record all our meetings from the initial phase of the project to the last phase. then google mail was also use in sending milestones to the stakeholders in order to avoid any form of external scope creep which may lead to rejection of deliverables.</p><p>3. Slack interface: This platform was used as a communication tool for the team, where meetings are been scheduled and personal messages to team members was sent as occasion arises.</p><p>4. Power Bi: The data Team was able to use power bi to create iterative report and dashboards with rich set of visualization, facilitating the discovery of deeper insight and trends.</p><p>CHALLEGES FACED:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*urORgApbHvVNBr8E" /><figcaption>SOLVING A PROBLEM</figcaption></figure><p>As a team we didn&#39;t face much challenges, because i was able to create a collaborative work space, when the project was given to us and was able to apply my leadership skills in managing the team even when a new member was added after the kickoff meeting, the new member was still usable and responsible towards the progress of the project.</p><p>The first challenge we had was where and how to source out required and current data on the given project topic, which we all agreed to go for secondary data and we were able to solve that challenge collectively.</p><p>Second challenge is having a team member who is temperamental and needed to be managed well by me the project manager and the Team lead.</p><p>Third Challenge we face was that google meet record for only one hour so we have to rush some of our meetings in order to meet up with time.</p><p>INSIGHT GAINED:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rhw88itsing2cttW" /><figcaption>INSIGHT GAINED</figcaption></figure><p>1.The Project Chatter was a road map to what we wanted to achieve which made the task easy to direct knowing the miles stones and timelines, it is indeed a practical knowledge acquired.</p><p>2.The Work breakdown structure further helped the project to be dividable into smaller chunks, this made all the team members responsible and all hands was on deck through out the project phase.</p><p>3.Slack interface helped our communication strongly in respect to scheduling a meetings, direct messages to team members and it made all team members use to the platform in terms of communication because the WhatsApp group was closed in order to facilitate communication on Slack.</p><p>Insight concerning the project topic Global Scam and Financial Fraud</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xQKmpkV3jMOuQ7qI" /><figcaption>Insight Gained</figcaption></figure><p>1.Types of scams and financial fraud (phishing, Ponzi schemes).<br>2. Methods used by scammers (social engineering, fake websites).<br>3. Impact on individuals, organizations, and economies.<br>4. Importance of vigilance and skepticism.<br>5. Role of technology in detection and prevention.<br>6. Best practices for protection (e.g verifying information, using security software).<br>7. Global trends and patterns in financial fraud.<br>8. Collaboration and information-sharing to combat fraud.</p><p>CONCLUSION</p><p>This project gave me an opportunity to learn practically and put theoretical knowledge into practice, i was able to learn the strength of a project manager practically which is communication and flexibility and to be able to manage all kinds of persons. The project topic was dealt with practically by my data team and we were able to give practical recommendations to global scam and financial fraud, having this in mind i say a big thank you to the data analytics team for successful collaboration with me as their project manager and a big thank you to Vephla University Our able stakeholder for this practical knowledge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b1409281259" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Link between Project Managers and Data Engineers?]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/the-link-between-project-managers-and-data-engineers-66fcd279fbce?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/66fcd279fbce</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Sat, 01 Mar 2025 01:03:44 GMT</pubDate>
            <atom:updated>2025-03-01T12:53:02.493Z</atom:updated>
            <content:encoded><![CDATA[<p>Daniel Olaleye 1st march 2025, Project Manager</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lV0yhv1C9KdnYYdr" /><figcaption>A Data Engineer</figcaption></figure><h3>INTRODUCTION</h3><p>The link between a project manager (PM) and a data engineer is crucial for the successful execution of data-centric projects. Each role has distinct responsibilities that, when effectively coordinated, lead to better project outcomes.</p><p>In today’s data-driven landscape, organizations increasingly rely on data to inform decisions, streamline operations, and gain competitive advantages. As a result, the roles of project managers and data engineers have become vital to the success of data-centric initiatives. Both positions are integral in guiding projects from inception to completion, albeit with distinct responsibilities and focus areas. Understanding the symbiotic relationship between these roles is essential for fostering collaboration that leads to effective project execution.</p><h4>The Importance of Collaboration</h4><p>The intersection between a project manager and a data engineer is crucial to the success of data projects. While the project manager focuses on the macro aspects — planning, stakeholder communication, and risk management — the data engineer concentrates on the micro aspects — technical execution, data quality, and system integration. This collaboration entails a continuous feedback loop where the project manager conveys stakeholder requirements and project goals, while the data engineer provides essential insights on the implications of data architecture, resource needs, and technical constraints. Their unified effort ensures that project objectives are met without compromising the integrity of the data.</p><h3>DEFINING ROLES</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5hDc0DC_H29VWjUw" /><figcaption>Definition of roles of a Project Manager and a Data Engineer</figcaption></figure><p>Project Managers are responsible for overseeing projects from a high-level perspective, ensuring that they are delivered on time, within budget, and according to predetermined scope and quality standards. They act as the bridge between stakeholders, teams, and upper management, facilitating communication and driving project objectives. Project managers employ methodologies such as Agile, Scrum, or Waterfall to carefully plan and execute projects, balancing organizational goals with team capabilities. Data Engineers, on the other hand, are the technical architects behind the data infrastructure that supports analytical and operational processes. Their primary focus is on designing, building, and maintaining the systems that acquire, store, process, and access data. Data engineers possess specialized skills in programming, database management, and data pipeline construction. They handle complex data sets and ensure data integrity, quality, and accessibility so that organizations can leverage data effectively.</p><h4>Here are key aspects of their Roles:</h4><h4>1. Understanding Project Goals and Requirements</h4><ul><li><strong>Project Manager:</strong> Defines the project scope, objectives, and deliverables based on stakeholder needs. The PM communicates these requirements to the data engineer.</li><li><strong>Data Engineer:</strong> Offers insights on the technical feasibility of the project, ensuring that the project requirements align with data architecture and capabilities.</li></ul><h4>2. Resource Planning and Allocation</h4><ul><li><strong>Project Manager:</strong> Evaluates the resource needs for the project, including personnel, tools, and technology. The PM coordinates with upper management to secure these resources.</li><li><strong>Data Engineer:</strong> Provides input on specific tools, technologies, and skills required for data handling, processing, and storage, helping the PM allocate appropriate resources.</li></ul><h4>3. Risk Management</h4><ul><li><strong>Project Manager:</strong> Identifies potential risks related to project timelines, budget, and scope. The PM establishes mitigation strategies and contingency plans.</li><li><strong>Data Engineer:</strong> Highlights technical risks associated with data quality, integration issues, or system limitations, enabling the PM to address these concerns proactively.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NYAUHAAJd649MqCI" /><figcaption>Data Engineer and Project manager Analyzing Risk</figcaption></figure><h4>4. Timeline and Milestone Management</h4><ul><li><strong>Project Manager:</strong> Develops project timelines, sets milestones, and tracks progress against these milestones. The PM ensures that the project stays on schedule.</li><li><strong>Data Engineer:</strong> Provides timelines for specific technical tasks, such as data acquisition, modeling, and testing, assisting the PM in setting realistic milestones.</li></ul><h4>5. Communication and Collaboration</h4><ul><li><strong>Project Manager:</strong> Acts as a liaison between stakeholders and the data engineering team, facilitating communication and ensuring that everyone is informed of project progress and changes.</li><li><strong>Data Engineer:</strong> Regularly communicates technical details, progress updates, and any challenges encountered during the project, fostering transparency.</li></ul><h4>6. Quality Assurance</h4><ul><li><strong>Project Manager:</strong> Monitors the quality of deliverables, ensuring that they meet the defined standards and requirements. The PM may implement feedback loops with stakeholders.</li><li><strong>Data Engineer:</strong> Ensures the integrity, accuracy, and consistency of the data being used, which is vital for the project’s success. The data engineer also conducts thorough testing to validate results.</li></ul><h4>7. Post-Implementation Review</h4><ul><li><strong>Project Manager:</strong> Leads the project retrospective to assess what worked well, what didn’t, and how processes can be improved for future projects.</li><li><strong>Data Engineer:</strong> Provides insights on technical successes and challenges faced during the project, contributing to the overall evaluation and learning process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mM16CP_94aQ-Bu9G" /><figcaption>collaboration between project managers and data engineers</figcaption></figure><h3>Effective collaboration between project managers and data engineers leads to numerous benefits:</h3><ol><li><strong>Clear Communication</strong>: The PM acts as a mediator, ensuring that technical language is translated into business requirements and vice versa. This clarity minimizes misunderstandings and aligns teams toward common goals.</li><li><strong>Faster Iteration and Innovation</strong>: By working in tandem, these roles can respond more swiftly to challenges and opportunities, adopting agile practices that allow for rapid prototyping and iterative development.</li><li><strong>Improved Quality and Compliance</strong>: With the data engineer focusing on data governance and compliance, the project can adhere to industry standards and regulations, reducing risk and enhancing quality.</li><li><strong>Resource Optimization</strong>: The project manager can better allocate resources based on the data engineer’s insights about technical requirements, leading to more efficient use of time and budget.</li><li><strong>Informed Decision-Making</strong>: Collaborative efforts yield better-informed decisions as technical feasibility is considered alongside business strategy, ensuring alignment with organizational goals.</li></ol><h3>Methodologies used by Project Managers while working with a Data Engineer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*SboBNy80pJ8hC2GJ3b1B8w.jpeg" /><figcaption>Project Methodologies</figcaption></figure><p>Project managers working with data engineers often utilize various methodologies to ensure efficient project execution, effective communication, and successful outcomes. These methodologies are tailored to the intricacies of data projects while also borrowing principles from more traditional project management frameworks. Here are some common methodologies used in projects involving data engineers:</p><h4>1. Agile Methodology</h4><ul><li><strong>Overview</strong>: Agile is an iterative project management methodology that emphasizes flexibility, collaboration, and customer feedback. It breaks projects into smaller, manageable increments called sprints, allowing teams to adapt to changing requirements quickly.</li><li><strong>Application with Data Engineers</strong>: Agile practices enable data engineers to build, test, and iterate on data pipelines, tools, and systems in short cycles. Regular stand-ups and sprint reviews facilitate communication between project managers and data engineers, ensuring alignment on priorities and addressing roadblocks promptly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19xYpOJohNBJXFJ1mtdAvQ.jpeg" /></figure><h4>2. Scrum Framework</h4><ul><li><strong>Overview</strong>: Scrum is a subset of Agile, focusing on specific roles (Scrum Master, Product Owner, and Development Team), events (sprints, sprint planning, daily stand-ups, and sprint reviews), and artifacts (product backlog, sprint backlog, and increment).</li><li><strong>Application with Data Engineers</strong>: Scrum’s structured approach helps data engineering teams prioritize tasks related to data architecture, ETL (Extract, Transform, Load) processes, and data quality assurance. The Scrum Master can facilitate team dynamics, while the Product Owner manages stakeholder expectations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*_8x0TS8tGrjRZgREf9Ur7Q.jpeg" /><figcaption>Scrum Methodology</figcaption></figure><h4>3. Kanban Method</h4><ul><li><strong>Overview</strong>: Kanban is a visual project management method emphasizing continuous delivery without overloading team members. It uses a Kanban board to visualize workflow, track progress, and manage tasks.</li><li><strong>Application with Data Engineers</strong>: Data engineering tasks, such as data collection, processing, and reporting, can be tracked on a Kanban board. This helps project managers and data engineers visualize workloads, identify bottlenecks, and optimize processes for efficiency.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*x6-MG-1L53d37QSO9sdJxQ.jpeg" /><figcaption>Kanban Methodology</figcaption></figure><h4>4. Waterfall Methodology</h4><ul><li><strong>Overview</strong>: Waterfall is a sequential project management approach where each phase must be completed before moving on to the next. It’s more rigid compared to Agile methodologies, making it suitable for projects with well-defined requirements.</li><li><strong>Application with Data Engineers</strong>: Waterfall can apply to data engineering projects where requirements are clear from the start, such as building a data warehouse. The phases — requirements gathering, design, implementation, verification, and maintenance — can be systematically followed, ensuring comprehensive documentation and planning.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ixoU8dJnuOZu_3Zqc7OHDg.jpeg" /><figcaption>Waterfall Methodology</figcaption></figure><h4>5. Lean Methodology</h4><ul><li><strong>Overview</strong>: Lean focuses on maximizing value by minimizing waste, emphasizing efficiency and continuous improvement. This methodology promotes a culture of optimizing resources and processes.</li><li><strong>Application with Data Engineers</strong>: Lean principles can guide data engineers in streamlining data pipelines, reducing redundancy, and improving data access speeds. Project managers can implement Lean practices to enhance team productivity and cost-effectiveness.</li></ul><h3>Challenges face by project managers in collaboration with Data Engineers</h3><p>Project managers face several challenges when working with data engineers, arising from the complexity of data projects, the technical nature of data engineering, and the need for effective collaboration across teams. Here are some common challenges:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XI0RWtaWMK_IvWMl" /><figcaption>Collaboration Between Project Manager and Data Engineer</figcaption></figure><h4>1. Communication Barriers</h4><ul><li><strong>Technical Language</strong>: Data engineers often use technical jargon that may be unfamiliar to non-technical team members, making clear communication challenging.</li><li><strong>Understanding Requirements</strong>: Project managers may struggle to define and communicate the project requirements effectively to data engineers, which can lead to misaligned expectations.</li></ul><h4>2. Rapidly Changing Technology Landscape</h4><ul><li><strong>Keeping Up with Trends</strong>: The data engineering field is constantly evolving, with new tools, technologies, and best practices emerging frequently. Project managers may find it difficult to keep up with these changes.</li><li><strong>Tool Selection</strong>: Choosing the right tools and technologies for the project can be daunting due to the vast array of options available.</li></ul><h4>3. Data Quality and Integrity Issues</h4><ul><li><strong>Data Sources</strong>: Data engineers often need to work with multiple data sources that may have varying levels of quality and consistency, complicating data integration efforts.</li><li><strong>Quality Assurance</strong>: Ensuring that the data being processed and analyzed is clean, accurate, and reliable can be a major challenge, as poor-quality data can lead to misleading insights.</li></ul><h4>4. Resource Allocation and Team Dynamics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WxBGCe5S4FA1GXHh" /><figcaption>Resource allocation</figcaption></figure><ul><li><strong>Limited Resources</strong>: Data engineering projects may compete for limited resources, leading to difficulties in task prioritization and allocation.</li><li><strong>Interdisciplinary Collaboration</strong>: Data engineers often need to collaborate with data scientists, analysts, and other stakeholders. Ensuring smooth collaboration can be challenging, especially when team members have different goals and priorities.</li></ul><h4>5. Project Scope and Planning</h4><ul><li><strong>Undefined Scope</strong>: Data projects can often start with vague objectives, leading to scope creep and challenges in project management as requirements evolve.</li><li><strong>Estimation Difficulties</strong>: Estimating the time and effort required for data engineering tasks can be challenging, given the complexity of data workflows and the potential for unexpected issues.</li></ul><h4>6. Data Security and Compliance</h4><ul><li><strong>Regulatory Compliance</strong>: Ensuring that data handling meets legal and regulatory requirements (such as GDPR, HIPAA, etc.) can complicate project execution.</li><li><strong>Security Measures</strong>: Implementing data security measures is crucial but can slow down project timelines and create additional layers of complexity.</li></ul><h4>7. Performance and Scalability</h4><ul><li><strong>System Limitations</strong>: Ensuring that data systems can handle the required load and scale efficiently can be a significant challenge, especially for projects that anticipate high data growth.</li><li><strong>Performance Bottlenecks</strong>: Identifying and resolving performance bottlenecks in data pipelines can require extensive troubleshooting and technical expertise.</li></ul><h4>8. Change Management</h4><ul><li><strong>Resistance to Change</strong>: Implementing new data processes or technologies may face resistance from the team or broader organization, making it difficult to achieve buy-in.</li><li><strong>Training Needs</strong>: Adequately training team members on new tools or processes is essential, but finding the time and resources to do so can be challenging.</li></ul><h4>9. Meeting Business Expectations</h4><ul><li><strong>Aligning with Business Goals</strong>: Ensuring that data engineering efforts align with broader business objectives can be challenging, especially in a fast-paced environment.</li><li><strong>Delivering Timely Insights</strong>: Project managers may face pressure to deliver timely insights from data projects while managing the complexities of data processing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0lRFFlrmNttjR-CGHtVUw.jpeg" /><figcaption>Real life strategies and examples of successful project</figcaption></figure><h4>In real-life scenarios, successful project managers often employ various strategies to work effectively with data engineers. Here are some examples that illustrate these strategies:</h4><h4>1. Regular Stand-Up Meetings</h4><ul><li><strong>Example</strong>: In a company developing a new data analytics platform, the project manager facilitated daily stand-up meetings with data engineers and other stakeholders. These brief meetings allowed team members to share progress updates, discuss roadblocks, and adjust priorities in real-time, fostering better communication and collaboration.</li></ul><h4>2. Clear Documentation</h4><ul><li><strong>Example</strong>: A project manager led an initiative at a healthcare organization to document all data pipeline processes and data sources meticulously. This included creating flowcharts and detailed descriptions of data transformations. This documentation served as a reference point for both data engineers and stakeholders, reducing misunderstandings about the data workflow and expectations.</li></ul><h4>3. Agile Methodologies</h4><ul><li><strong>Example</strong>: In a tech startup, the project manager implemented Agile methodologies to manage the data engineering team’s work. The project was divided into sprints, with clear goals set for each iteration. This approach allowed the team to adapt quickly to changes and continuously deliver incremental improvements, keeping the project aligned with business objectives.</li></ul><h4>4. Cross-Functional Workshops</h4><ul><li><strong>Example</strong>: At a financial services firm, the project manager organized cross-functional workshops involving data engineers, data scientists, and business analysts. These workshops allowed different teams to align their objectives, share insights, and collaboratively solve problems, leading to a more integrated approach to data projects.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eUbqQLwLCVKo45eGT_UNIA.jpeg" /><figcaption>setting loops</figcaption></figure><h4>5. Loops</h4><ul><li><strong>Example</strong>: A project manager at a retail company established regular feedback loops with data engineers to assess the functionality of data pipelines. After each release, they conducted reviews with the end-users to gather feedback on data accuracy and usability. This real-time feedback helped the data engineers make necessary adjustments quickly.</li></ul><h4>6. Training and Upskilling</h4><ul><li><strong>Example</strong>: In a large corporation facing difficulties with data literacy, the project manager coordinated training sessions for both data engineers and stakeholders. They brought in external trainers to cover topics on data management tools and basic data concepts, ensuring all team members had a foundational understanding, which improved collaboration and efficiency.</li></ul><h4>7. Establishing a Data Governance Framework</h4><ul><li><strong>Example</strong>: A project manager in a telecommunications company implemented a robust data governance framework. They worked with data engineers to define data standards, ownership, and stewardship policies. This strategy helped to improve data quality and integrity, ensuring that all team members adhered to best practices.</li></ul><h4>8. Setting Up a Shared Project Management Tool</h4><ul><li><strong>Example</strong>: At a marketing analytics firm, the project manager introduced a project management tool like JIRA or Trello. This tool was used to track tasks, progress, and dependencies between data engineers and other departments. Visibility into project status enhanced accountability and coordination among team members.</li></ul><h4>9. Aligning Data Projects with Business Goals</h4><ul><li><strong>Example</strong>: A project manager at a non-profit organization successfully aligned a data cleaning project with strategic goals by directly collaborating with leadership. By clearly linking the data insights to fundraising efforts and outcomes, they ensured that data engineers understood the importance of their work, increasing motivation and focus.</li></ul><h4>10. Managing Stakeholder Expectations</h4><ul><li><strong>Example</strong>: In a software development company, the project manager held monthly stakeholder meetings to provide updates and manage expectations. By clearly communicating project timelines, potential risks, and accomplishments, they ensured stakeholders were informed and engaged, reducing pressure on data engineers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jd2jDxFrkBCsZIvGg-MbSA.jpeg" /><figcaption>Stakeholders deliberating</figcaption></figure><h3>Conclusion</h3><p>In summary, the partnership between project managers and data engineers is a cornerstone of successful data-centric projects. By leveraging their unique strengths and maintaining open lines of communication, they can tackle complex challenges, drive innovation, and ensure that data initiatives deliver value to the organization. As the demand for data-driven insights grows, so too will the importance of this collaboration in navigating the intricacies of modern project landscapes. Ultimately, the success of data initiatives hinges on recognizing the interdependencies between these vital roles and fostering a culture of collaboration and shared accountability.</p><p>Project managers and data engineers can leverage a variety of methodologies to enhance collaboration, streamline processes, and deliver successful data projects. The choice of methodology often depends on project requirements, team dynamics, and organizational culture. By adopting the appropriate methodology, project managers can effectively guide data engineers, ensuring that data initiatives align with business goals and provide valuable insights for strategic decision-making.</p><p>Project managers must navigate various challenges when working with data engineers to ensure that data projects are successful and deliver value to the organization. By recognizing these challenges and employing effective strategies, such as fostering communication, investing in training, and adopting suitable methodologies, project managers can enhance collaboration and drive successful outcomes in data engineering initiatives</p><p>These real-life examples illustrate the value of various strategies employed by project managers in collaboration with data engineers. Effective communication, structured methodologies, and a focus on alignment with business goals are crucial for overcoming challenges and achieving successful data projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66fcd279fbce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Nexus between Project Managers and Product Designers?]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/the-nexus-between-project-managers-and-product-designers-18f0453d3529?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/18f0453d3529</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Wed, 26 Feb 2025 19:43:43 GMT</pubDate>
            <atom:updated>2025-02-26T19:43:43.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ngDYT6C5hXlMtepz" /><figcaption><strong>A PRODUCT DESIGNER WORKING</strong></figcaption></figure><h3>INTRODUCTION</h3><p>In todays fast paced business landscape, delivering successful product and projects requires a harmonious partnership between the project manager and the product designer. While both roles share a common goal of driving the business success, they approach this objective from different angles, leveraging their unique skill sets and expertise.</p><p>in some cases the project manager cooperates closely with the designer from the moment they both receive a client’s brief with the requested product’s description. They meet the client to discuss the expectations in detail, clarify any doubts, and establish the next steps in the process. The project manager accompanies the designer when they explain to the client for the first time what wireframes are and why creating them is a crucial step in the website development. When the plan is in place and expectations defined, the creative work starts. The client receives the wireframes of his product once they’re ready and can discuss them with our team to pin down the functionalities and decide on interface elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YJoehEPk96Wvaaih" /><figcaption><strong>PROJECT MANAGER WORKING WITH PRODUCT DESIGNER</strong></figcaption></figure><h3><strong>The project manager’s role in the design stage</strong></h3><p>Within the project team, the roles are clearly defined by the project manager. The project manager gets designer working on UX developers responsible for the front and back-end. All of them are like perfectly fitting pieces of the puzzle. Their duties don’t usually overlap. For example, it would be a waste of time for the designer to spend hours on administrative issues or for the developer to coordinate every team member’s work. There must be a person who looks at the big picture and oversees the workflow — that’s the project manager. His tasks are crucial to the project’s success, so if you look for a company to create your website, always turn to one that hires people for that role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KKV19CKVhtAIVp7g" /><figcaption><strong>PROJECT MANAGER GIVING INDIVIDUALS TASKS TO BE CARRIED OUT</strong></figcaption></figure><h3><strong>What does a project manager do?</strong></h3><p>Project manager needs to be highly organized, resilient, and communicative. They coordinate the work of an internal team and manage clients’ expectations at the same time. Their duties include, for example:</p><ul><li>Prioritizing and monitoring project tasks</li><li>Tracking time spent on the project</li><li>Troubleshooting</li><li>Reporting on progress</li><li>Maintaining the documentation</li><li>Staying in touch with clients and making sure their expectations are met</li></ul><p>And that’s not all, of course. But this short list already shows how complex and demanding this role is (albeit also super exciting and fun). The project manager’s role in the design process</p><p>We believe it’s very important for the project manager to be actively involved in your website’s or application’s design. Of course, the client’s business needs and, consequently, requested products differ, and so do the projects. However, in most cases, the designer-PM cooperation looks similar.</p><p>The person coordinating the team’s work cooperates with the designer and the client simultaneously. While they are ready to answer customers’ questions regarding the wireframes, they also discuss internally with the designers the best approach to take to ensure that the client’s business needs and style preferences are met and his concept is understood correctly.</p><p>If the presented wireframes are approved, the design of the main page starts. (That’s usually the case; however, as we mentioned, the projects differ, and occasionally another page may be created first.) This main page is showcased to the client, who then has a chance to provide his feedback. We involve clients early on so that we can correct the course of action without delaying the work, if needed.</p><p>Here, the designer and PM work together in tandem and not only provide answers and clarify doubts, but also use their experience and skills to explain or suggest the most suited solutions. We want to ensure the client’s success by providing the best possible product, so the project team takes a proactive approach and proposes ideas that could improve the final outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o8_tsZNnKD9JRf6c" /><figcaption><strong>PRODUCT DESIGNER EXPLAINING TO THE TEAM</strong></figcaption></figure><p>Comments are taken into account, and the agreed changes are implemented. Then, the time comes to establish the work order and next steps in the project. If needed, after the whole website is designed and presented, the second iteration of the client’s corrections can occur.</p><p>Such a level of project manager’s engagement in the design phase is not a rule in the digital world. However, we believe that a person holding this role should be present to build a bridge between the client and the designer, facilitate communication, and ensure that expectations are met and the best solutions are delivered.</p><h3>What are Project Management Methodologies?</h3><p>As a project manager, you know you have many different ways to deliver your projects. Generally speaking, project managers can use different project management methodologies. Each uses different project management frameworks, principles, themes, standards, and processes. Ultimately, the project management methodologies comparison may help you choose the right method, which depends on each project, client, and team. With project management methods such as Agile, Waterfall, Lean UX, and thinking design. Organizations can tailor their project execution strategy to meet specific goals, adhere to timelines, and manage resources effectively, aligning with the unique demands and constraints of each project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xbj4BnwUm2c_d08X" /><figcaption><strong>PROJECT MANAGER ANALYSING A SUITABLE METHODOLOGY FOR THE PROJECT</strong></figcaption></figure><h3>Project Management Methodologies:</h3><p>When comparing project management methodologies, it’s essential to consider their core principles and ideal applications.</p><ul><li><strong>Agile</strong>, for instance, is adaptive, prioritizing customer feedback and iterative progress. It’s suitable for projects requiring flexibility and rapid changes.</li><li><strong>Waterfall</strong>, in contrast, is sequential, emphasizing meticulous planning and execution linearly, making it ideal for projects with well-defined stages and predictable outcomes.</li><li>Lean UX is a collaborative, iterative way of designing and building products. It goes hand-in-hand with the agile methodology, which originated in the software industry.</li><li>Design thinking is a process for creative problem-solving that helps teams move past the first “good ideas” and discover creative solutions</li></ul><h3>Project Management Methodologies</h3><p>They include Waterfall, Agile, Lean UX, Thinking design. If you are aware of what is project management, let us discuss these project management methods in detail, along with the advantages, disadvantages, and appropriate project management methodologies examples:</p><h3>1. Waterfall Project Management Methodology</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SrhJWTWfGvpPljvv" /><figcaption><strong>WATERFALL METHODOLOGY</strong></figcaption></figure><p>The Waterfall methodology, also known as linear project management methodology is a more traditional approach and it tends to be mostly used in the construction and manufacturing industries. According to this project management methodology, the project needs to be broken down into sequences that are all dependent. This means that the second phase will only start when the first one is completed. The Waterfall Methodology includes 5 different stages: idea engineering, system design, implementation, testing and validation, and maintenance. In some cases, where project managers need to get benefit from waterfall methodology along with other methodologies, a hybrid model is used. Agile Waterfall Hybrid methodology is one of the examples.</p><h4>Advantages of Waterfall Project Management Framework</h4><ul><li><strong>Clear Structure:</strong> The Waterfall project management framework provides a clear, linear structure, making it simple to understand.</li><li><strong>Well-defined Documentation:</strong> Due to its systematic approach, each phase of the Waterfall model generates its own set of documentation.</li></ul><h4>Disadvantages of Waterfall Project Management Framework</h4><ul><li><strong>Inflexibility to Change:</strong> Once a phase is completed, it is challenging to go back and make changes.</li><li><strong>Late Problem Discovery:</strong> Problems or mistakes in requirements may not be discovered until the testing phase.</li></ul><h3>2. Agile Project Management Methodology</h3><p>The Agile Project Management framework is another famous project management method that also transforms the entire project into small cycles or phases. One of the main benefits of using Agile is that it is quite flexible. This way, it is perfect when you need to continuously adapt to changes according to the client’s feedback. The Agile project management methodology should be used in projects that require frequent interaction.</p><h4>Advantages of Agile Project Management Framework</h4><ul><li><strong>Flexibility &amp; Adaptability:</strong> Agile offers the ability to adapt to changes quickly and efficiently.</li><li><strong>Customer Satisfaction:</strong> Continuous integration of customer feedback ensures the final product is more closely aligned with customer needs.</li></ul><h4>Disadvantages of Agile Project Management Framework</h4><ul><li><strong>Less Predictability:</strong> The flexible nature of Agile can lead to less predictability in terms of project cost and timeline.</li><li><strong>Requires High Customer Engagement:</strong> The success of Agile often depends on the active participation of the customer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19xYpOJohNBJXFJ1mtdAvQ.jpeg" /><figcaption><strong>AGILE METHODOLOGY</strong></figcaption></figure><h3>· <strong>lean UX Methodology</strong></h3><p>Lean UX is a collaborative, iterative way of designing and building products. It goes hand-in-hand with the agile methodology, which originated in the software industry. The agile methodology breaks a project up into short, rapid cycles in order to get things done quickly, with continuous testing and improvements along the way. Lean UX follows a similar approach, working in a constant loop of thinking, making, and testing.</p><p>The purpose of lean UX is to harness the power of collaboration, to reduce waste (in terms of time, effort and resources), and to experiment and build rapidly in order to get feedback early on. With this feedback, the product can be improved incrementally.</p><h3>· Design Thinking Process</h3><p>Design thinking is a process for creative problem-solving that helps teams move past the first “good ideas” and discover creative solutions. View where uncertainty and ambiguity are welcomed and embraced to consider all sides of a problem. A design mindset can be applied to any life situation, and it aids in developing innovative ideas by considering the bigger picture and allowing that to shape our decisions as we move forward.</p><p>The method is steeped in a deep belief that the end-user should be at the heart of all decision-making. The benefit of design thinking is that, through empathy for your customer, consumer, or client, you are able to create products and experiences that truly help people.</p><figure><img alt="THINKING PROCESS" src="https://cdn-images-1.medium.com/max/1024/0*DqSR2ro4uSoup2qP" /><figcaption><strong>DESIGN THINKING PROCESS</strong></figcaption></figure><h3>3 core product design challenges and solutions</h3><p>While product development and design is an ever-evolving process, there are still several challenges that could prevent product designers from reaching their product goals.</p><p>Let’s take a look at what these challenges involve and how you can overcome them — so you can validate your product design and meet user needs, fast.</p><p>1. Research challenges</p><p>2. Design process challenges</p><p>3. Post-launch iteration challenges</p><h3>1. Research challenges</h3><p>Given all the user data, channels, and tools out there, conducting thorough research about your users and translating that research into actionable insights can be daunting for product designers and teams.</p><p>Before you start, you need to have a research process in place to help you achieve product-market fit and user success.</p><h4>4 steps to overcome research challenges and improve your research process</h4><p>1. Identify your ideal customer profile (ICP) based on their pain points, characteristics, purchasing behaviors, and demographics. Use it to determine their most-used channels and product preferences.</p><p>2. Use social listening tools like Hootsuite or Brand watch to observe mentions of your brand or product on channels relevant to your target audience, so you know what they’re talking about and what they need. For example, if you see people on social media responding positively to a competitor’s product feature, you can think about incorporating a similar feature.</p><p>3. Predict market demand with tools like Think with Google and see popular trends in product searches and their likelihood of success. Then, look at competitor reviews on websites like G2, Capterra, Trustradius, and Google.</p><p>4. Ask for feedback: poll your target audience about potential product ideas or features using polls on Instagram Stories or LinkedIn. Or, use unobtrusive feedback widgets and place them throughout critical touch points in the customer journey for key insights into product ideations and improvements.</p><p>For example, after placing a feedback widget on your homepage, you might discover that new visitors don’t understand what your product does or the problems it solves. This way, you can take steps to showcase your product’s features directly on your homepage to get users to understand your product’s value, quicker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZFs3-414fsIczl9H" /><figcaption><strong>GET FEEDBACKS</strong></figcaption></figure><h3>2. Design process challenges</h3><p>Crafting a solid design process involves cross-functional collaboration, prioritizing your product roadmap, and leaving enough room for testing and tweaking. But, it can be hard to find (and stick to) a process that isn’t too complicated or costly. And you don’t want to risk a delay in rollout because your process was too lengthy.</p><h4>4 ways to overcome design challenges</h4><p>1. Encourage cross-functional collaboration and stakeholder alignment by uniting teams on your main platforms. Make sure you’re using the same CRM, reporting tools, and dashboard, for easy access to customer insights. Integrating your tools with Slack can also help keep customer insights readily accessible to your teams and keep everyone up to speed on where your product’s headed.</p><p>2. Survey your team and users to better understand what you could streamline in your design and development process. Administer anonymous surveys to your product team for fresh ideas on how to improve your process, or survey your target market for early-stage product screening insights.</p><p>3. Iterate your product design testing methods: implement the feedback you’ve collected into your design process and explore tried-and-tested project management methods like Kanban or Scrum.</p><p>4. A/B tests your prototype and sees what your audience responds to or likes better. Then, use your findings to improve and streamline your product design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1brwWFA0couPxwOm" /><figcaption><strong>TEAM SOLVING AN ISSUE</strong></figcaption></figure><h3>3. Post-launch iteration challenges</h3><p>Once you’ve launched your product, you’ll need to keep a close eye on customer insights that will help you refine your product down the line. Sometimes, product designers forget that post-launch product iteration is as important as early development and design.</p><h4>4 ways to make sure you’re continuously refining and improving your product</h4><p>1. Administer customer satisfaction (CSAT) surveys to gauge your customers’ short-term satisfaction with your product. For example, after receiving a low CSAT score during a new product rollout, ask customers to provide a reason for their score to get direct insights into their experience.</p><p>2. Watch user sessions within your product for a firsthand view of the user experience to see exactly what blocks your customers in their journey or what keeps them exploring.</p><p>3. Ask for feedback throughout the customer journey, including during user onboarding, to get insights into what customers like or dislike about your product, and optimize accordingly.</p><p>4. Conduct product-market fit surveys and ask your customers if they’ve adopted your product into their everyday lives, or if they’d miss using it. Use your findings to better tailor your product to market and user needs. For example, after administering a product-market fit survey about your product, you might get a clearer understanding of the product roadmap and better prioritize high-value initiatives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DFiGNaujsP3Krmue" /><figcaption><strong>TEAM MEMBERS DOING A MARKET SURVEY</strong></figcaption></figure><h3><strong>Successful project management strategies in product design</strong></h3><p>· Establishing Clear Communication and Collaboration</p><p>· Setting Realistic Timelines and Milestones</p><p>· Identifying and Managing Risks</p><p>· Utilizing Resources Efficiently</p><p>· Monitoring and Evaluating Progress</p><p>· Adapting and Problem-solving as needed</p><p>When embarking on any design project, the first step is to gain a comprehensive understanding of the project scope and objectives. This foundational phase is crucial as it sets the stage for all subsequent activities. By clearly defining what the project aims to achieve, teams can align their efforts and resources effectively.</p><p>This involves not only identifying the end goals but also understanding the specific requirements and constraints that may impact the design process. Engaging stakeholders early on is essential; their insights can provide valuable context and help clarify expectations. By fostering an environment where everyone feels comfortable sharing their thoughts, teams can collaboratively outline a vision that resonates with all parties involved.</p><p>Moreover, breaking down the project into manageable components can significantly enhance clarity. This approach allows teams to focus on individual elements while keeping the bigger picture in mind. Utilizing tools like Claritee can streamline this process, enabling teams to visualize their ideas and objectives quickly.</p><p>With its intuitive interface and drag-and-drop features, Claritee empowers users to create a clear roadmap for their design journey. By leveraging pre-built templates and AI-powered technology, teams can ensure that their project scope is not only well-defined but also adaptable to changes as they arise. This initial understanding of the project scope and objectives lays a solid foundation for collaboration and innovation throughout the design process.</p><figure><img alt="Having a clear view of the project" src="https://cdn-images-1.medium.com/max/1024/0*8PQpaO0QBsRFlZYx" /><figcaption><strong>FOCUS ON THE GOAL OF THE PROJECT</strong></figcaption></figure><h3>Key Takeaways</h3><ul><li>Understanding the project scope and objectives is crucial for setting the right direction and goals.</li><li>Establishing clear communication and collaboration ensures that everyone is on the same page and working towards the same objectives.</li><li>Setting realistic timelines and milestones help in managing expectations and tracking progress effectively.</li><li>Identifying and managing risks proactively can help in minimizing potential disruptions to the project.</li><li>Utilizing resources efficiently is essential for maximizing productivity and achieving the project goals within the set constraints.</li><li>Monitoring and evaluating progress regularly allows for timely adjustments and ensures that the project stays on track.</li><li>Adapting and problem-solving as needed is important for overcoming unexpected challenges and ensuring successful project completion.</li></ul><h3>Establishing Clear Communication and Collaboration</h3><p>Effective communication is the lifeblood of any successful design project. Establishing clear channels for dialogue among team members fosters a collaborative atmosphere where ideas can flourish. Regular check-ins, brainstorming sessions, and feedback loops are essential components of this communication strategy.</p><p>By encouraging open discussions, teams can address concerns, share insights, and build upon each other’s strengths. This collaborative spirit not only enhances creativity but also ensures that everyone is on the same page regarding project goals and expectations. Utilizing tools like Claritee can further facilitate this process by providing a centralized platform for sharing design ideas and updates, making it easier for team members to stay informed and engaged.</p><p>Collaboration goes beyond just communication; it involves creating an inclusive environment where every team member feels valued and empowered to contribute. Encouraging diverse perspectives can lead to innovative solutions that might not have emerged in a more homogeneous setting. Claritee’s user-friendly interface allows individuals of varying skill levels to participate actively in the design process, breaking down barriers that often hinder collaboration.</p><p>By integrating feedback seamlessly into the design iterations, teams can refine their ideas collectively, ensuring that the final product reflects a shared vision. This emphasis on collaboration not only enhances productivity but also cultivates a sense of ownership among team members, ultimately leading to a more successful outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TPNQ2pX3JoBt_Kv2" /><figcaption><strong>TEAM MEMBERS HAVING OPEN DISCUSSION</strong></figcaption></figure><h3>· Setting Realistic Timelines and Milestones</h3><p>Once the project scope is defined and communication channels are established, it’s time to set realistic timelines and milestones. This step is critical in ensuring that the project progresses smoothly and stays on track. By breaking the project into phases with specific deadlines, teams can create a structured approach that allows for regular assessment of progress.</p><p>It’s important to consider the complexity of tasks and the availability of resources when establishing these timelines. Engaging the entire team in this process can provide valuable insights into what is feasible, fostering a sense of collective responsibility for meeting deadlines. Incorporating milestones into the timeline serves as a motivational tool for teams, providing opportunities to celebrate achievements along the way.</p><p>These checkpoints not only help maintain momentum but also allow for reflection on what has been accomplished thus far. With Claritee’s rapid prototyping capabilities, teams can quickly create MVPs (Minimal Viable Prototypes) that serve as tangible representations of progress. This visual feedback can be incredibly motivating, as it allows team members to see their ideas come to life in real-time.</p><p>By setting realistic timelines and celebrating milestones, teams can cultivate a positive atmosphere that encourages continued innovation and collaboration throughout the design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WUGUZv4iEWiyjGFh" /><figcaption><strong>SETTING REALISTIC TIMELINES</strong></figcaption></figure><h3>· Identifying and Managing Risks</h3><p>Every design project comes with its own set of risks, and identifying these potential challenges early on is essential for successful management. By conducting a thorough risk assessment, teams can pinpoint areas that may pose obstacles to progress. This proactive approach allows for the development of strategies to mitigate risks before they escalate into significant issues.</p><p>Engaging in open discussions about potential challenges fosters a culture of transparency, where team members feel empowered to voice concerns without fear of judgment. This collaborative effort not only strengthens team dynamics but also enhances problem-solving capabilities. Once risks have been identified, it’s crucial to implement effective management strategies.</p><p>This may involve creating contingency plans or reallocating resources to address specific challenges as they arise. Claritee’s intuitive interface allows teams to visualize potential risks alongside their design ideas, making it easier to assess how these factors may impact overall progress. By integrating risk management into the design process, teams can remain agile and responsive to changes, ensuring that they stay focused on their objectives while navigating any obstacles that may come their way.</p><h3>· Utilizing Resources Efficiently</h3><p>Efficient resource utilization is key to maximizing productivity in any design project. This involves not only managing time effectively but also leveraging tools and technologies that enhance collaboration and streamline workflows. Claritee stands out as an invaluable resource in this regard, offering features that simplify the design planning process.</p><p>With its drag-and-drop functionality and pre-built templates, teams can quickly create prototypes without getting bogged down in technical details. This efficiency allows designers to focus on creativity rather than administrative tasks, ultimately leading to more innovative outcomes. In addition to utilizing design tools effectively, it’s important for teams to assess their human resources as well.</p><p>Understanding each team member’s strengths and weaknesses enables leaders to assign tasks strategically, ensuring that everyone is working in areas where they can excel. Encouraging cross-functional collaboration can also lead to more efficient use of resources, as team members bring diverse skills and perspectives to the table. By fostering an environment where collaboration thrives, teams can tap into each member’s unique talents, resulting in a more cohesive and productive design process.</p><h3>· Monitoring and Evaluating Progress</h3><p>Monitoring and evaluating progress throughout the design process is essential for ensuring that projects remain aligned with their objectives. Regular check-ins allow teams to assess whether they are on track to meet their milestones while providing opportunities for reflection on what has been learned thus far. Utilizing tools like Claritee can facilitate this evaluation process by offering visual representations of progress through prototypes and design iterations.</p><p>This visual feedback not only helps teams identify areas for improvement but also reinforces a sense of accomplishment as they see their ideas evolve over time. In addition to tracking progress against established timelines, it’s important for teams to remain open to feedback from stakeholders and users alike. Gathering input from various sources can provide valuable insights that inform design decisions and enhance overall quality.</p><p>By integrating this feedback into ongoing iterations, teams can ensure that their final product meets user needs effectively. This commitment to continuous improvement fosters a culture of innovation where every team member feels empowered to contribute ideas and suggestions, ultimately leading to a more successful outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EjmBMWTO4bvJqWa3" /><figcaption><strong>MONITORING AND EVALUATING PROGRESS</strong></figcaption></figure><h3>· Adapting and Problem-solving as Needed</h3><p>In any design project, adaptability is key to navigating unforeseen challenges and changes in direction. The ability to pivot when necessary allows teams to respond effectively to new information or shifting priorities without losing sight of their overall objectives. Encouraging a mindset of flexibility within the team fosters resilience and empowers individuals to embrace change as an opportunity for growth rather than a setback.</p><p>Utilizing tools like Claritee can support this adaptability by enabling rapid prototyping and iteration, allowing teams to explore new ideas quickly without extensive rework. Problem-solving is an integral part of this adaptive approach; when challenges arise, it’s essential for teams to come together collaboratively to brainstorm solutions. Creating an environment where team members feel comfortable sharing their thoughts fosters creativity and innovation in addressing obstacles.</p><p>By leveraging diverse perspectives, teams can develop comprehensive solutions that may not have been considered otherwise. Claritee’s user-friendly interface facilitates this collaborative problem-solving process by providing a platform for visualizing ideas and integrating feedback seamlessly. Ultimately, embracing adaptability and problem-solving as core principles empowers teams to navigate the complexities of design projects with confidence and creativity, leading to successful outcomes that reflect their collective vision.</p><h3>Conclusion</h3><p>The project manager works closely with the product designers, communicating the mind of the stakeholders at every stage of the process. The project manager uses any of the methodology based on the goals, scope and budget of the project. and he also ensure effective communication through out the process of the the project in order to avoid internal scope creeps in the process of the project. The project manager also escalate with the stakeholders to get every bit of the information and the expected outcome of the project this will help the PM to work against external scope creeps.</p><p>The project manager works effectively with the product designer having the stakeholders desired outcome in mind, and considering the need of the targeted market and also put into consideration the trending designs that are moving in the market. The PM makes problem solving strategies against road blocks that may arise during the project.</p><h3>References</h3><p>Develtio,(2025). The project manager’s role in the design stage. Develtio. <a href="https://develtio.com/blog/knowledge/the-project-managers-role-in-the-design-stage/">https://develtio.com/blog/knowledge/the-project-managers-role-in-the-design-stage/</a></p><p>Bruton, L. (2022, June 13). What is lean UX? UX Design Institute. <a href="https://www.uxdesigninstitute.com/blog/what-is-lean-ux/">https://www.uxdesigninstitute.com/blog/what-is-lean-ux/</a></p><p>Hotjar Ltd. (2014–2025). Product design. <a href="https://www.hotjar.com/product-design/">https://www.hotjar.com/product-design/</a></p><p>Claritee. (2024, October 30). Effective design project management strategies for success. <a href="https://claritee.io/blog/effective-design-project-management-strategies-for-success/">https://claritee.io/blog/effective-design-project-management-strategies-for-success/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18f0453d3529" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do Project Managers Work with Backend Engineers?]]></title>
            <link>https://medium.com/@danielolaleyebgmail.com/how-do-project-managers-work-with-backend-engineers-f9d36daecf02?source=rss-7959b600224a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9d36daecf02</guid>
            <dc:creator><![CDATA[Daniel Bayo Olaleye]]></dc:creator>
            <pubDate>Wed, 26 Feb 2025 19:42:09 GMT</pubDate>
            <atom:updated>2025-02-26T19:42:09.737Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RofXyd2rtbQJ86Nf" /><figcaption>Backend Engineer</figcaption></figure><h4>INTRODUCTION</h4><p>Back-end web development is the process of creating the logic, functionality, and data management of a web application. It involves programming languages, frameworks, databases, APIs, and servers. As a back-end web developer, you need to manage complex and dynamic projects that require collaboration, communication, and efficiency. The role of Project Manager is pushing for results, withstanding pressure from stakeholders, translating requirements to engineers, and affecting the project’s success by executing their responsibilities.</p><p>It’s all about using a specific set of tools, knowledge, and techniques to control the execution of IT projects. The main goal of all these activities is to gain successful results and value via the development of a technology-powered software product. The process involves a lot of specialists, including PMs, software engineers and architects, quality assurance engineers, designers, analysts, and many more. Sometimes, teams require the involvement of industry experts who know a lot about the specifics of a given niche.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r19ykfas-rFspY8S" /><figcaption>Team working together</figcaption></figure><p>When highly specialized individuals attempt to work together, there is a high risk of friction if things aren’t managed properly. We all know how frontend developers and designers can sometimes clash, and it’s not uncommon for engineers and software developers to have their fair share of disagreements.</p><p>But today, let’s focus on the potential friction between project managers and backend engineers . It’s a dynamic that requires attention and effective management to keep things running smoothly.</p><p>When you’re building software, the roles of project manager and software developer are equally important for the successful launch of your project. Productivity and output rely on both sides working together to produce the highest quality product for customers. Yet, time and time again, we see a divide between the two personas.</p><p>Poor communication and lack of respect can derail even the most talented teams. It’s vital that your company better understands the relationship between your software developers and project managers so that you can manage it appropriately.</p><p>Let’s examine these two important roles, where problems arise, and how you can bridge the gap between your software developers and project managers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QueYLzsE6Wf00Nau" /><figcaption>Project manager giving clear explanation</figcaption></figure><h4><strong>Roles and Responsibilities: Software Developers and Project Managers</strong></h4><p>Software developers and project managers have very distinct roles and often times there’s a dotted line in the chain of command which can be a root cause of friction. Both are aligned on the output, but most are not aligned on how to get there.</p><p>Project managers are typically given projects by the company and are asked to manage the cost, the resources assigned and the timing of the project. They’re responsible for reporting to stakeholders and providing constant status updates on the project up until launch.</p><p>Software developers, on the other hand, are typically assigned tasks, essentially pieces of the project, by their managers. They’re responsible for reporting on iterations of the project, or what is known as “sprints.”</p><h4><strong>Where the Challenge Originates</strong></h4><p>While part of the cause for friction is the dotted line chain of command, the other contributing factor is the fundamental difference in how each person operates. Many might say the root cause is poor communication but, in truth, it’s the “how” each communicates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ka8yxyw1PGikHguTwwkb0g.jpeg" /><figcaption>Project manager having frictions with backend engineer</figcaption></figure><p>Blaming the lack of collaboration on poor communication is not really a true cause. Everyone has their own communication styles and with so many SaaS tools available to us, workflow habits can change over time.</p><p>Based on conversations with many project managers and developers, I’ve created a short table on likes and dislikes from both:</p><h4><strong>Key Tips to Help Bridge the Gap</strong></h4><p>The opportunity here is figuring out how to adapt to each other’s working styles. This is key when trying to manage a project efficiently and effectively. Because the project manager is ultimately responsible for the project, it takes most effort from the project manager to really step up to the plate and engage their developers.</p><p>So how do they get it done?</p><ol><li>Involve your software development team early on</li></ol><p>Every project has a purpose: to solve a problem. That problem could be anything from boosting market share by releasing a new product, enhancing customer satisfaction through a new feature, or developing integration for a partner agreement. Whatever it may be, the demand for the project stems from a specific need or requirement.</p><p>2. Involving developers in the initial launch of a project can be a game-changer when it comes to problem-solving. When developers are included right from the start, it provides them with valuable context and understanding of why they’re being tasked with developing software within a tight timeline.</p><p>And how do you do it without an in-person meeting or email? If you’re using a tool like Assembla, you can post the project in a ticket and @ mention users that will be involved in the project. Or you can add it to your wiki and send a link to the document to all parties involved (preferably the communication channel your team uses).</p><p>If your team is using Slack, you should create a channel for the project and invite everyone involved. This gives the entire team visibility into the project even when they’re not involved with the everyday conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uWtBVLbVBakse8BL" /><figcaption>Product manager explaining to the backend engineer</figcaption></figure><h4><strong>The role of a Project Manager in software development</strong></h4><p>This is one of the critical roles in the IT industry as he or she orchestrates the entire process from the beginning to the end. A PM takes an active part in negotiating the project with all stakeholders, communicating the requirements to all team members, and organizing and monitoring the process. Depending on the project management methodology, the level of responsibilities may differ. In some cases, a PM is responsible for billing, reporting, and resolving conflicts.</p><ol><li>Understand software development workloads before asking questions</li></ol><p>A common scenario that can cause a rift between the two parties is the lack of understanding some project managers have for the time it might take for a developer to complete a task. I’ve seen this exact scenario pop up over and over in various organizations.</p><p>It happens in the marketing organization with frontend developers, in the product organization with backend developers and everything in between. Programming in a certain language is a very specific skillset and there are different levels of experience.</p><p>2. It’s the role of the project manager to sync up with their software development</p><p>Project manager or most senior developer to understand what levels of experience the developers have, what language they’re coding in, how much time is typically spent on specific tasks and, most importantly, what tools and/or services can a project manager provide to the software development team that would help them work more efficiently and effectively.</p><p>This puts unreasonable pressure on the development team. Yes, a project manager needs to answer to the client or management, but they must also balance these expectations with the reality of the workload. Understanding the development team’s workload clears up a lot of assumptions and better prepares the project manager to address questions from stakeholders.</p><p>3. A project manager shield developers from outside issues.</p><p>While it’s important to involve developers early on and provide them visibility into the project, it’s equally important to shield them from office politics or endless debates over small product changes. Change requests are going to happen, but often times before a change request is approved, there’s a lot of debate between stakeholders and the project managers before coming to a conclusion. Cost and timelines have to be taken into consideration and that can take time to sort through.</p><p>By shielding issues like these, a project manager isn’t just alleviating stress for the developer, they are building trust. If you can trust your manager to filter out unnecessary distractions for you, then you know they have your best interest at heart.</p><p>4. Share the same suite of tools and services</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2RCjaaGZ4-4jEAA-" /><figcaption>tools for software engineers</figcaption></figure><p>If you want to improve communication and work more efficiently, it’s crucial that the entire team on the project uses the same tools and services.</p><p>Slack has become a comfortable place for all personas on a team to work from. At Assembla, we use Slack and have created channels for different teams within our organization. As a project manager, decide on which communication tool everyone should be using so there are no excuses for why teammates are not receiving updates.</p><p>If you’re a software developer, you’re likely working out of a code repository tool like Github — a tool most project managers cringe at. And if you’re a project manager, you’re likely working out of a complex project management tool — tools most software developers typically cringe at. Software developers just want to manage code, and project managers just want to manage tasks. When you’re developing software launches, both are equally important.</p><p>Assembla is a tool that bridges that gap between project managers and software developers with task management and code repositories built in. We also have integrations with both Slack and Github making it much easier for teams to adapt. Imagine merging requests directly in tickets:</p><p>We’ve built <a href="https://get.assembla.com/assembla-cloud-pricing/">Assembla</a> from the ground up to help software development teams work more collaboratively. By bridging the gap between software developers and project managers, products and features will be shipped faster. A company’s success will also improve as the relationship between PMs and developers improve.</p><p><strong>Methodologies used for software development</strong></p><p><strong>1.</strong> <strong>Agile methodology</strong></p><p>The most effective project management strategy for back-end web development is agile methodology. Agile is a flexible and iterative approach that allows you to deliver working software in short cycles called sprints. Agile focuses on customer feedback, team collaboration, and continuous improvement. Agile helps you to adapt to changing requirements, deliver value faster, and improve quality and performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19xYpOJohNBJXFJ1mtdAvQ.jpeg" /></figure><h3>Scrum framework</h3><p>One of the most popular ways to implement agile methodology is using the scrum framework. Scrum is a lightweight and simple framework that defines roles, events, and artifacts for agile teams. Scrum roles include the product owner, who represents the customer and defines the product vision and backlog; the scrum master, who facilitates the scrum process and removes impediments; and the development team, who designs, builds, and tests the product. Scrum events include the sprint planning, where the team plans what to work on in the next sprint; the daily scrum, where the team updates each other on their progress and challenges; the sprint review, where the team demonstrates the product to the customer and collects feedback; and the sprint retrospective, where the team reflects on their performance and identifies improvements. Scrum artifacts include the product backlog, which is a prioritized list of features and requirements; the sprint backlog, which is a subset of the product backlog that the team commits to deliver in the next sprint; and the increment, which is the working software that the team produces in each sprint.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9d36daecf02" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>