At QuickSchools, we believe in continuous improvement for our product (and service). As such, we employ the Agile Development methodology for software development. This means that we make frequent incremental releases that we call Sprints. The industry standard for Sprints is between 1 – 4 weeks. At QuickSchools, our Sprints are about 3 weeks long, give or take.
Improvements that are included in any particular Sprint are prioritized based on demand. So if a a lot of schools want a certain improvement, or if a lot of schools stand to benefit from a certain improvement, we tend to work on those first. Sprints also include general improvements to infrastructure like hardware, network and security upgrades, as well as improvements to performance, availability and data recovery (improvements you don’t necessarily notice over time). But we do try to include functional improvements to each Sprint as well. It’s really the functionality improvements that people notice and pay attention to.
Sprint D7 – May 21, 2018
That being said, we wanted to be a little more transparent with our releases. We had a release earlier this week (labelled Sprint D7) and it contains the following functional improvements:
- Student Tags
- Scheduling Dropdown (Private Beta)
- Refactoring for Master Scheduler (Private Beta)
- Report Creator bug fixes
If you have any suggestions for improvements, please don’t hesitate to engage our support staff. They will be relaying feedback to our product development and engineering teams for prioritization and development.
[…] wanted to make a quick QuickSchools announcement about our most recent Sprint release. Sprint D8 which was deployed earlier today includes the […]
[…] The QuickSchools Gradebook is one of our core modules and we spend a lot of time making sure teachers have the best possible experience when working with it. We’ve been taking teachers’ feedback and have made a lot of improvements over time. […]
[…] have a new Sprint Release coming up next week. Be sure to stay tuned. And as always, we welcome your feedback to help us […]
[…] the interest of transparency, we’ve starting publishing our release notes since May 21, with Sprint D7. And this process has continued till today, with the upcoming release of Sprint D18. We look […]
[…] our next Sprint E2 will be 4 weeks long, and will be deployed on the week of Feb […]
[…] changed our engineering schedule a little bit. Our development Sprints will now be 2 weeks long, instead of 3. This should make for a smoother rollout of new […]
[…] Sprint has mainly been focusing on bug fixes and minor improvements. The WYSIWYG Editor in the E-Mail […]
[…] There’s so much that the system can do, coupled with the fact that new improvements are being released on a regular basis, schools don’t necessarily realize the full potential of our […]
[…] next Sprint E23 will be the last sprint of 2019, and will run an extra week with a scheduled deployment on Dec 30, 2019. But for now, […]
[…] the next several Sprints, QuickSchools will be focusing on bug fixes, performance improvements and UI […]
[…] making several improvements to the Admissions module in QuickSchools, we thought we’d summarize some of the features in a […]
[…] are looking into improving the way we manage attendance that is Not Yet Taken. Some ideas we are considering for the FUTURE […]
[…] are constantly looking for ways to improve our product and services. New improvements are prioritized based on demand. Improvements we are considering […]
[…] to Learning Management Systems like Google Classroom improved. It is our philosophy to make incremental but frequent improvements to the QuickSchools offering. Here we discuss some of the recent improvements to the Google […]
[…] Sprint has mainly been focusing on bug fixes and minor improvements. The WYSIWYG Editor in the E-Mail […]
[…] making several improvements to the Admissions module in QuickSchools, we thought we’d summarize some of the features in a […]