After planning meetings, devs use remainder of this day to plan and get a head start on implementation activities.
Devs are actively implementing features and providing incremental releases to QA for testing.
Planning activities for next sprint, including PBI assignment and task estimation. This is a secondary opportunity to seek clarification on PBI requirements or acceptance criteria
Feature / Deliverable Demo
Devs use remainder of day to prepare for upcoming sprint:
- Preliminary design
Sprint tasks should be closed out or pulled into next sprint by EOD
Sprint Planning Meeting
Some teams follow up with a dev-specific planning meeting
Monday #1 is not considered a construction day, devs use remainder of day to plan/design implementations
Brief (~15 minute) conversations between offshore QA and individual devs, usually moderated by onshore QA lead:
- Discuss upcoming PBIs
- Identify remaining areas requiring clarification
- Final review of acceptance criteria / scenarios
We plan for construction to be completed by EOD on Wednesday #2 so that QA can finish testing implementation by end of sprint. On rare occasions construction may continue past this point, but that should be an exception rather than a rule.
Pre-planning exercise for next sprint, breaking PBIs into individual tasks, assigning to dev, and entering hours.
Some teams perform this as a group activity, others assign PBIs and have devs individually create tasks and assign hours.
Regular review and sizing of upcoming PBIs
This is an early opportunity to review and clean up PBIs and acceptance criteria
Demonstrate new features and/or deliverables to stakeholders.
Look back over the sprint to identify successes and opportunities for improvement. Active participation and dialogue is encouraged.
Functional testing begins as soon as the first testable PBI is delivered.
If bugs are discovered during regression testing, they are usually added into the next sprint.