Agile in Action:
Our Product Development Cycle
Your feedback drives quarterly releases of new features and improvements
Ever wonder how software gets made? Or wish you had more say in the software you use daily? Let us pull back the curtain to show how your feedback as Tevera users vitally informs and feeds into our software development process.
Responsive Development: The Agile Model
Our software team follows a development process distinguishing the most successful brands: the Agile Model. Agile development encourages rapid, flexible responses for continuous improvement. Here’s how it works: we release new versions of software on a regular basis, then seek real-world feedback from our users. Our Tevera engineers and designers analyze this feedback and bring it back into the development cycle for new features, product enhancements, and quality improvements. Two-week engineering “sprints” focus development on these specific, user-informed improvements and features for faster project completion. Finally, our bug and user acceptance (UA) testing looks at the user experience to ensure that the release looks and feels as originally outlined, in a way that works best for you. If not, it cycles back into a sprint to work out the kinks. When everything looks good, we release this latest software version, along with training and support materials.
Releases are completed monthly or quarterly, depending on the complexity. For users, this means that we are able to respond quickly (one might say… agilely?) to your feedback. We want to design according to your experience and needs, so share your thoughts and suggestions!
Core Development Framework: Jobs-to-be-Done
At the heart of our process is a development framework based on Jobs-to-be-Done (JTBD) principles. We use the JTBD framework to understand and unlock the student career journey, from classroom experience through licensure, and on to practice. Along that journey, we map the “jobs” of each stakeholder including program administrators, field instructors, clinical supervisors, faculty, and employers. JTBD allows us to break those jobs down into steps, ultimately helping us develop software that simplifies a job in the first place and makes it that much easier for stakeholders to complete!
Agile in Action: The New Student Interface
Here’s a concrete example of your vital role in our product development: In 2016, we released our first version of Tevera (Clinical Training Manager). In December 2017, we surveyed students to get their initial feedback. We also conducted a series of in-depth, one-on-one interviews to get more specific usability feedback. Users responded positively to Tevera’s functions tailored to their “core jobs,” but felt that the interface got in the way of “getting the job done.” Based on their input, we’ve developed a new Student UI that improves the student experience by making their workspaces much more intuitive. This process also lays the foundation for future enhancements.
Student UI Sneak Peek
Our new Student UI is scheduled for release in early April. Take a look:
Coming Soon: More New Features!
In the next weeks, we’ll give more information on a slew of new features coming out of our agile process. We hope that you will be pleased and encourage you to continue sharing feedback. Keep that improvement cycle turning!