Reviews -What it signals?

I am sure it signals a long proces and time.
I heard and also said many times. :) We are agile and we need a working application not processes.
Will the working pice of applications will suits to customer requriements? how do you validate?
Don't you think reviews what validates standards followed during development?

Reviews are done at different levels and areas.
Each one will enhance the application targeting a specific area.
I could see these many reviews which will add value for an applications which will win customer's heart.

Techincal Reviews
Application maintanance
Perforamcne
Techincal Archtecture
Enterprise integration
Coding and design
Security Reviews
Application Usability reviews
Application Branding standards
Copy Rights Review
User interface reviews

Each one of the above is done by different experts. These will ensure the product would stay in the market quite a long period.

Importance of code reivew in agile development

Code review is essentially vital part for agile development and it must be done along with our code coverage.
Code review has a great potential to reduces bugs count and increases the productivity on long run.
It provides quality code in terms of
1. following coding standard to make sure everyone understands your coding.
2. identifying bugs development stage reduces the number cycles between dev, qa or even from production to development.
3. catching performance bottle necks like loops, memory leaks, reducing unnecessary costly calls to db and so on

Code review will really gives you more learning and it multiplies your knowledge as you become aware on how other person think and code.
You must feel great to get your code reviewed to make sure you're strong in your delivery by using another pair of eye to catch any unwanted things that you don't want to put in to code base.
When you get comments on your code, your confidence level on your coding style increases and you become quality coder.