Gallery Review

The Team

  • Kayla Davis
  • Bill Dybas
  • Robert McLaughlin
  • Tina Howard

About

The School of Photographic Arts and Sciences (SPAS) holds an annual art exhibition highlighting the top works of RIT student artists. Students can submit works for consideration during an open call, and a panel of RIT faculty jurors vote on which art will be displayed in the gallery at this show. Currently, SPAS has been paying for and using a software as a service product, Cafe, to facilitate this process; however, frustrations with Cafe’s difficult-to-use interface and poor user-experience for both administrative and student workflows has led them to seek custom replacement software which better fits their use case and work process. The new system will be designed to meet the department’s needs, and will be hosted on CIAS infrastructure allowing for full control of the open call process and for future software feature development as desired.


Development Methodology

We are using a Distributed Scrum Agile methodology as the backbone of our process. In order to keep high visibility and accountability, we will have 1 - 2 week sprints that require: a triage and planning meeting to allocate work; a retrospective meeting to figure out what we're doing well, what we need to continue doing, and what we need to do better; daily standups through a Slack channel; and demos to our team and sponsor to show off our incremental work.


Metrics

Velocity
Velocity is a measure of the amount of work a the team can tackle in a single sprint. Velocity gives our team an idea of what we can handle in a single sprint and in a big picture sense, what we can commit to creating by a specific date.
Code Coverage
Code coverage will give us a measure of how well tested our code is. This is important to creating software that works as expected. A robust suite of tests works to make sure we’re writing code correctly before committing and not creating regressions. We will use code coverage as a reference point for how well tested our code is, but it isn’t the end-all be-all of proving code quality. It serves more purpose in showing us where we are lacking in testing.

Domain Model


4 Up


Time Tracking