Electronics > Projects, Designs, and Technical Stuff
How do yo limit feature creep?
technix:
--- Quote from: DaJMasta on January 25, 2020, 04:21:15 am ---Split it into a new project or consider the first one done and this one with the extra features to be the sequel.
The problem with feature creep is that you get too much going on at once and there are too many places where things can go wrong for it to be practical to troubleshoot or deal with, so if you're doing a more iterative design and adding features, it's not really an issue.
In your example specifically: if each version was its own board that was assembled and tested, I'd say it's no feature creep at all and is instead a design building off earlier ones. If all three versions made it to the schematic/layout stage but weren't actually built and tested, yeah, that would be pretty massive feature creep.
Just gotta define what you want to do and actually do it. If that proves less than you want overall, nothing wrong with adding more or making it more complex- so long as the first version is done. The risk with feature creep is that you add so many things at once that you can no longer really manageably make the thing work.
--- End quote ---
I have built, tested and used the first two versions each for a few months. The whole "bugs found in first revision" thing originates from me testing the fully assembled board of the first revision. The third version is now in JLCPCB pipelines.
obiwanjacobi:
You define a Minimal Viable Product (MVP) - with any less features the product would be useless.
That is your version 1. All new-ideas are written down for next versions. Only if show-stoppers are encountered (the design doesn't work, the part is unavailable, etc.) you change it. No 'it will be handy for future extension' add-ons, nothing. Just your MVP.
Also set a reasonable time limit. Not so tight you will have to rush things and cut corners (some corner cutting is allowed) that you get yourself in trouble, but don't take forever. Work in iterations of 2 or 3 weeks. Plan one or two iterations ahead.
This doesn't mean that you ship version 1. It only means that you have something that works. The next version may add features to distinguish your product in the market. Define what that is and do only that. Repeat.
[2c]
tkamiya:
My personal projects are never DONE. There's always something to fix, change, improve, experiment, etc, etc, etc. That's how I often end up with heap of parts and an extra hole or dozen on front/back panels.
My Rb + GPS project is in second generation + few modifications. Already has 6 extra holes on bottom panel.
thinkfat:
My personal projects are done when I get bored with them or when they become so useful that I don't want to change anything anymore for fear of breaking something.
Recent stuff:
- Garden irrigation system - done, because it's in service and I don't want to mess with it any more.
- Connector board for a LPRO-101 Rb standard - done, boring
- Connector board for a Samsung UCCM GPSDO module - done, waiting forever to be put in a real case to make it useful, but superseded by the next project:
- DIY GPSDO board for a LPRO-101 Rb standard. That's what I call feature creep. I started with a simple power connectort hat is about to become a full-blown GPSDO.
:palm:
I wanted a rude username:
More philosophically, when you find yourself planning how to fit another feature in, stop and make some tea and think about what else you could be doing with your most valuable possession ... time.
When you realise you can create five cool little single-function projects in the time you would spend adding functionality to one project, it really changes your perspective. ;)
Remember the Pareto principle: 80% of the utility comes from 20% of the work.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version