Requirements

Defining the Problem

"Stating the problem clearly is half the solution"

• Some Great Developer

Scope Creep

It is easy to begin a project with a certian scope and budgeted resources, and then, through time, allow the scope to creep and expand while the resources aloted to it remain the same. This is an undesireable outcome that tends to happen due to poor articulation of the scope from the outset.

Signoff

Requirements must be signed off by all parties involved.

This process should be iterative and increasingly time intensive:

1. Back of the Envelope (quick and vague)
2. Excalidraw Sketch up(easy and rough)
3. Figma Deisgn (comprehensive and clean)
4. Code (difficult and quasi permanent)

Caring and Preciousness

If one cares, your ideas are precious to you. But* when working in a cohort/group/team, changes for different reasons (preference or logistics) are enevitable. Often between this step and compoletetion, idividuals can become too atatched to their precious ideas / work. This doesn't help anyone and is immature. The trick is to care patiionatily, and with a detached utilitarianistic furver, pivot or expand or change or redact or undue or ... whatever the projects needs.

The reminder is: Serve the ideal of the project not the preciousness of your original work.