The Development Prioritization subteam consists 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.
Team tasks includeThe prioritization process includes:
- Continual reviewing of The subteam continually review member-contributed feature requests and bug reports, including verifying
- Subteam members are assigned Jira tickets for each meeting to investigate and discuss at the team meetings. Subteam members verify the issues, seeking seek/provide clarification when needed, and screening for duplicates or , obsolete issues.
- Evaluating feature requests and bug reports for clarity and gather any needed information
- Provide or obtain clarification for issues and secure from original reporters or provide details
Prioritization criteria include:
- Number of votes received by community votes
- Voting for epics (if process is enacted by Prioritization group)
- Development prioritization surveys , or institution-specific technical issues that should instead be addressed locally.
Factors influencing the prioritization include
- Number of votes on the Jira tickets
- The results of the Development prioritization survey (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)
...