...
- Re: Separating Prioritization and Testing: Discussion notes
- 2015-12-14 TAC/UAC Coordinating Committee
Implementation notes
Jan 2016 - wrap up of 1.5 release
tbd - early Jan setup meeting of Prioritization Team (weekly check-ins?)
late Jan - process in place and schedules and meeting invitations in place for 2016 releases
late Jan - first Prioritization working meeting (grooming)
Jan 29 - backlog prioritization finished - 1mo worth of stories
sometime in Jan - Testing team meets
Feb 2016 - implement new development process
Feb 1 - Sprint planning meeting
Feb 19 - end of development and concurrent testing
Feb 22 - 26 QA testing
Week of Feb 22 - second Prioritization working meeting (grooming)
Feb 26 - COB ETD end of sprint
Draft Schedule
One release per every four months, three per year
...
Maintenance releases necessary to address critical bugs may occur independent of this schedule.
Draft Process / Cycle
Note - this is a general outline. Further changes and refinements may be made over time as groups are get underway with new cycle and ideas as improvement are raised.
1.Submission
Who: Users
Process step description: Submit a feature request or report a bug in the ArchivesSpace Support JIRA
When: rolling basis
2. Initial evaluation of tickets.
Who: ArchivesSpace Program Team (Brad, Christine, Chris & Brian)
...
Chris - your suggestions sound like good ones that should be discussed / examined further after the new development process is underway. It would be great to have a group (Program Team? one the Documentation sub-teams?) look at the current submission process think through the pros & cons of moving to the 2 alternates you suggest - as well as thinking through any set-up / transition work involved in changing how this is done.
When: rolling basis
3. Move accepted tickets from Support to Dev JIRA.
Who: ArchivesSpace Program Team (Brad, Christine, Chris & Brian)
Process step description: moves sufficiently detailed feature (and non-duplicative) requests and bugs into Development JIRA and categorize with a label, e.g. Epic e.g. 'EAD export'.
When: rolling basis
4. Prioritization / Grooming meeting.
Who: Development Prioritization team
...
When: Before start of each monthly sprint and/or once before start of a 4-month release cycle
5. Sprint Planning meeting.
Here's a draft overview of the meeting I made
...
When: Beginning of sprint cycle
6. Development & testing per sprint.
Who: Project Team
Process step description: Project team to work on code and documentation and testers to test functionality as stories are delivered.
...
When: weeks 1 - 3 of each sprint
7. Q/A testing
Who: Program team ( + others?)
...
When: last (4th) week of the sprint
8. Release
Who: Release Manager, Community Support Manager
...
When: three-weeks in advance of the release schedule - release date
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.
...
I changed this from "Agile Team" to "Project team" just because "Agile" feels a bit loaded. Project might be too generic?
Project team (code, testing, and documentation contributors):
Task: Implement features and bug fixes and documentation additions according to prioritization determined by Prioritization team. Will organize prioritized work into three consecutive month-long sprints.
...
for code contributions, unit tests should be included
[Brad to write up notes on overall testing strategy]
Meetings: Sprint planning meetings, 30min standups 3 times / week (M, W, F)
...
Testing:
Task: Testing features and bug fixes, during the first three weeks of a sprint.
...
As a new TAC member who just completed my first testing assignment, I think it would be useful to come up with guidelines on exactly what is expected here, where the outcome should be reported, etc. Maybe this is unique to a particular functionality and gets worked out during the Sprint Planning Meeting?
...
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.
...