Student-led software development at Leiden University, delivering scoped MVPs in a structured academic setting (February–June).
Projects are executed by teams of about six students as part of a university course. Outcomes are typically prototypes or early-stage products.
LUdev in brief
LUdev assembles teams of final-year bachelor students (Computer Science, Data Science & AI, Bioinformatics, Informatics & Economics at Leiden University) to execute software projects within a fixed academic semester (February–June). Projects are selected based on feasibility, educational value, and clarity of scope. Each team works in Agile sprints with biweekly check-ins and faculty supervision. Deliverables typically include a functional prototype or MVP, source code, and documentation.
This model differs from commercial development: timelines are fixed, scope must be well defined upfront, and outcomes prioritise learning and feasibility over production guarantees.
A team consists of approximately six students who together dedicate around 500 hours in total to your project. Work follows Agile methodologies and is structured through defined deliverables (see our timeline), through which students iteratively familiarise themselves with your organisation and context, refine requirements, and prioritise development.
The project lasts one academic semester (February–June, 5 months). Students work in biweekly sprints with at least biweekly meetings with the client. Each team is supported by an experienced student mentor, with whom they meet weekly. A midterm evaluation is conducted by faculty and teaching staff. More details can be found in the project timeline.
Teams work largely independently from your internal processes, part-time, and from the university, resulting in minimal integration overhead. LUdev is responsible for supervision and grading, allowing you to focus on product direction and feedback rather than day-to-day management. Additionally, the focus is on delivering a clearly scoped MVP rather than open-ended placement work.
How we work
LUdev offers a straightforward collaboration model that respects your time and delivers concrete outcomes.
Submit a clearly defined project proposal. Projects are evaluated on feasibility within one semester, technical depth, and educational value. The project must involve a substantial software development component; proposals focused primarily on research with little to no code output are not suitable.
A team of approximately six students is assigned based on skill fit and interest. Together, you refine the scope, success criteria, and constraints. LUdev transitions to a supervisory role; day-to-day collaboration takes place directly with the student team.
Development runs from February to June in biweekly sprints. You participate in regular progress meetings and provide timely feedback. The project concludes with the delivery of a prototype or MVP, source code, and agreed-upon documentation.
Client responsibilities
Active involvement is required for a successful project.
Be available (online or in person) for the project kickoff in February.
Participate in biweekly meetings with your student team.
Provide feedback to your student team on their demos within a few days to maintain progress.
Commit approximately 1 hour per week on average.
Provide all required data, systems, or specialised hardware before the project starts. We provide a development environment for the students to work in and to track their progress.
Complete short midterm and final evaluation questionnaires. These are taken into account during the grading process.
Our approach & deliverables
Partnerships are two-way investments: you receive fresh perspectives and software that may range from a prototype to a fully working solution, while students gain real-world experience. See our portfolio for previous outcomes of development by our students.
Projects are executed in an academic setting. No guarantees are made regarding delivery timelines, completeness, or production readiness. Software is provided "as-is" without warranties. No hosting, maintenance, or post-project support is included.
Costs
Free of charge, suitable for educational, research, and charitable initiatives.
By submitting a project, you agree to the Terms of Service. Projects run from February to June and require active client participation.
Current Board
LUdev is led by students, with support from faculty in both advisory and supervisory roles. Together they run the organisation and guide project teams.
CEO
As a recent Bachelor’s graduate in Data Science & AI, I have gained experience working on a wide range of projects, which sparked my passion for applying academic knowledge to real-world challenges. As CEO of LUdev, I will be responsible for the overall direction and management of the organization, providing strategic oversight and representing LUdev externally to strengthen collaborations with partners.
CTO
With four years of undergraduate education in Computer Science and hands-on experience through various (extracurricular) projects, I now oversee the technical infrastructure at LUdev. In this role, I also support and guide both clients and students in navigating technical challenges they may face.
CCO
As a graduate of the Bachelor in Computer Science & Economics, I combine technical knowledge with business insight to bridge the gap between IT and organizational needs. As CCO, I am responsible for managing our partnerships and ensuring clear, effective communication with the companies we collaborate with.
COO
With my experience in mentoring student groups and managing many software projects during my bachelor's in computer science, I will be responsible for implementing the CEO's plans and ensuring that the business runs smoothly. This involves overseeing the progress of company staff, managing day-to-day operations and supporting other staff as needed.
