...
- Design: 1 Week
- Sprint Planning happens at the beginning of this week
- Available the thursday Thursday BEFORE sprint planning, Product Owner will produce Theme for sprint, and prioritized list of issues for review
- Design meetings for any changes/new features that involve redesign. Only the key stakeholders for the given issue need attend. Out of that meeting should come a spec that QA can then use to write test plans from and developers can use to implement code from.
- Sprint Planning happens at the beginning of this week
- Feature Development: 2 weeks
- QA works on test plans for the upcoming functionality during this phase
- End of these 2 weeks is FEATURE FREEZE. The release engineer will deliver first release to QA with a release note stating details of what new features are included in this release.
- No triage during the first week; should have triage the thursday Thursday of the second week
- Bug Backlog: 1 Week
- Bug triage weekly
- At the end of this cycle, there is a developer code freeze. This means that after this point, only fixes to bugs related to the development work in this sprint can be addressed. Code should be branched (see SVN Guide for details).
- End of this week there should be another release to QA. Th release note should include a list of bugs fixed in the new release candidate. Optionally there could be additional releases during the week.
- QA Phase: 2 weeks
- Bug triage weekly, or more if QA sees a need (not daily)
- Developers will be fixing major bugs as they come in, bug fixes will be checked into the release branch.
- Iterative releases to QA, decided upon by communication between dev and QA. Release notes will accompany any release to QA.
- The final release candidate should be stable by the wednesday Wednesday before the release to production.
- Towards end of cycle, QA gives recommendation of go or not go, and list of blocking issues that must be fixed in order to release.
- Communicate with customers about upcoming release.
- Product owner produces document for the next sprint the last friday Friday of this phase.
- Product Release
- Assuming we are on schedule, actual release would occur the tuesday or Wednesday of the Design Week for the next sprint. The code should be tagged in the release process. Please refer to guide on how to release thalia .
...