3 ms·
I'm in this exact position. Brought up in a startup with CTO role to build a complex piece of visual storitelling software. A thing that miss from the list of
by LoSboccacc 11y ago
I'm in this exact position. Brought up in a startup with CTO role to build a complex piece of visual storitelling software.
A thing that miss from the list of competency is to fight thoot and nail feature creep.
We just released our mvp within a week of the estimate and it was hard to fight back all the 5 minutes types of addition that came to mind to everyone on the project.
A mvp is also an idea factory and over excitable folks will be gmtempted to add loads of stuff before user validation which kind of defeats the whole scope of it
- fit2rule 11y agoFeature Creep means you've got a broken development process - most likely in the area of writing and approving requirements, and reviewing requirements, and so on. Never work on a project where the requirements aren't written, using a standard form and language - and never, ever, accept a verbal request for a feature - get it into a tracking system so that it can be formalized.
- LoSboccacc 11y agoDoesn't really apply to my position tho. I'm the one helping defining and shaping those. Heck the whole thread is about starting from zero at the point the mvp is slight more than an idea.
- fit2rule 11y agoBut that's the point: going from zero (idea) to implemented (software) requires a few steps along the way, and imho one of those very important steps is the proper administration of requirements specifications in such a way that feature creep doesn't happen. I know its not easy: thats why its important.
- deleted 11y ago[deleted]