How do you prioritize features in a product backlog when resources are limited?

During my final year project, I worked on developing a student management app aimed at helping students organize their schedules and track assignments. With limited time and resources, we had to prioritize which features to implement first. We conducted surveys among our peers to identify the most requested features. After gathering the feedback, we used a simple ranking system: features that addressed the most common pain points, like assignment reminders and calendar integration, were prioritized. This approach not only kept our project focused but also ensured we delivered a product that met the immediate needs of users. By the end of the semester, our app was well-received, and we received positive feedback for its usability.