π On This Page (Tap to expand) βΎ
- 1. Choosing Your Project Architecture: Pro vs. Corp Workspaces
- Option A: The Pro Tier Approach (Lightweight Direct Sharing)
- Option B: The Project & Enterprise Tier Approach (Corp Governance)
- 2. The 5-Stage Project Delivery Lifecycle
- 3. Stage 1: Initiation, Scope & Project Charter (Tier 3 Documents)
- 4. Stage 2 & 3: Backlog Staging & Sprint Planning (Planning Studio)
- How to Run a High-Impact Sprint Planning Session:
- 5. Stage 4: Execution, Sub-Steps & Quality Assurance
- 6. Stage 5: Timekeeping, Timesheet Exports & Sprint Rollover
- Logging Billable & Non-Billable Hours
- Exporting Client Invoices & Timesheets
- 1-Click Sprint Rollover & Archiving
- 7. Project Management Best Practices & Summary
- Related Guides & Deep Dives
1. Choosing Your Project Architecture: Pro vs. Corp Workspaces
Before launching a project, select the collaboration model that fits your team's size, budget, and governance requirements:
Ideal for: Freelancers, solopreneurs, agile duos, and ad-hoc client collaborations.
Structure: You create a Matrix and invite collaborators directly via email.
Setup Time: 10 seconds. Zero corporate hierarchy or overhead needed.
Ideal for: Agencies, multi-department companies, and cross-functional squads.
Structure: Root Corp container > Project containers > Scoped Matrices.
Capabilities: Pooled seats, Project Admins, compliance audit logging, and 30-day trash.
Option A: The Pro Tier Approach (Lightweight Direct Sharing)
If you are on the Pro Tier, you do not need an enterprise contract to collaborate. You can run projects immediately:
- Create a dedicated Matrix for your project (e.g.,
"π Website Relaunch"). - Click [ π₯ Share Matrix ] in the header.
- Enter the email addresses of up to 20 collaborators (designers, copywriters, or client stakeholders).
- Select their permission level (
EditororViewer). - Instant Collaboration: Your team members can view cards, mark tasks complete, leave comments, and log hours without complicated onboarding.
Option B: The Project & Enterprise Tier Approach (Corp Governance)
When running larger organizational initiatives with multiple workstreams:
- The Corp Container: Corp Admins create an organization umbrella with pooled seats.
- Dedicated Projects: Create a formal Project container (e.g.,
"Project Phoenix: ERP Migration"). - Project-Linked Matrices (
sharingMode: 'project'): All matrices assigned to the project are automatically visible to authorized project members. - Delegated Project Admins: Empower squad leads to invite members and manage matrices without granting them full company-wide administrative rights.
- Compliance Audit Trails: Track every task deletion, status change, and role elevation in a tamper-evident audit log.
2. The 5-Stage Project Delivery Lifecycle
Regardless of your tier, every successful project follows five operational stages:
flowchart TD
S1["π 1. CHARTER & SPECS
Tier 3 Scope Document & Roles"] --> S2["β‘ 2. STAGING & BACKLOG
Planning Studio LHS Source Pool"]
S2 --> S3["β±οΈ 3. CAPACITY & SPRINTS
Hour Budget & Sprint Target"]
S3 --> S4["π― 4. EXECUTION & QA
Q1βQ4 Allocation, Subtasks & Checklists"]
S4 --> S5["π 5. AUDIT & ROLLOVER
Timesheets, Invoicing & 1-Click Rollover"]
style S1 fill:#eff6ff,stroke:#3b82f6,stroke-width:1.5px,color:#1e40af
style S2 fill:#f5f3ff,stroke:#8b5cf6,stroke-width:1.5px,color:#5b21b6
style S3 fill:#fefce8,stroke:#eab308,stroke-width:1.5px,color:#854d0e
style S4 fill:#ecfdf5,stroke:#10b981,stroke-width:1.5px,color:#065f46
style S5 fill:#f8fafc,stroke:#64748b,stroke-width:1.5px,color:#3341553. Stage 1: Initiation, Scope & Project Charter (Tier 3 Documents)
Never start a project with raw, unorganized tasks scattered in a backlog. Anchor the initiative with a Tier 3 Document:
- In your project matrix, open the Documents Tab.
- Click [ + New Document ] and title it:
"Project Charter: [Project Name]". - Standardize on the following core sections:
- Summary & Objectives: What does success look like?
- Scope of Work (In-Scope vs. Out-of-Scope): Explicitly list what you are not building to avoid scope creep.
- Project Roles: Who is Responsible, Accountable, Consulted, and Informed?
- Milestone Schedule: Key release targets and deadlines.
- Keep this document linked to the board so any team member or client can review project principles at any time.
4. Stage 2 & 3: Backlog Staging & Sprint Planning (Planning Studio)
Traditional project tools force you to groom backlogs through endless ticket tables. DoneIsGoodβs Planning Studio (min-width: 1024px) provides a distraction-free, dual-pane desktop command center:
flowchart TD
subgraph Studio["β‘ PLANNING STUDIO: Sprint Staging & Hour Budgeting"]
direction TB
subgraph LHS["LEFT PANE: Master Project Backlog"]
direction TB
BDSrc["Source: Client Alpha Backlog"]
TasksList["βοΈ Staged Tasks: Database migration β’ Stripe webhooks β’ API docs"]
BatchBtn["Batch Actions: [ β±οΈ Set 2h ] [ β‘οΈ Move to Sprint ]"]
BDSrc --> TasksList --> BatchBtn
end
LHS --> Divider["βοΈ RESIZABLE DIVIDER (Drag & Drop or Batch Move)"]
Divider --> RHS
subgraph RHS["RIGHT PANE: Sprint 4 Container"]
direction TB
SGoal["π― Sprint Goal: Complete Auth & Stripe API (34h / 40h Budget)"]
subgraph SprintQuads["Sprint Matrix Allocation"]
direction TB
SQ1["π₯ Q1: DO FIRST (6.0h β’ 1 task)"]
SQ2["π± Q2: SCHEDULE (22.0h β’ 4 tasks)"]
SQ3["π€ Q3: DELEGATE (5.0h β’ 2 tasks)"]
SQ4["π Q4: SOMEDAY (1.0h β’ 1 task)"]
SQ1 --- SQ2 --- SQ3 --- SQ4
end
SGoal --> SprintQuads
end
end
style Studio fill:#f8fafc,stroke:#cbd5e1,stroke-width:2px,color:#0f172a
style LHS fill:#ffffff,stroke:#e2e8f0,stroke-width:1.5px
style Divider fill:#eef2ff,stroke:#818cf8,stroke-width:1.5px,stroke-dasharray: 4 4
style RHS fill:#ffffff,stroke:#e2e8f0,stroke-width:1.5px
style SprintQuads fill:transparent,stroke:none
style SQ1 fill:#fff1f2,stroke:#fecdd3,color:#9f1239
style SQ2 fill:#eff6ff,stroke:#bfdbfe,color:#1e40af
style SQ3 fill:#fefce8,stroke:#fef08a,color:#854d0e
style SQ4 fill:#f8fafc,stroke:#e2e8f0,color:#475569How to Run a High-Impact Sprint Planning Session:
- Open Planning Studio: Click the
β‘icon in the navigation bar. - Set the Panes: Set the Left Pane to your
"Project Backlog"and the Right Pane to your"Active Sprint Matrix". - Configure the Sprint: Click [ βοΈ Sprint Config ] on the right:
- Sprint Goal: State a crisp, singular outcome (e.g. "Ship Stripe subscription billing and invoice webhooks").
- Date Boundaries: Define a 1-to-2 week window.
- Focus Capacity Budget: Set the total target hours available for the sprint (for example, 40 hours for a solo developer, or 120 hours for a small team).
- Rapid Estimation: Click the
β±οΈpill on task cards to assign duration estimates (15m,30m,1h,2h,4h,8h). - Drag-and-Drop Allocation:
- Q1 (Do First): Hard dependencies, deployment blockers, and critical path items.
- Q2 (Schedule): Core strategic deliverables that move the needle.
- Q3 (Delegate / Batch): Administrative syncs, documentation, minor config tweaks.
- Q4 (Someday): Nice-to-have features that can wait if time runs tight.
- Watch the Capacity Gauge: The live progress meter ensures you never schedule more hours than your team can sustainably execute.
- Elaborate, Assign & Schedule in the Destination Matrix: Keep the project backlog clean and fast. Once tasks cross the split divider into the destination sprint matrix, team leads and builders elaborate the execution details:
- Individual Assignment: Assign unambiguous accountability to specific team members or external contractors.
- Scheduling: Set explicit target due dates or calendar blocks that sync directly to Google Calendar.
- Elaboration (Notes & Steps): Convert high-level tasks into actionable delivery checklists using Tier 1 Steps (
β‘ Generate Steps), and document technical specs, API endpoints, or repository links in Tier 2 Notes. - Tagging: Apply tags (
#backend,#design,#qa,#client-signoff) for rapid multi-dimensional filtering.
5. Stage 4: Execution, Sub-Steps & Quality Assurance
Once the sprint launches, teams move into the daily execution flow:
- βοΈ 1. Verify Stripe signature header on incoming requests
- βοΈ 2. Handle
invoice.payment_succeededand update user subscription document - βοΈ 3. Handle
customer.subscription.deletedwith 3-day grace period - βοΈ 4. Write unit test suite with mock Stripe payloads
Local CLI testing command:
stripe listen --forward-to localhost:5001
- Clear Definitions of Done: Never assign a task titled "Fix payment bug". Use Tier 1 Steps so every acceptance criterion is verifiable.
- Assignee Ownership: Assign tasks to specific collaborators so everyone knows who holds the ball.
- Activity & Comments: Team members leave updates directly inside the task card, keeping technical discussions attached to the deliverable rather than lost in chat channels.
6. Stage 5: Timekeeping, Timesheet Exports & Sprint Rollover
A project is only as healthy as its time accounting. DoneIsGood features built-in Time Recording directly tied to tasks:
Logging Billable & Non-Billable Hours
- Live Stopwatch: Click the play icon on any task card when beginning work. When finished, stopping the timer automatically records the duration.
- 1-Click Completion Prompt: Whenever a task is marked complete, DoneIsGood prompts: "Log time spent on this task?" with intelligent suggestions matching your initial estimate.
- Category Tagging: Assign categories to time entries (
Development,UI Design,Client Meeting,Code Review,QA).
| Task Name | Category | Member | Hours | Date |
|---|---|---|---|---|
| Stripe Webhook Handler | Development |
Alex R. | 3.8h | 14 Oct |
| Subscription UI Flow | UI Design |
Maya S. | 4.2h | 14 Oct |
| Weekly Client Demo | Meeting |
Alex & Maya | 1.0h | 15 Oct |
| End-to-End Test Suite | QA Testing |
Alex R. | 2.5h | 16 Oct |
| TOTAL LOGGED: 11.5 Hours | BILLABLE: $1,725.00 NZD | |||
Exporting Client Invoices & Timesheets
- Open the Time Recording dashboard.
- Filter by the Project Matrix and current date range.
- Click [ Download CSV ] or [ Export JSON ].
- Import directly into Xero, QuickBooks, FreshBooks, or attach as a transparent appendix to your client invoice.
1-Click Sprint Rollover & Archiving
When your sprint deadline arrives:
- Re-open Planning Studio.
- Click [ π Review & Rollover ] on the sprint matrix.
- DoneIsGood inspects your board:
- Incomplete Tasks: Automatically migrates unfinished tasks back into the project backlog (or rolls them forward into Sprint 5).
- Archive Sprint Matrix: Freezes the completed sprint matrix, preserving its time logs and completion history indefinitely without cluttering active menus.
7. Project Management Best Practices & Summary
| Project Milestone | Recommended Action in DoneIsGood |
|---|---|
| Pick Architecture | Use Direct Share for small/client projects; use Corp & Projects for agencies and enterprise squads. |
| Define Scope | Author a Tier 3 Project Charter before adding tactical tasks. |
| Stage & Estimate | Braindump tasks in Planning Studio and apply duration pills (β±οΈ 15mβ8h). |
| Destination Refinement | Assign owners, schedule due dates, elaborate Tier 1 steps/notes, and apply tags in the target sprint matrix. |
| Budget Capacity | Use the Cognitive Capacity Gauge to cap sprint commitments against realistic hours. |
| Enforce Quality | Add Tier 1 Steps for QA criteria before marking tasks ready for execution. |
| Track Hours | Use the live stopwatch and prompt to log time immediately upon task completion. |
| Client Billing | Export timesheet CSVs filtered by project for transparent invoicing. |
| Sprint Close | Use 1-Click Rollover to cleanly archive completed sprints and carry forward loose ends. |
Related Guides & Deep Dives
- Planning Studio & Agile Sprints: Full technical walkthrough of dual-pane triage, split dividers, and capacity budgeting.
- Corp & Project Admin: Governance, multi-project workspaces, pooled licensing, and audit logging.
- Time Recording & Timesheets: Eliminate time leakage, configure categories, and export audit-ready reports.
- Collaboration & Projects: Foundational team sharing, member permissions, and async task comments.