>Programmers, I have a request. Post a comment that says something about agile that is valuable to know in an interview and might also make sense to me.
>
>It isn't a .net interview so general is better

This might not help you at all, but I'm going to summarize my views on Agile. I've seen many shops that implement it (or claim they implement it).

- Not that I'm opposed to Agile, but I see many places that abuse it and use it as an excuse to avoid ANY aspect of the older waterfall methodology. Lack of long-term focus, lack of identifying all the integration points, excessive focus on simple unit tests....leading to excuses at the end that are analogous to "the operation was a success but the patient died". I'm not saying I'm a fan of the waterfall approach, but agile is so badly abused that I'm usually skeptical when people say they use it (especially if I get a strong whiff/stench that they not keeping their eye on the end game)

- The places that take "Scrum" seriously (and realistically...i.e. run by someone with substantial experience) are the ones that seem to implement agile in a positive way with repeatable processes. My two cents, I would study Scrum.

- All participants need to buy into the process. If people look upon sprint meetings or daily scrum meetings with so much dread, they possibly will either minimize what they say (or even be dishonest). Obviously that doesn't help anyone. If team members doesn't realize that a Scrum process can help them in their focus, it's not going to work.

To borrow from the assertion of my political affiliation, I'm agile with a little 'a', not a big 'A'. <s>

You might want to send a message to TCH, who (I believe) has substantial experience in this area.