Introduction
•	Principles
•	Impact on software process
Principles
•	Deliver valuable software "early and often"
•	Why doesn't "go straight to programming" satisfy this?
•	"often" -- 2 weeks-2 months
•	Expect and profit from change
•	Collaborate with customer
Principles
•	Need motivated team members
•	What do you think happens if they are not motivated?
•	Members organize themselves
•	Face-to-face communication
•	Management needs to provide space for this
Principles
•	Maintain same pace of progress at all times
•	How does this compare with the stereotype of software projects?
•	Everything produced should be of high quality
•	"It works" is not good enough
•	Team reviews and improves its practices regularly
Impact on process
•	Do not skip modeling, but use it to understand
•	Diagrams are for what is difficult to design
•	What makes a program component difficult to design?
•	Tools are less important 
•	usually do not need permanent record
•	ease of drawing and sharing make whiteboard more useful
Impact on process
•	Ex: how does Extreme Programming's "pair programming" follow agile principles?
•	What are the advantages?
•	Does this contradict "early and often" production of valuable software?