It could be understood and done in style "let"give user slightly alive something and let him test that for us". And that way is really very dangerous and bad practically in any way.
The analogy could be: Cargo-cult. When wild tribes after a US base moved away in 1945 built a model of a plane of sticks and leaves and thought that its spirit will bring them prosperity. The main problem: they do not know what this thing is for and really don't want to know. They have their own ideas and are happy with them. It is a simulation of work.
But if the target was not to give slightly alive something to user as fast as possible, but:
- to give him a piece of real work as fast as possible, already supported for invisible for user but helpful for authors tools such as automated testing and logging.
- if that piece already gives user some undestanding about how the whole future product will be worked with
- to repair problems and add further features with as fast reaction as it is possible, with product remaining solid and sound
then it is very good way in REAL agile style.
Analogy for that case is: A client has ordered a new model of some technical machine.
- He gets pictures how that machine could work.
- He gets an armchair of the driver.
- He gets the armchair with all levels and controls faces around it
- He gets carrosery with wheels and motor and simplified driver place for movement only, without special apparature controls - to check how it moves
- The real work places is mounted on the carrosery .... And so on. - up to the ready product.
And on every stage the work could be solidly checked and the client and the producer can correct former mistakes.