speaker is C. Daniel Chase from UC Boulder

presentation is more philosophy and concepts than technical details

get feedback constantly, build it around motivated individuals, business and developers work together daily

emphasis on face to face conversation = one large room with all the programmers

working software primary measure of progress

I wish I had a separate office

daugustine, I think that's a huge point. I wonder who determines when it is 'working' developers, or end users?

it's hard to say, "working" to me as a developer means something different than "working" to an end-user

many times, if an end user doesn't know how to use an application, they think it's non-working

www.agilealliance.org/

daugustine true

Scrum has been thrown around within the CBA Dev team in the past 4 years because we tend to approach projects without emphasis on structure.

advocating source code management

Don't think we truly have all the characteristics of Scrum.

saltybeagle, related to this session, what was that University Newsroom site we saw that was so good?

Version control, release tracking, development vs production code lines

We are working on release tracking. How many builds inclement a version or sub-version

or do you do it by features or components added?

almostcool news.ncsu.edu/

emphasizing Test Driven Development, Unit Testing and Functional Testing

when we complete our newworkspace, face-to-face coding meetings will be more possible.

Ruby on Rails has behavior testing where it runs the test, does the ajax call for json/xml (test the response)