7. •
•
•
•
No inflexible and lengthy process with the waterfall project model.
No creation of requirements specifications full of misunderstandings which is already obsolete
by the time the project ends
No need for "perfect specifications"
No media discontinuations
Instead
•
Using the new approach, business users were immediately ableto create their own applications
with simple "real live" modeling entities.
•
Thew new approach immediately generates executable code
•
The results can be experienced immediately
•
The modesl can be changed and adapted at any time, as often as necessary and even during
operation
•
The model from "real live" entities corresponds to the execution 1:1
7
8. •
Five professionals from the business department have learned in just a few sessions how they
can describe their problems more and more precisely
•
Once they understood that they were in the process of building their own applications and that
they would be able to change them as often as they want, they took advantage of their creative
freedom in an ever more productive manner.
•
The approach kept business users encouraged to make more changes and improvements
again and again up to the last minute before the planned GO Live.
8
10. •
•
•
•
Business users see the application as the property they created. There are no acceptance
problems. Users feel they are participants, not affected bystanders.
Asa result of the unlimited amount of possibilities for change ( formal theory, not corruptible)
and the possibility to create their own design, the business users assumed complete
responsibility for the solution.
The understanding and identification of the business department for the solution are at 100%.
Accordingly it will react with due speed to change requirements.
The cooperation Business – IT was not a service relationship any more Instead it was upgraded
to a partnership
10