splits

"Give yourself permission to ship something you know isn't right." — @w 

Anything else is too slow! The polish comes later.

Start with a functional prototype. It should be rough. It should be janky. Get that version in front of users fast.

How we scope a quick 'n' dirty MVP at Splits:

1) List everything that might important or relevant to the project.
2) Okay, now what is the *absolute minimum* from this list that's necessary for a functional prototype?

AFTER completing this "make it work" phase, you can start fixing the glaring flaws, fulfilling feature requests, and optimizing performance.

"Give yourself permission to ship something you know isn't right." — @w 

Anything else is too slow! The polish comes later.

Start with a functional prototype. It should be rough. It should be janky. Get that version in front of users fast.

How we scope a quick 'n' dirty MVP at Splits:

1) List everything that might important or relevant to the project.
2) Okay, now what is the *absolute minimum* from this list that's necessary for a functional prototype?

AFTER completing this "make it work" phase, you can start fixing the glaring flaws, fulfilling feature requests, and optimizing performance.

https://splits.org/blog/make-it-work-make-it-right/

internet rabbit • comms @ /splits • https://www.sonyasupposedly.com/