0% found this document useful (0 votes)
2 views3 pages

Hackathon

Uploaded by

shovonroy55
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views3 pages

Hackathon

Uploaded by

shovonroy55
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1) Feasibility analysis:

 Mobile-first, offline-capable apps (Progressive Web App + lightweight Android app) are
feasible because smartphone ownership and mobile internet usage among youth in rural
India are high — but expect intermittent connectivity and older devices.

 Schools & clusters already exist (primary/secondary schools in Nabha block). Work
through school heads and the District Education Office for approvals and teacher
involvement. Local language (Punjabi) support and alignment with state curriculum will
be critical.

 Initial pilot can be low-cost using: open-source LMS (Moodle/Adapt learning),


DIKSHA/PM eVIDYA content integration, and low-cost devices or community-learning
kiosks.

 Community acceptance: medium to high if we involve parents and teachers, show early
learning gains, and keep costs low. Gender dynamics and device access at home need
active mitigation (see Risks).

2) Potential challenges & risks (with


mitigation strategies)
1. Limited or unreliable internet / low bandwidth
o Risk: Students can’t stream video; downloads fail.
o Mitigation: Offline-first app with background syncing; small-file formats (audio +
slides, low-res video), microlearning units <10 min; school-level caching server /
local Wi-Fi hotspots; offer printable worksheets; schedule large updates overnight
or via USB shuttle to schools.
2. Insufficient device access (shared devices, older phones)
o Risk: Not every child has a smartphone; device may be shared.
o Mitigation: BYOD + school-device pool (tablets for labs), community learning
centers (one or two low-cost tablets per hamlet), classroom projected lessons
(teacher uses single device + projector), SMS/IVR content for feature-phone
fallback.
3. Teacher resistance / low digital pedagogy
o Risk: Teachers don’t adopt platform; poor integration in class.
o Mitigation: Co-design training modules; short hands-on teacher training (in-
person + video), teacher incentives (certificates, link to appraisal), make teacher
dashboards simple with lesson plans and auto-generated worksheets.
4. Language / cultural relevance
o Risk: Content in English/Hindi only; not engaging.
o Mitigation: Localize all UI & core content into Punjabi; use local examples,
stories, and community voices; involve local teachers in content review.
5. Power / infrastructure issues
o Risk: Power cuts limit device charging and server uptime.
o Mitigation: Solar-powered charging stations for schools/kiosks; low-power
devices and local caching to reduce dependence on constant power.
6. Gender and social barriers
o Risk: Girls may have less access to devices or parental restrictions.
o Mitigation: Community awareness sessions highlighting benefits; girls-only
learning groups; schedule community center hours convenient for girls; partner
with local women’s groups.
7. Funding & sustainability
o Risk: Pilot runs out of funds after initial phase.
o Mitigation: Mix funding sources from day one — apply for Samagra Shiksha /
DIKSHA-aligned grants, approach CSR arms of local industry, offer district-level
licensing, and show measurable outcomes quickly to unlock further funding.
8. Data privacy and child-safety concerns
o Risk: Data misuse or unsafe content.
o Mitigation: Minimal personal data collection, store data on secure servers,
parental consent flows, implement content moderation and age-appropriate filters,
follow Indian data protection guidelines.

5) Concrete strategies & recommended


implementation plan (pilot → scale)
Phase 0 — Planning (0–1 month)

 Stakeholder mapping: District Education Office (Patiala), cluster coordinators, 3–5 pilot
schools in Nabha (mix government & private).
 Define KPIs: usage (DAU/MAU), lesson completion rate, learning gain (pre/post tests),
teacher adoption rate.

Phase 1 — Pilot build (1–3 months)

 Build minimal MVP: offline-capable Android app + PWA, content for classes 3–8 (Math
& Language), Punjabi localization, simple teacher dashboard.
 Integrate existing free NCERT / DIKSHA modules to accelerate content.
 Procure 10–20 low-cost tablets for school kiosks and one local caching device (Raspberry
Pi with Wi-Fi and cached content).

Phase 2 — Pilot roll-out & monitoring (3–6 months)

 Train teachers (2 days) + follow-up coaching.


 Monitor KPIs weekly; run short learning assessments after 3 months.
 Community engagement: parent meetings, student competitions.

Phase 3 — Evaluate & scale (6–12 months)

 Measure learning gains; refine content UX; develop sustainability plan (district licensing,
CSR).
 Expand to adjoining villages/blocks based on results.

You might also like