On the basis of feature requests and bug reports in the development catalog, this subteam prioritizes development work for each scheduled features release (1 per every four months) in advance of the first sprint for each features release. 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. 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 subteam meets at least monthly a few days before the scheduled SCRUM meeting.
Prioritization criteria (subject to refinement by the prioritization subteam in 2016) are:
- Number of votes received in community voting round (early 2016)
- Voting for epics (if process is enacted by Prioritization group)
- Theme / epics targeted per release
- Sufficient specification (see Hydra Project for useful guidance as to what constitutes a well-documented story )
- Expertise / 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 and sprints in collaboration with the ArchivesSpace Program Team
- Continual grooming of icebox and backlog - reviewing issues, verifying, de-duping
- Provide or obtain clarification for issues - secure from original reporters or provide details*
Team Leader Responsibilities:
- Schedule and facilitate meetings of Prioritization Subteam and Program Manager
- Represent Prioritization Group in monthly Scrum meetings or, if unable to attend, delegate this responsibility
- Report targets for each release to Scrummaster prior to each Sprint Planning meeting
- Report to Community Support Manager prior to each Sprint Planning meeting
*Note as of 2016, a decreasing number of JIRA issues should require additional clarification, as Program Team will request clarification directly after user submission and before moving in the development queue.
2016 Roster
Leader: Jason Loeffler
Members:
...
prioritization process:
The lead reviews Bug and Feature Request Jira tickets and assign tickets to subteam members to investigate and discuss at the subteam meetings. Each meeting tries to address a mixture of Bug and Feature requests, from both the “Awaiting Prioritization” and “Awaiting More Information” queues. 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 (in order from least to greatest - these descriptions are suggestions for applying more consistency with the priority rankings):
- Trivial: a really small improvement for a specialized area of the program with limited impact and little time-constraint
- Minor: an improvement for an area of the program with little time-constraint
- Major: a large improvement for the program with some time constraint
- Critical: the program currently is not working and impacts users in regular use
- Blocker: the program currently not working, dramatically impacts users in all use, and must be addressed immediately.
- 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 and the subteam lead updates the ticket status.
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)
- Developer capacity and expertise
- Priorities outlined in the Development Roadmap
Average Workload:
The ensure that Dev. Pri. discusses enough tickets and has time for discussion, the monthly meetings are 1.5 hours long.
The average time commitment for subteam members is approximately 2.5 hours per month (including the monthly meeting time). Each person is usually assigned 3 tickets to investigate for each meeting.
The average time commitment for the subteam lead is approximately 3.5 hours per month (including the monthly meeting time). The lead selects and assigns the tickets, facilitates the meetings, routes the tickets on the kanban boards, and prepares quarterly reports to the UAC or TAC chair as requested.