/
Dev/Pri Retrospective 2025-2026

Dev/Pri Retrospective 2025-2026

Overview of Accomplishments

Assessed 115 unique tickets (including ~20 in Awaiting More Information purgatory)

Passed for development: 69

Awaiting more information: 20

Closed: 23

Reassigned to different subteam: 4

  • Regularly kept up with bug report and feature request backlog

  • Cleared out ~20 awaiting more information tickets

  • Solicited community feedback on several tickets via the ArchivesSpace email list to guide Dev Pri decision-making

What Went Well

  • Rewriting and/or splitting tickets to make sure each ticket has only one issue/request and asks are clear for developers 

  • Good mix of experience on the sub-team with different aspects of the platform. Tickets were assigned well based on experience

  • Meetings were mostly efficient thanks to member engagement

  • Clarifying member expectations in and outside of Dev/Pri meetings

What Did Not Go Well

  • Theming meetings based on groups of tickets. There was never really a solid group of tickets that revolved around the same issue for us all to focus on. At most, 2 people were assigned tickets for the same ArchivesSpace module. Perhaps theming would be more achievable with a larger backlog.

What Can be Improved

  • Engagement with tickets without needing prompting via requests for feedback on specific tickets

  • Member awareness of the ticket creation processes 

  • When themed/grouped tickets are assigned, communicating to the assignees that they might want to work together before the meeting

  • Clarity on how tickets are selected for review, especially out of the backlog

Ideas for Next Term

  • Establishing clearer guidelines for reviewing Awaiting More Information tickets

  • Specify the meeting that tickets with requests for feedback will be discussed at, and make explicit invitation to commenters and others to attend that meeting

  • Collaborate with the Member Engagement subteam to get the word out about the ticket creation/engagement process. Maybe there’s an opportunity to talk with the people involved in the Member Match groups about this?

  • Perhaps attempting to group tickets not only from the backlog but also including “ready for implementation” tickets could help theming tickets and creating meaningful groups? 

  • Expanding meetings to be up to 2 hours, with an expectation of only using 60-90 minutes, so fewer tickets get bumped to the next meeting

  • Establish guidelines for reassigning tickets if members have scheduling conflicts (either for reassigning to someone else for the next meeting, or adjusting expectations for communicating ahead of time about meeting attendance)

  • Link to work plan in agenda

  • Build in a short pause before each person presents their tickets to allow people to review the tickets before the presenter discusses them

Roster Changes for Next Term

Departures: Alexander Duryee (TAC), Bonnie Gordon (TAC) Regine Heberlein (TAC), and Bri McLaughlin (TAC)

2025-2026 Lead: Dalton Alves (UAC)

2025-2026 Vice-Lead: Evalyn Stow (TAC)