2 ms·
IMO the problem with software methodologies is leaky abstraction. There just isn't a general framework that tells you how to categorize and deal with every iss
by lordnacho 8y ago
IMO the problem with software methodologies is leaky abstraction.
There just isn't a general framework that tells you how to categorize and deal with every issue that you come up with.
The main thing I get from the various methodologies is general philosophies. Things like "try to get feedback incorporated quickly". Or "Identify in advance the things that are expensive to change".
- aswanson 8y agoSoftware in the abstract problem solving against varying constraints. It stands to reason there would not be a single method that capture the best means of doing so.
- pytester 8y agoI kind of wish we applied "micro-methodologies" rather than methodologies. I think we should be doing "import retrospectives" rather than "import scrum" and sharing and experimenting with a diversity of approaches (e.g. various different ways to do retros). We're essentially treating "methodologies" as software that runs teams. Furthermore, if we are doing software we should follow the UNIX philosophy and the bazaar rather than the cathedral. Edit : I kind of want to make this a reality now. I've registered http://micromethodology.com http://micromethodology.com and will make it so micromethodology.com/standup can be a place to share "how we do [x variant] standups" via pull requests on https://github.com/hitchdev/micromethodology.com https://github.com/hitchdev/micromethodology.com