necessary eval
devx / note / 1 min read

MoSCoW Method of Software Proposals

MoSCoW method

Feature creep is a real thing. It’s pretty hard to present any technology proposal
to a group of engaged engineers without large “blue sky” converstations starting.

The MoSCoW method gives you four one word classifications that will make your intentions clear.

  • MUST - we will build this now
  • SHOULD - not committed to
  • COULD - not planning on it
  • WON'T - not doing

The wiki page is so good that I’m just going to link to the MoSCoW method.

related
devx secrets terraform terraform state secrets note 3 min

Terraform Secret Placement

Terraform has its strengths and its challenges. Of its strengths, Terraform gets you referential integrity, reproducability, and a rich set of clients with great documentation. One of its challenges includes keeping sensitive secrets out of…

devx environment venv note 3 min

Know Your Binaries

It’s pretty hard to be clever if you’re an executable file. Understanding how your programming interpreter views the world can save you days of development time and release you from the perils of virtual environments. After you hand your…

devx vim editor note 4 min

Scripting Editors: It Doesn't Have to be VIM

Putting a pin in the text editor holy war – do you use VIM, or Emacs?! We may point out hipster tendencies by using these “way better” vintage technologies, but there is still extreme value here. What you’re missing out on is having…

necessary eval / pragmatic technology and leadership notes · rss © 2026
type to search titles, summaries, topics, and article text.