How Healthy Is Your Scope on a Startup Software Project? A Self-Assessment for New PMs
A ten-question self-assessment for individual contributors evaluating scope health on a startup software project — to surface expansion before it forces a date slip.
Ten questions that tell you whether the schedule will hold
New PMs on startup software projects are usually the first to feel scope expansion and the last to be authorized to act on it. The assessment turns the feeling into evidence.
Individual contributors on startup software projects often sense that scope is expanding before they have evidence to act on. This self-assessment converts the sense into a score, which is what the founder needs to authorize a corrective.
Score honestly. Each yes is one point. The total places your project's scope health in one of three tiers, each with specific next moves.
Ten questions, 1 point per yes
0 / 10- Does the project have a written scope baseline that hasn't been edited in the last 30 days?
- Has every backlog item added in the last 30 days been explicitly approved by a single named decision-maker (founder or senior PM)?
- Is the original launch date still the planned launch date?
- Can you list the project's top 3 outcomes from memory, in the same words the team would use?
- Are 'while we're at it' additions being declined more often than accepted?
- Does the team have a dedicated scope review meeting (weekly or biweekly) separate from execution standups?
- Has the founder seen the current backlog in the last 14 days?
- Is the difference between 'must have at launch' and 'nice to have' written down somewhere?
- When a stakeholder asks for a feature, does the team have a way to defer it explicitly (not just 'we'll see')?
- Has the schedule been re-validated against current scope in the last 30 days?
How to read your score
8–10: Healthy scope discipline. The schedule will probably hold. Re-run the assessment monthly to catch drift early.
5–7: Typical for a startup software project at month 2-3. The discipline is partially in place, but gaps are letting scope expand silently. The light fix-edition guide is the next read; it's a one-week corrective.
Below 5: Scope is expanding faster than the project can absorb. The corrective is more substantial than the light fix. Start by establishing a scope baseline (question 1) and a named decision-maker (question 2) — those two changes alone usually move the score by 2-3 points within a week and create the conditions for the rest.
The clusters, decoded
Discipline cluster (questions 1, 2, 8, 9). Checks whether the project has the basic infrastructure to manage scope deliberately. A no on question 1 means there's no reference point for what scope was supposed to be; a no on question 2 means no one is making explicit decisions; a no on question 8 means must-have and nice-to-have aren't distinguished; a no on question 9 means stakeholder requests aren't being handled deliberately.
Visibility cluster (questions 4, 5, 7). Checks whether scope is visible to the people who need to see it. A no on question 4 means the team and you have drifted from a shared understanding of outcomes; a no on question 5 means small additions are accumulating; a no on question 7 means the founder is not seeing what's actually being built.
Process cluster (questions 3, 6, 10). Checks whether scope is treated as a managed dimension of the project. A no on question 3 means the date has already slipped; a no on question 6 means scope conversations are happening reactively in standups; a no on question 10 means the schedule's relationship to scope hasn't been re-examined recently.
- TodayScore the project10 minutes. Score honestly.
- Day 1Identify the lowest clusterPick one cluster to address. Don't try to fix all gaps at once.
- Days 2-7Address gaps one at a timeEach gap is a brief conversation with the founder, then a process change. Track which gaps are closed.
- Day 30Re-scoreRun the assessment again. Track the trend.
The assessment is a 10-minute diagnostic. Its leverage is in the conversation it motivates with the founder — converting a vague feeling that scope is creeping into a specific score with specific next moves.
For early detection before the assessment is needed, see spotting scope creep early; for the corrective when the score is low, see the light fix-edition guide; for the parallel WBS-focused diagnostic, see the WBS health assessment.