Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 ArchivesSpace User Advisory and Technical Advisory Councils. The Development Prioritization was created in January 2016 following a decision to split the former Features Prioritization and Testing team into two separate groups. 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: 

  • Mark Custer
  • Gordon Daines
  • Chris Prom
  • Kari Smith
  • Suzanne Stasiulatis
  • Lydia Tang
  • Sally Vermaaten
  • No labels