Page Comparison

...

• Re: Separating Prioritization and Testing: Discussion notes
• 2015-12-14 TAC/UAC Coordinating Committee

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:  

Draft Process 

1.Submission

...

Testers for each feature to be identified before beginning of each sprint (?). Testers added as watchers to tickets so will be automatically notified when a feature is ready to be tested.

When: weeks 1 - 3 of each sprint