ROF: Sprint Planning

1 Sprint Architecture
- 1.1 Backlog Item Breakdown
2 Release Process
- 2.1 Daily Breakdown
- 2.2 One-off Sprints
- 2.3 Backlog item checklist
- 2.4 Shippable Stories
- 2.5 UAT
- 2.6 Sprint Testing
- 2.7 Sprint Branches
- 2.8 Sprint Environments
3 Deployment
4 Definition of Done
- 4.1 Future consideration
5 Testing

Sprint Architecture

Backlog Item Breakdown

Percent	Task

Percent	Task
50%	New releasable feature work
10%	Bug Fixes
20%	Other tech or sprint-related work including: Ad-hoc testing - EN and FR Missed unit or automated tests Tech debt
10%	Release activities (including notes and change log) Documentation Make sure Playwright tests are passing
10%	Buffer

Release Process

We will ship once per sprint.

Process	Task

Process	Task
Ship once per sprint	Ship all shippable features once per sprint

Daily Breakdown

Length: 10 business days

Day	Task	Team Members

Day	Task	Team Members
1-3	Write change management ticket for release in two weeks (not next release but the following release)	Maggie & Jugraj
	Create sprint branch	Ashiq
	Confirm user stories that will go in next release	Jugraj, Ashiq & Maggie
	Finish UAT spreadsheet - based on users stories confirmed in the spreadsheet Send UAT spreadsheet to users	QA & Steve
	Distribute tickets in the sprint to the team: Write test case Manually test	Maggie
	QA & dev meeting to identify possible test cases as a group	QA & Dev
	Complete any additional testing of backlog items from previous sprint (if required) Add backlog items in current sprint to UAT spreadsheet (preparation for next release) Write test cases for PBI and bugs in current sprint Ad-hoc testing in QA environment (30min-1hr) Test backlog items as needed	Ewa & Tarek
	Develop backlog items Write test cases as needed Test each other’s backlog items as needed	Dev team
Day 4	Final sign off on backlog items to ship	Jugraj, Ashiq and Maggie
	ACC smoke test	QA, dev and Maggie
Day 5-8	Day 5 - Release ACC to prod	Jugraj & Ashiq
	Write test cases for PBI and bugs in current sprint as needed Test backlog items as needed	Ewa & Tarek
	Develop backlog items Write test cases as needed Test each other’s backlog items as needed	Dev team
Day 9	Identify what has met the definition of done that can be shipped on day 5 of next sprint Anything else that is not done will be completed and shipped the following sprint.	Jugraj, Ashiq and Maggie
	Write test cases for PBI and bugs in current sprint as needed Test backlog items as needed	Maggie & Tarek
	Develop backlog items Write test cases as needed Test each other’s backlog items as needed	Dev Team
Day 10	Sprint review & sprint planning Finish and wrap up what can be done	QA & dev team

One-off Sprints

Bug fix only sprint
Full regression test

Backlog item checklist

Team Member	Task

Team Member	Task
Dev	Complete backlog item or bug development Write test case (if needed) Create automated test (Playwright)
QA	Write test cases Manually test feature and surrounding features

Shippable Stories

Type	Required to Ship

Type	Required to Ship
Tech Debt	Definition of done is met
PBI	Definition of done is met
Bug	Definition of done is met

UAT

Product Owner or QA:
- Provide list of backlog items to users
- Users can test in ACC if they have time
- If users do not have time, they do not have to test (not required)
- Users should only test one hour max

Sprint Testing

UAT testing sheet
Smoke testing

Sprint Branches

Task	Branch	Team Member

Task	Branch	Team Member
Create sprint branch	Sprint branch	Ashiq
Push sprint code to sprint branch	Sprint branch	Dev team

Sprint Environments

Task	Environment

Task	Environment
Dev testing & Playwright	Dev
Current Release	ACC
Next Release*	QA

*When work in QA is ready for next release, they will be pushed to ACC

Deployment

Current: Manual deployment

Future: One-click deployment (Jugraj is working with Henry)

Definition of Done

Acceptance criteria is complete
PO (or equivalent) has approved screenshot of UI for new work (as needed)
Unit test is complete
Test case is written
Playwright test is written
Changes don’t introduce any new security defects, code-quality issues, or lower the code-coverage percentage
QA manual (main functionality and other components it interacts with) test is complete in correct branch
Documentation for security groups

Future consideration

Definition of done future consideration

Security
Code coverage

Testing

Task	Team Member

Task	Team Member
Ad-hoc testing	QA
Writing test cases	QA & Dev
Unit test	Dev
Automated - Playwright (B-unit test - UI based)	Dev
Manual test	QA & Dev
UAT prep	QA
UAT	QA or PO
Smoke test	QA & Dev
Regression test	QA & Dev