http://en.wikipedia.org/wiki/SCRUM
scrum software development.
it's a lot more interesting that the UML which, for christ sakes, as i've been reading this crap, all i can think is, and some of these people on lbo think judith butler and the po-mos just make shit up to make it sound important. obviously, you have never read Rational Unified Process and the Unified Modeling Language.
*rolls eyes*
i mean, i'm sure some of it's useful. in fact, in really complicated software, no doubt RUP and the UML are incredibly useful. but man, applied to Web-based applications and freakin' web sites? It's a little much.
maybe it's just that i tend to be organized, but a lot of this stuff, it's like security blankets for people or something. put it all in a lot of overstuffed process and imagine that clinging to your process will make it all magically work.
talk about bandaids on gangrene.
today i had to fill out something asking me about requirements docs. why do they suck so much was the basic point of the questionnaire. because they are all based on some standard someone came up with 107 years ago, and everyone uses that standard, and no one really knows why it's a good idea to use a template for writing a master's thesis.
So no one asks: maybe they suck coz they suck! maybe it's the freakin' template everyone uses without! maybe it's b/c product developers often never worked in the trenches, coding. maybe it's b/c getting to the part -- what you freakin' actually have to code -- requires scanning through layers upon layers of total bullshit!
all i can think of when i read those things --and sadly, i've written them -- is an undergrad padding her paper to make it look important! fluff.
it's the cwayzee.
i sat in a meeting today and everyone was all freaked out about this big project that suddenly came down the pike. oh no! it's going to throw everything off. oh noes! it was pages and pages of excel spreadshet to change practically nothing. so there was all this la dee fuckin doo da because no one brought it right to the developers to find out what had to be done.
people without klewXfour, though, they were certain -- partly also because they never bothered to read the fucking document to see that the changes were negligible -- that it was going to be Hyoooooooooooooge! oh noes oh noes oh noes.
and of course, if you acknowledge at all that it might not be so hyooooooooooooge, well.... the deal is, you learn really really quick that you never, ever do that -- because you will pay the price for that.
and you'd think it's just some peculiar dysfunctionality, but it's not. you hear the same complaint everywhere. you learn the same lesson: never educate them that it's not as hyooooooooooooge as they think it is.
it's teh cwayzee.
http://cleandraws.com Wear Clean Draws ('coz there's 5 million ways to kill a CEO)