The methodologies behind FoundStep, defined plainly.
FoundStep is a methodology for solo developers and indie teams who lose releases to scope creep, not bad code. Each concept below names one practice, shows how it differs from the usual approach, and links to a longer writeup.
Scope Locking is a project management methodology where a project's feature set and task list are frozen after planning. Any addition requires an explicit unlock action with a mandatory written justification, creating a permanent audit trail of scope changes.
Shame History is a permanent, immutable record of every scope change made during a project's lifecycle. Each entry captures what was changed, why, and when, creating an undeletable accountability trail that discourages casual scope creep.
Most solo projects fail at scope, not code. The feature list grows mid-build, the original plan stops matching reality, and the release date slips until the project dies in your repo. FoundStep treats that as a process problem. The fix: lock the scope after planning, and log every change to it for good.
Each concept on this page names one piece of that system. Scope Locking is the rule. Shame History is the log. Together they pull the discipline off your shoulders and into the workflow, so staying on scope doesn't depend on willpower at 11pm on a Tuesday.
Each concept covers a different stage of the build. Together they keep you honest about scope from plan to ship.
| Concept | Stage | Role in the lifecycle |
|---|---|---|
| What is Scope Locking in Project Management? | Planning | Freezes the feature set after planning so any addition needs an explicit unlock with a written reason. |
| What is Shame History in Software Development? | Accountability | Logs every scope change permanently so unlock decisions stay visible months later, not just in the moment. |
Quick answers about the methodology and how it sits next to the frameworks you already know.
FoundStep wires Scope Locking and Shame History into the project from the start, so you don't have to remember to enforce them. Read the deeper writeups or try it on your next build.