TL;DR
Fix your process problem, then look again at your available options for automating it.
Don't Violate "CodeGnome's Law"
CodeGnome's Law says:
If you can't do it by hand, then you can't automate it. Automation is a tool to increase consistency, but it is not in itself a substitute for ...
This is the most recent use of the term.
It was originally coined by MarkWallace on November 14th, 2012.
I rather suspect that I would approach this as "tools & techniques to construct work packages". From my limited understanding, a "feature" is nothing more than a work package - a discrete deliverable with schedule & requirements.
I don't know of any software to assist in constructing and mana...
And the law states:
> If you can't do it by hand, then you can't automate it. Automation is a tool to increase consistency, but it is not in itself a substitute for a well-defined process or process control.
This has personally really helped me determine when to automate and when to just keep doing the manual stuff.
Yes indeed. Mark C. Wallace gets full credit for originating the catchy name that labels the core idea of one of my previous posts. The original wording of the law was "Define your process, then automate it." --Maybe that makes the longer quote CodeGnome's First Corollary? How embarrassing if I misquoted myself! :)
I rather suspect that I would approach this as "tools & techniques to construct work packages". From my limited understanding, a "feature" is nothing more than a work package - a discrete deliverable with schedule & requirements.
I don't know of any software to assist in constructing and mana...
