XP Context

Why XP is considered extreme?  Since I don't know what the
traditional development methodology is like, I don't quite understand what
are the major differences  between XP and traditional development
methodology. [Kyung]

How much of XP are we already being taught as part of the standard
curriculum at Grinnell? Is XP a fairly standard paradigm in the CS
industry? [Tim]


Agility

"Driving is not about getting the car going in the right direction.
Driving is about constantly paying attention, making a little correction
this way, a little correction that way." (pg 11) [Alex]

"Stay aware. Adapt. Change." How is this important to XP specifically.
[Pat]

I feel like the internet is the foremost factor in the issue of "vague and
rapidly changing requirements". So exactly how has it made requirements
so hard to pin down, or else what might also be contributors to this?
[Jay]


Creating value

On that, the quote on page 3 was one of the first things to strike me:
"In XP you only do what you need to do to create value for the customer."
Many of the practices we learned in OOAD created value for the customer,
but could have been left out and still had value; does this quote imply
to try to get software to the customer ASAP without having a cohesive
design process? [Andy]

Priority to business? Ladies and gentlemen, are we in the right
department? [Rick]


Coping with others

we could discuss how to go about making the best of bad situations.
What do you do if your boss(es) don't understand XP and aren't cooperative
about implementing it?  What do you do if your bosses get it, but your
partner really doesn't? [Alexi]

"You can't control others' expectations... My terror of deadlines vanished
when I learned this lesson. It's not my job to "manage" someone else's
expectations." (5) [Saul]


Values

What values have our CS professors at Grinnell tried to instill in us?
[Heather]