Two-Week Sprint Board: Plan to Retrospective

Project & Development

Two-Week Sprint Board: Plan to Retrospective

For development teams running two-week iterations, opened on day one and used until the sprint closes. The whiteboard holds the sprint goal, team agreements, blockers, and daily notes, plus a map of the two-week flow and the four sprint events. The task board tracks work through code review and testing, and starts with four parent tasks - planning, daily rhythm, review, and retrospective - each with its own subtasks.

0 Likes 0 Copies Author: WeProcess
sprint agile scrum retrospective two-week cycle
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Two-Week Sprint Board: Plan to Retrospective

Whiteboard preview

1. Sprint Goal (what these two weeks ... 2. Agreements This Sprint 3. Blockers & Dependencies 4. Daily Notes 5. Retro Notes (KPT) 6. How the Two Weeks Usually Go 7. What to Do When Work Gets Thrown In Take it in today Swap it into the sprint Push to next sprint Park it in the backlog Two-Week Sprint B... How to use: 1. Fi... Goal & outcome Agreements Blockers Learnings GoalWrite it here in 1-2 sentences.Keep it specific enough to judge on the last day. Definition of Done- Tests are passing- Review is approved- Docs are updated Signals of success- Points done: __ / __- Carried over: __- Unplanned work: __ Questions for the last dayDid we hit the goal?If not, what got in the way? Daily check-in at 10:00, 15 minutes Leave review requests in progress and ping Flag the same day if an estimate is slipping Unplanned work goes on the board before it starts Waiting on external API spec (ask: ____) Waiting on another team's review (asked: __/__) Recolor anything stuck for two days Post what you notice, right away That went well matters just as much Save improvement ideas for the retro Keep: what to continue Problem: what got in the way Try: what to test next (just one) Day 1Sprint planningAgree the goal, estimate, and set the load. Acceptance criteria get written here too. Day 2-4Getting goingStart the work and close the design gaps. Surface spec holes now, not later. Day 5Mid-sprint checkCompare progress against the goal. Adjust the load if the gap is real. Day 6-9Closing outReview and testing run together. Avoid starting anything new. Day 10Review & retroDemo the work, run KPT, pick one Try, and carry it forward. 縦軸: Urgency (low ... Outages and customer-facing bugs. Start today even if the goal shrinks, and note what you cut in the goal frame. A request that serves the goal. Drop an equal amount of work and record the trade on the board. Urgent but off-goal. Tell the requester it lands next sprint and move it to the top of the backlog. Neither urgent nor on-goal. Write one line on why, then park it. The decision ends here. 8. The Four Sprin... Four SprintEvents Sprint Planning Agree the goal Sprint Review Demo the work,take feedback Daily Check-in 15 min: progress & blockers Retrospective KPT and the next Try
100%

Drag to move, scroll to zoom

Task board contents

Sprint Backlog 14 items

Plan the sprint
Run the daily rhythm
Prepare the review
Run the retro
Write the goal
Estimate top items
Add acceptance rules
Set the daily format
Check blockers daily
Pick the demo owner
Write the demo flow
Collect KPT items
Pick one Try to run
Sort out carryover

In Progress 0 items

Code Review 0 items

Testing 0 items

Done 0 items

← Back to templates