which did more for womens rights; the gals that stood at the picket lines (or whatever it was at that stage through the century) protesting and refusing to shave their armpits...
Hey, stop right there, I'm already on the side of the armpit shavers.
A lot of people say that extreme apathy (XA) is too fringe and would never work in their organization, but it's really working in our shop.
The XA planning game, where you get a bunch of blank cards and never get around to writing anything on them or talking to the customer about them, really keeps us on track or whatever.
And I never thought I'd get used to pair apathy, but it turns out my partner and I don't really care one way or the other.
You could look it all up on some wiki somewhere, I forget. Google it or something.
Wait, is this not a methodology thread? Meh, no biggie...
It's hard to recommend something without knowing what your typical project size is. You want to run something that'll take 500 staff hours of effort much differently than something that'll take 5000 staff hours... or 50, or 50,000.
And what's your key objective? Do you need to show something by December 1, or can you project any date as long as it clears a well-defined quality test on that date?
What's your need for accurate tracking of progress? Do you need to tell people something believable every week about when they can expect the THING that they've ordered, or can you just say "we're working on it, and we're somewhere in the middle?"
All that said, the approach I've seen work the best is an email folder, a spreadsheet, and a brilliant dedicated experienced person who kept it all in her head and spoke the right language to everyone concerned. Get whatever tools you want - as long as the craftsmen are right, everthing else will be fine...
Slashdot Mirror
I think you can get the 8'10" chick from Amazon.
... someone is reading a logfile and saying "wtf???"
Smart move keeping the site simple - serve it up, IIS!
A lot of people say that extreme apathy (XA) is too fringe and would never work in their organization, but it's really working in our shop.
The XA planning game, where you get a bunch of blank cards and never get around to writing anything on them or talking to the customer about them, really keeps us on track or whatever.
And I never thought I'd get used to pair apathy, but it turns out my partner and I don't really care one way or the other.
You could look it all up on some wiki somewhere, I forget. Google it or something.
Wait, is this not a methodology thread? Meh, no biggie...
Please god tell me it's not purple...
"I love you, you love me, I'm robot se-cur-i-tee..."
For some dumb reason, I didn't check the apple section before submitting this one... perhaps because I didn't submit it to the apple section...
Thought it was interesting, as I code for the Microsoft world and am never against having more options.
Please, go back to whatever usually goes on here, and pardon the repetitive redundancy.
Oh, for the love of God.
Cask, dammit, cask!
It's hard to recommend something without knowing what your typical project size is. You want to run something that'll take 500 staff hours of effort much differently than something that'll take 5000 staff hours... or 50, or 50,000.
And what's your key objective? Do you need to show something by December 1, or can you project any date as long as it clears a well-defined quality test on that date?
What's your need for accurate tracking of progress? Do you need to tell people something believable every week about when they can expect the THING that they've ordered, or can you just say "we're working on it, and we're somewhere in the middle?"
All that said, the approach I've seen work the best is an email folder, a spreadsheet, and a brilliant dedicated experienced person who kept it all in her head and spoke the right language to everyone concerned. Get whatever tools you want - as long as the craftsmen are right, everthing else will be fine...
Or, y'know, not. Good luck, comrade.
Priorities, folks, let's focus...
No kidding. It seems Henry was sorta wacky that way.
Carry on. I'll edit as required.
Shakespeare for me, of course.
And yes, I've read it in the original Klingon.
Um, if you need your last-minute heroism... it wasn't a remarkably potent design, now was it?
... can't they just put newer, smaller, niftier satellites about ten klicks behind the first one in its orbital path?
Isn't all the money spent just getting there?
It would have killed you to mention "oh, btw, here's the screenscrape of the text linked"?
"Aren't", dammit, "aren't"!!!!
How are they going to graduate well-rounded people who still want to be engineers?
Spent all my mod points
Next story, haiku challenge
Taco is so cruel