Requirements Planning with MoSCoW & Brainstorming

1. Why Separate Ideas from Commitments?

Every software project, team initiative, or client deliverable starts with a flood of ideas:

• Customer feature requests and feedback emails
• Improvements noticed during testing
• Creative shower thoughts and "what-if" suggestions
• Technical debt and refactoring ideas

If you drop all these raw ideas directly into your active daily to-do list, two bad things happen:

1. Daily Overwhelm: Your task board fills with hundreds of speculative ideas. Real daily priorities get buried, and the AI coach nags you about tasks you had no intention of doing this week.
2. Scope Creep & Broken Deadlines: During planning, teams often treat every good idea as something they have to build right now. Without clear boundaries, releases drag on for months.

DoneIsGood gives you a clear, structured pipeline:

flowchart LR
    A["Raw Ideas & Feedback
(Unmanaged Matrix)"] -->|"Planning Studio
Hour Budgeting"| B["Milestone Scope
(MoSCoW Matrix)"]
    B --> C["[M] Must Have
(Non-negotiable)"]
    B --> D["[S] Should Have
(High value)"]
    B --> E["[C] Could Have
(If time permits)"]
    B --> F["[W] Won't Have
(Future cycle)"]

2. Step 1: Set Up an Unmanaged Ideas Matrix

Start by creating a matrix to hold your backlog and brainstormed thoughts.

1. Click + Add Matrix in the top navigation or sidebar.
2. Name it something clear, such as "Product Backlog" or "App Ideas".
3. Click the matrix settings gear icon (⚙️) next to its name to open Matrix Properties.
4. Under Management Mode, choose Unmanaged / Ideas & Backlog:

[ ] Actively Managed Matrix (AI coaching, alerts, and digests enabled)
[x] Unmanaged / Ideas & Backlog (Muted: no alerts, coaching, or digests)

What "Unmanaged" Means in Practice

• No AI Nagging: The AI Advisor will not suggest working on these tasks during your daily check-ins.
• No Overdue Alerts: You will never receive push notifications, red badges, or email reminders for parked ideas.
• No Daily Digest Clutter: These items stay out of your morning briefing.
• Open Capture: Anyone on the team can add tasks, voice notes, or checklists anytime without worrying about mess.

3. Step 2: Create Your MoSCoW Milestone Matrix

When you are ready to prepare a sprint, release, or client milestone (for example "v2.0 Release" or "Q4 Website Redesign"), create a dedicated delivery matrix.

1. Create a new matrix named for your target release (e.g. "v2.0 Scope").
2. Open its Matrix Properties (⚙️).
3. Under Board Layout & Methodology, select MoSCoW:

( ) 📐 Eisenhower Matrix (Do, Schedule, Delegate, Delete)
(x) 🎯 MoSCoW Matrix (Must, Should, Could, Won't Have)
( ) 📋 Kanban Board (To Do, In Progress, Done)

Your board immediately updates its 2×2 grid into the four standard MoSCoW quadrants:

4. Step 3: Use the Planning Studio for Side-by-Side Scoping

Rather than dragging tasks one by one across screens, open the Planning Studio (✨ Planning in the top bar).

The Planning Studio gives you a dual-pane workspace:

• Left pane (Source): Choose your unmanaged "App Ideas" matrix.
• Right pane (Destination): Choose your "v2.0 Scope" MoSCoW matrix.

+------------------------------------+------------------------------------+
| SOURCE: App Ideas (Unmanaged)      | DESTINATION: v2.0 Scope (MoSCoW)   |
|                                    | Capacity Budget: 40h [=======   ]  |
| [ ] User login with Google (2h)    | [M] Must Have (18h)                |
| [ ] Stripe checkout flow (6h)      | [S] Should Have (10h)              |
| [ ] Dark mode toggle (3h)          | [C] Could Have (6h)                |
| [ ] Export data to CSV (4h)        | [W] Won't Have (this time) (12h)   |
+------------------------------------+------------------------------------+

1. Estimate Hours Rapidly

Click the duration pills (30m, 1h, 2h, 4h, 8h) on each candidate task. Accurate estimates make realistic planning possible.

2. Drag or Batch Move Tasks

• To move individual items, drag a task card directly into the Must, Should, Could, or Won't Have box on the right.
• To move multiple items at once, select their checkboxes on the left and click ➡️ Must (M), ➡️ Should (S), or ➡️ Could (C).

5. Step 4: Balance Scope with the Cognitive Capacity Gauge

As you move requirements into your MoSCoW quadrants, watch the Cognitive Capacity Gauge at the top of the destination pane:

• Green (< 80% capacity): You have healthy buffer room.
• Blue (80% to 100% capacity): Your sprint is fully booked.
• Amber / Red (> 100% capacity - Overcommitted): You have promised more hours than your team or sprint budget can realistically deliver.

How to Fix Overcommitment

When the gauge turns amber, you do not need to delete ideas or panic. Use the MoSCoW method:

1. Review your Could Have [C] quadrant.
2. Drag tasks from Could Have down to Won't Have [W].
3. If still overcommitted, check your Should Have [S] quadrant and agree on what can be safely postponed.
4. As soon as the gauge drops back into the blue or green range, your scope is locked and achievable.

6. Step 5: Executing the Milestone

Once planning is complete, close the Planning Studio. Your team can now work directly from the MoSCoW board in Matrix View or List View:

1. Focus on Must Haves First: The team tackles Q1 ([M] Must Have) tasks before anything else.
2. Move to Should Haves: Once the core non-negotiables are stable, start work on Q2 ([S] Should Have).
3. Finish with Could Haves: If you finish early, pull in Q3 ([C] Could Have) items as time allows.
4. Hold the Line on Won't Haves: If stakeholders ask for new bells and whistles mid-milestone, point to the agreed Q4 ([W] Won't Have) list and schedule them for the next planning cycle.

Summary Checklist