values Individuals and interactions over processes and tools

values Working software over comprehensive documentation

values Customer collaboration over contract negotiation

values Using specific processes, procedures, or best practice 

values Responding to change over following a plan

values Using a rigid framework

So that each team member can say What did I work on yesterday? What am I working on today? What issues are blocking me?

Improves shared goals across the team

So that everyone know what each person in the team is doing

Build and improves collaboration and communication

Team members can see if they can help others, if there is a need

Because it's easier for clients to if the system is what they want from actually seeing what has been developed, or what is being developed rather than documents or models.

Because they are part of the team.

There is no need, the client will see what has been completed at the end of the project.

in case new requirements or changes in the business environment have come up and then they can be added even though the iteration isn't finished.

in case priorities have changed, since the last time you saw your client.

just assuming the the way it's  always been done is the best way.

 just automating existing processes without thinking too much about whether or not that process is effective or efficient.

 helping find the best dependency path of tasks to be performed

looking for problems  in analysis that may affect the development path