# Remote Sprint & OKR Planner

## Overview
A single‑page workspace that lets remote teams **track product backlog**, **run two‑week sprints**, **capture retrospectives**, and **visualise quarterly OKRs**. All tables are pre‑wired with relation and rollup properties so you can:

* Pull backlog items into the active sprint automatically.  
* See sprint progress reflected in the OKR dashboard.  
* Export sprint completion data to Zapier/Make for automated reporting.

> 💡 Tip: Duplicate this page for each quarter (Q1‑2025, Q2‑2025, …) and rename the “Quarter” property in the OKR Dashboard to keep historical data clean.

## Backlog Database
| ID | Title | Description | Priority | Epic | Owner | Status | Estimate (hrs) | Created |
|----|-------|-------------|----------|------|-------|--------|----------------|---------|
| B001 | User auth revamp | Replace legacy login with OAuth2 | High | Authentication | Alice | Ready | 12 | 2025‑01‑03 |
| B002 | Mobile push notifications | Add push for new releases | Medium | Engagement | Bob | Ready | 8 | 2025‑01‑05 |
| B003 | Dashboard UI refresh | Redesign charts for better UX | Low | UI/UX | Carol | Backlog | 16 | 2025‑01‑07 |

> 💡 Tip: Use the **Priority** select (High, Medium, Low) to auto‑filter items into the next sprint view.

## Sprint Boards (Two‑Week Sprints)
| Sprint ID | Task (Relation → Backlog) | Owner | Status | Story Points | Sprint Start | Sprint End | Linked OKR (Relation) |
|-----------|---------------------------|-------|--------|--------------|--------------|------------|-----------------------|
| S2025‑01 | B001 | Alice | In Progress | 8 | 2025‑02‑01 | 2025‑02‑14 | O1 |
| S2025‑01 | B002 | Bob | Not Started | 5 | 2025‑02‑01 | 2025‑02‑14 | O2 |
| S2025‑02 | B003 | Carol | Not Started | 8 | 2025‑02‑15 | 2025‑02‑28 | O3 |

> 💡 Tip: Set up a **Zapier** “New Database Item” trigger on the Backlog DB to automatically create a linked task in the current sprint when the Status changes to “Ready”.

## Retrospective Journal
| Sprint ID | Date | What Went Well | What Could Be Better | Action Items |
|-----------|------|----------------|----------------------|--------------|
| S2025‑01 | 2025‑02‑14 | Fast auth rollout, good team sync | Under‑estimated push work | Add buffer for external API calls |
| S2025‑02 | 2025‑02‑28 | UI mockups approved early | Dashboard data latency | Refactor data pipeline, add monitoring |

> 💡 Tip: Use the **Rollup** of “Action Items” back into the Backlog DB to automatically create follow‑up tasks.

## Quarterly OKR Dashboard
| Objective | Key Result | Owner | Target | Current | Progress % | Quarter |
|-----------|------------|-------|--------|---------|------------|---------|
| O1: Strengthen security | KR1: Reduce login failures by 30% | Alice | 30% reduction | 12% reduction | 40% | Q1‑2025 |
| O2: Boost user engagement | KR1: Increase push open rate to 25% | Bob | 25% open | 10% open | 40% | Q1‑2025 |
| O3: Improve product UI | KR1: Reduce UI complaints by 50% | Carol | 50% reduction | 20% reduction | 40% | Q1‑2025 |

> 💡 Tip: Add a **Formula** column `Progress % = (Current / Target) * 100` to auto‑calculate progress.

## Automation & Integration Guide
| Integration | Trigger | Action | Notion Property | Zapier/Make Endpoint |
|-------------|---------|--------|-----------------|----------------------|
| Zapier – New Sprint Task | New row in Sprint Boards | Update linked OKR progress | Linked OKR → Progress % | `https://hooks.zapier.com/...` |
| Make – Sprint Completion | Status = “Done” in Sprint Boards | Move task to “Completed” archive | Status | `https://hook.make.com/...` |
| Zapier – Retrospective Action Items | New row in Retrospective Journal | Create Backlog item | Action Items → Backlog.Title | `https://hooks.zapier.com/...` |

> 💡 Tip: Keep the **Database ID** (found in the URL) handy; you’ll need it when configuring Zapier/Make webhooks.

## How to import into Notion
1. **Create a new page** in your Notion workspace where you want the planner.  
2. Click the three‑dot menu → **“Import”** → select **“Markdown & CSV”** and upload this `.md` file.  
3. Notion will render each markdown table as a **plain table**. For each table:  
   a. Click the table → **“Turn into database”** → choose **“Table – Full page”**.  
   b. Rename the database to match the section title (e.g., “Backlog”).  
   c. Adjust each column’s **property type** (Select, Person, Date, Number, Relation, Rollup, Formula) according to the header description.  
4. Set up **Relation** properties:  
   * In “Sprint Boards”, add a Relation to “Backlog” (Task) and to “Quarterly OKR Dashboard” (Linked OKR).  
   * In “Retrospective Journal”, add a Relation to “Sprint Boards”.  
   * In “Quarterly OKR Dashboard”, add a Relation to “Sprint Boards”.  
5. Create **Views** for each database:  
   * Backlog → “Ready for Sprint” (filter Status = Ready).  
   * Sprint Boards → “Current Sprint” (filter Sprint Start ≤ today ≤ Sprint End).  
   * OKR Dashboard → “Progress Bar” (group by Quarter, show Formula).  
6. Open **Zapier** or **Make**, create new scenarios using the **Database IDs** (copy from the URL after `…/`), and map the fields as shown in the Automation & Integration Guide.  
7. Test a few triggers (e.g., change a Backlog item to “Ready”) to confirm tasks appear in the active sprint automatically.  

Your Remote Sprint & OKR Planner is now live—ready for remote teams to plan, execute, and measure impact every quarter. Enjoy!