Software Design
GroupedIn
A platform for managing university group projects (first named MyGroups), planned with a product backlog and sprints, prototyped in Figma, built as a beta and refined through usability testing with five users.
- Team of 6
Project Files 2
What I learned
The challenge
One platform had to serve four kinds of users (students, group leaders, lecturers and staff) without becoming complicated for any of them. Usability testing with five users pointed to improvements in clarity, navigation and task flow.
The experience
Planning in sprints with a product backlog and story points, then building and refining the platform in iterations as a team of six.
Skills I developed
- Agile planning
- Software requirements (SRS)
- UML diagrams
- UI/UX prototyping
- Usability testing
01The problem
Group projects are a core part of studying at Taylor’s, but forming groups, dividing work, communicating and keeping lecturers informed are common struggles. Existing platforms such as MyTimes and CampusCentral aren’t built for group work.
02What the team built
- Project tracking: a shared to-do list where members add and complete tasks, and the group leader balances the workload
- Consultations: students ask lecturers for help and get answers on the platform
- Separate views for students, group leaders, lecturers and system staff
- Interface sketches, a Figma prototype and a functional beta platform
03Software engineering process
Planning
A product backlog, story-point estimates, sprint goals and prioritised tasks.
Requirements
A software requirements specification, refined in the group project.
Design
Use case and activity diagrams, and interface sketches for each type of user.
Implementation
Iterative development in sprints, from a prototype to a functional beta platform.
Testing
Task-based usability testing with 3 students and 2 external users, followed by interviews. The interface was improved based on the results.