...
We have settled on meeting biweekly to check in on our projects, in order to maintain momentum. To avoid an undue time commitment, the meetings often were less than an hour long.
We established a “swimlane” in Jira to easily identify tickets with a “Usability” tag and prevent any accidental overlap with Dev Pri team projects.
The subteam was initially divided into two groups working on Public Interface and Staff Interface tickets. Moving forward, we have decided to work as a full subteam on specific larger scale projects, not individual tickets.
...
The Usability subteam will need to stay in touch with the ArchivesSpace program manager, to make sure that projects that they spearhead are not already being worked on by developers.
CC UAC chair and vice chair
The “swimlane” approach in Jira is currently imperfect, because
there isn’t an obvious workflow or routing tickets back to Dev. Pri. for approval, especially if future Usability members don’t also serve on Dev. Pri.
It may also create an artificial bottleneck for tickets that have the Usability tag which otherwise are straightforward enough to not need input from the subcommittee before Dev. Pri. vetting.
While the Collection Organization view project will extend beyond the term of several of our members, we hope the reconstituted team will be willing to pick up and champion the project into the future.
The Usability subteam, additionally, in collaboration with the Program Manager, might want to consider exploring a large-scale grant to improve the usability of the interfaces.
The Usability subteam might want to consider building on the work and advocating for the implementation of the Staff Interface Enhancement Working Group’s recommendations. While submitted in 2017, many of the recommendations still haven’t been implemented.
Continue to also refer to the now-defunct Reports team final recommendations, to ensure that reports continue to develop in functionality.