Max = orange
CFitz = Pinkish? Puce?
Related call notes:
- Re: Separating Prioritization and Testing: Discussion notes
- 2015-12-14 TAC/UAC Coordinating Committee
...
It would be good for some group to consider improvements to steps 1 - 3 to in particular bug tracking and reporting as we could probably make some improvements. Currently support requests also come via a number of channels and this causes problem for everyone involved in the process. Need to encourage users to log tickets in support JIRA.
CF: Yes, I agree with the bug reporting. It's compounded by the fact the support JIRA doesn't allow users to follow tickets and that people have to add an email. IMO, the support JIRA hasn't really worked out. Would it be best to just encourage people to record bugs in either 1) Github issues or 2) the mailing list. We add those in JIRA ( since I use completed JIRA tickets to generate the change log )? I think this would eliminate one channel ( the JIRA support ). Users adding their own tickets to the general AR JIRA project often means they just get lost...
When: rolling basis
3. Move accepted tickets from Support to Dev JIRA.
...
Meetings: Monthly (1st month -target features and bugs for release and suggest first sprint; 2nd month - suggest targets for second sprint and groom icebox; 3rd month - suggest targets for third sprint and groom icebox; 4th - start preparation for next sprint)
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):
...