...
- Re: Separating Prioritization and Testing: Discussion notes
- 2015-12-14 TAC/UAC Coordinating Committee
Draft Schedule
One release per every four months, three per year
Three sprints per each release, each a month long in duration
Development and concurrent testing occurs during the first three weeks of each sprint; concurrent testing is supported by nightly builds
Q/A testing for the sprint occurs during the fourth week of each sprint
Community testing of a release candidate occurs for three weeks prior to each scheduled release
Maintenance releases necessary to address critical bugs may occur independent of this schedule.
Draft Process
1.Submission
Users submit a feature request or report a bug in the ArchivesSpace Support JIRA
...
When: Beginning of sprint cycle
6. Development & testing per sprint.
Developers begin work and indicate to testing team when stories are ready to be tested.
...
When: weeks 1 - 3 of each sprint
7. Q/A testing
Program team, and any others, test deliverables of the sprint during the last (4th) week of the sprint and indicate which stories are accepted for the scheduled release and which are rejected.
Rejected stories may be resolved during the last week of the sprint, deferred to the next sprint, or placed into the backlog for a future release
8. Release
The designated Release Manager prepares a Release Candidate three-weeks in advance of the release schedule.
The ASpace Community Support Manager notifies the community of the presence of the release candidate, indicates new features and bug fixes in the release, and invites the community to test those additions as well as other areas of the application
Problems reported are cycled back to the Q/A team for resoltuion. Problems may be resolved prior to the release and included in it, or removed from the release and targeted for a later release.
The designated Release Manager prepares the release, after the community testing period is over and all resolutions made.
The Community Support Manager announces the distribution of the release, indicating the new features and bug fixes that made it into the release, as well as those that ultimately "fell out".
Groups involved:
Development Prioritization
Task: On the basis of feature requests and bug reports filed in the development catalog, this team prioritizes development work for each schedule features release (1 per every four months) in advance of the first sprint for each features release.
Leader:
Members:
Meetings:
Development:
Task: Implement features and bug fixes according to prioritization determined by Prioritization team. Will organize into three consecutive month-long sprints, according to is perception of the most expeditious way to address the workload.
Leader:
Members:
Meetings
Testing:
Task: Testing features and bug fixes, during the first three weeks of a sprint.
Leader:
Members:
Meetings:
Quality assurance
Task: Testing features and reviewing prepared documentation during the last week of a sprint to ensure all work necessary for a sprint has been completed or deferred to the following sprint.
Leader: Brad W.
Members: Members of the program team (developers, program manager, community manager)
Meetings:
...