Methodologies: Waterfall · Agile · MVP
A methodology is how you arrange SDLC's phases in TIME: Waterfall runs all phases in one big pass; Agile compresses the same cycle into short, repeating iterations, each ending with a working piece. Why: the fatal disease of solo projects is "I'll build for 2 years, then show it" — Agile + MVP is the vaccine. Your Samevian is already moving in iterations (v1.0 -> v2.0, Phase 1 -> Phase 3). When: planning a project, at the moment of "let's do everything at once" temptation, prioritizing a backlog, in an "I'm tangled up, what do I do first" state. How: Waterfall — 1->2->3->4->5->6 ONCE, over months. Agile — pick a small piece -> a mini-cycle in 1-2 weeks -> a working demo -> feedback -> the next piece. Where: Waterfall where requirements are set in stone (a bridge, aviation). Agile — almost everywhere in software, especially solo and startup work. Who: in teams, a PM/Scrum master runs it; solo, it's you managing yourself — discipline replaces the manager.