Development Prioritization subteam

The Development Prioritization subteam is comprised of members from both the ArchivesSpace User Advisory and Technical Advisory Councils. This subteam was created in January 2016 following a decision to split the former Features Prioritization and Testing team into two separate groups.  In collaboration with the ArchivesSpace Program Team, the subteam prioritizes feature requests and bug reports for developers working on future releases of the ArchivesSpace program and occasionally may make recommendations on creating Task Forces to holistically address specific areas of the program for improvement.

The prioritization process:

The co-leaders survey Bug and Feature Request Jira tickets and assign tickets to subteam members to investigate and discuss at the subteam meetings.  In preparation for the meeting, subteam members:

• Verify whether the issue still relevant and whether it should be addressed locally or within the actual program
• Comment on the ticket/share it with the ArchivesSpace member listserv to gather additional clarification/community input when needed
• Confirm or reevaluate the priority ranking of the ticket
  • Rankings in order of least to greatest severity:
    • Trivial
    • Minor
    • Major
    • Critical 
    • Blocker
• Confirm or suggest tags for the tickets (this helps with grouping related tickets for development projects)
• Document their routing recommendation (“Awaiting More Information,” “Ready for Implementation,” "Ready for Community Developer," or “Closed” if the ticket is declined) in the monthly meeting agenda

During the Dev. Pri. meetings, the subteam discusses the tickets and their recommendations and route them to their next status. The subteam member assigned to the ticket will follow up on the ticket with explanatory comments on the decision.  Each meeting tries to address a mixture of Bug and Feature requests, from both the “Awaiting Prioritization” and “Awaiting More Information” queues.

Factors influencing the prioritization include

• Demonstrated community interest in the issue by supporting votes and comments on the tickets and/or discussion on the member listserv and Google Group
• Sufficient specification (see the How to Request a new Feature/How to Report a Bug documentation and Hydra Project)
• Developer capacity and expertise
• Priorities outlined in the Development Roadmap
• Results of the Development prioritization survey (last issued July 2016)

2018 Roster and Areas of Expertise