If your software development team is not following any design methodology, what is that called?
views:
701answers:
34
+11
Q:
If your software development team is not following any design methodology, what is that called?
ADD anarchy driven development
danswain
2009-11-20 18:08:18
+8
A:
"ad hoc" or if you are feeling nice, "minimalist" methods. More likely though, they are following some kind of methodology without being aware of or acknowledging it.
Leigh Caldwell
2008-09-26 17:56:11
Hurrah for a response that doesn't knee-jerk assume that the team is incompetent!
Rich
2008-09-28 22:19:26
+2
A:
chaos? Is it due to leadership, or due to the team itself?
Do any of the programmers fit one or more of these types?
DaveJustDave
2008-09-26 17:56:32
A:
Bad.
Though some would argue that they're just being loose, which usually indicates that the scale of the project has a theoretical limit. Many projects start off as just one-offs that grow and grow. Eventually you'll have to adopt a design methodology to keep the project going.
Orion Adrian
2008-09-26 17:56:41
Funny, but in my experience it was more like "let's have a meeting to discuss whether or not we want to change that 3 lines of code, and to discuss what kind of process should we implement so that we don't have to do that again."
JasonTrue
2009-11-20 18:15:50
A:
Big Bang Theory - That is what I call code that I spend hours writing with no prep/design work and without compiling it until I am done. I try not to do this too often though.
pdavis
2008-09-26 18:43:12
+2
A:
It is called adventure.
No design methodology does not mean no design. So it can be a valid option. But why reïnvent the wheel.
Unfortunately currently we are not using a methodology, but it will be my task in the long run to optimize the development process.
Gamecat
2008-09-26 19:48:33
+1
A:
ADD - Also known as "Ass-hole Driven Development"
Read this classic post from Scott Berkun (and the gazillion other funny acronyms for frequently seen, but not so frequently documented methodologies ;-)
No, this is not offensive... it's a real good eye-opener! Go read it now, you'll love it (I guarantee it)
http://www.scottberkun.com/blog/2007/asshole-driven-development
Johan Pelgrim
2008-09-26 22:21:55
A:
I call it a "Star Trek Mission". You may have some goal in mind, but you spend all your time on small away missions, which don't help you reach your goal. If you stack up too many away missions, you may even forget what your goal is.
bruceatk
2008-09-27 12:07:40
A:
JFDI - just f***ing do it
http://www.orangeandblack.co.uk/software-methodology-jfdi.aspx
pjp
2009-11-20 17:46:35
A:
If you look at it from CMMI levels, this would be maturity level 1. If you can recreate the process, just not in an organized way, then you might be up to level 2. Either way, it probably just means you have an immature organization.
Josh
2009-11-20 17:50:36
+1
A:
Unprofessionalism. At least one of the guys should establish some kind of methodology, even though under the radar of management.
Remember this advice from Joel: Getting Things Done When You're Only a Grunt
JuanZe
2009-11-20 17:55:04
+1
A:
This is called Rapid Application Conception and Heuristic Extreme-programming (La R.A.C.H.E), from the famous International Institute of La RACHE (IILAR). Actually, this is a wordplay in French (La RACHE = l'arrache which means something like quick and dirty) which is of course impossible to translate without loosing the fun part. Obviously, the whole site is a joke and the content is not serious. If you understand a bit of French, you may find it funny :) Below, the typical cycle when using La RACHE:
Pascal Thivent
2009-11-20 18:08:58