Class scheduling in the ICS department combines many complex and often confusing systems, involving three main parties: the instructors, the scheduling staff, and the department administrators. Altogether, multiple inefficiencies in the scheduling process has lead to unnecessary mistakes, a reduction to productivity, and further frustration from all involved parties.
Our team was given the opportunity to develop a software solution, in the form of a scheduling hub that would encompass the convoluted scheduling process by all involved parties.
Team SchedulAnts: Jessica Allen, Matthew Mendoza, Kevin Barahona, Shenghua Huo, Quincy Yang
Project partner: Lumen Russell
UI Designer
Software Engineer
Resident 10x (problems) Software Developer
Software Engineer
Software Engineer
Due to the large scope of the deliverable, our team collectively divided into two sub-teams, each focusing on the development of the application from different perspectives: one focused on the development of the visual frontend, and the other on the data-driven backend. While separate, every member collaborated with the team as a whole through task-driven development, adhering to traditional Agile methodology.
Alongside regular inner-team communication between members, our team established weekly meetings with our stakeholder to disclose any and all work developments, and to initiate feedback conversations. These conversations looked to address any concerns between the parties, and for the stakeholder to exercise agency within decision making. Through the use of Slack, our team was able to maintain a reliable communication pathway to the stakeholder, and a method for them to continue conversations post-weekly meetings.
Cross Platform Development
Required strategic teamwork, division of labor, and effective team communication
Team/Stakeholder Collaboration
Information overload required us to negotiate with the stakeholder to create a
singular truth.
Project Scope/Ballooning
Excess information quickly scaled our requirements for the project, minimizing
effective work
Negotiation helped trim priorities, correcting development
Learning Tech Stack
Different experiences lead to division, requiring more personalized workflows and
increased peer-collaboration
Working closely with our sponsor, our team successfully narrowed the project's scope to focus on the most essential features for the duration of the project. Based on suggestions from our sponsor, professor, and UI/UX evaluators, we implemented and adjusted the core components of the system accordingly.
Acknowledging our team's foundation, our application takes inspiration from formerly used products that initially looked into solving the issue of scheduling within the ICS department. However, each solution ultimately fell into disuse from a lack of usage either through little motivation to switch, or fundamentally limiting features.
Using various technologies, we created supplementary material that will help developers and stakeholders understand the requirements, constraints, and functionality of our current system at a high level. This will ensure that future development can continue with ease.
Describes stakeholders and their user stories that influence the design of the API
Describes the information models that API will store and access
Describes available functionality of the ICS scheduling API including endpoints, validation, and expected responses.
The developed interface is the result of conversations between multiple different potential users of the interface, namely instructors who provided feedback on how they may want to input preference data, and scheduling staff who indicated what types of information they would like to see in the interface. These, in addition to own self-generated opinions with the use of personas, allowed us to identify key areas of concern in context of the previously used products. Each piece of feedback was reviewed by the team and stakeholder, and prioritized to most efficiently address concerns.
In the hopes of achieving
User Experience / Accessibility:
The user interface was iteratively refined based on user testing and stakeholder feedback.
Following the implementation of the most user-friendly design, the website's accessibility was thoroughly evaluated using the WAVE tool.
All contrast errors were corrected, and all images and links were provided with appropriate alt-text to ensure comprehensive accessibility.
Ultimately, to satisfy stakeholder expectations, our team developed the foundation for the ICS Scheduling Hub. The web-based application allows Instructors to input schedule preference information that would then be stored and managed for the ICS scheduling staff to use. The current build focuses on the Instructor side of the hub, but provided adequate tools for future wings of the site to be developed, utilizing instructor-sided information.