This is a cross-council subteam that includes members of The Development Prioritization subteam is comprised of members from both the ArchivesSpace User Advisory and Technical Advisory Councils. The Development Prioritization This subteam was created in January 2016 following a decision to split the former Features Prioritization and Testing team into two separate groups. On the basis of In collaboration with the ArchivesSpace Program Team, the subteam prioritizes feature requests and bug reports in the development catalog, along with developer availability, this subteam prioritizes development work for each minor and major release. The subteam meets at least monthly.
Past prioritization criteria have included:
- Number of votes received in community voting round
- Voting for epics (if process is enacted by Prioritization group)
- Development prioritization surveys (last issued July 2016)
- Themes and epics targeted per release
- Sufficient specification (see Hydra Project for useful guidance as to what constitutes a well-documented story )
- Expertise and capacity of available developers
- Anecdotal evidence of community priorities, e.g. listserv discussion, email reports
Team responsibilities include:
- Select prioritized features and bugs for upcoming releases in collaboration with the ArchivesSpace Program Team
- Continual grooming of icebox and backlog including reviewing issues, verifying, de-duping 1
- Provide or obtain clarification for issues and secure from original reporters or provide details*
Team Leader Responsibilities:
- Schedule and facilitate meetings of Prioritization Subteam with Program Manager
1 As of March 2017, the ArchivesSpace Technical Lead, in conference with the Prioritization group, has proposed a revised bug reporting and feature request. Once implemented, the Prioritization group will resume grooming of icebox and backlog.for developers working on future releases of the ArchivesSpace program.
The prioritization process:
Subteam members are assigned Jira tickets to investigate and discuss at the team meetings. In preparation to the meeting, subteam members verify the issues, seek/provide clarification when needed, and screen for duplicates, obsolete issues, or institution-specific technical issues that should instead be addressed locally. During the meeting, the subteam discusses the tickets, reevaluates the priority ranking, and will route the ticket to “Awaiting More Information,” “Ready for Implementation,” or “Closed” if the ticket is declined. Subteam member assigned to the ticket will follow up 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 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
Co-Leaders: Jason Loeffler (Unlicensed) (TAC) and and Lydia Tang (Unlicensed) (UAC)
TAC Members:
- Megan Firestone (Unlicensed)Blair
- Patrick Galligan (Unlicensed)
- Cory Nimer
UAC Members:
- Suzanne Stasiulatis (Unlicensed)