This web page is associated with a book called called Hermeneutics in Agile Systems Development.
The book can be bought at: https://play.google.com/store/books/details/Dr_Jerome_Heath_Hermeneutics_in_Agile_Systems_Deve?id=mi6VBQAAQBAJ
The book gives a more complete explanation of these issues and includes a number of related topic discussions. The combination develops the understanding of the concepts of Agile software development.
Do you want to know how software is developed?
Agile is the new world view of systems development. Structured design is now relegated to systems that have a short development time, the way to develop the software is already known (there is no need for design), and the system will not change in any way during the design.
Agile methodologies have been developed over time from developers experiencing success by rejecting the ideas of the structured methodology and the waterfall style of project management.
The main strengths of Agile methods are:
Visibility (through the looking glass)
Adaptability (context calculus)
Business Value (incrementally increasing the value)
Less Risk (changes are made on a Just In Time bases)
The biggest problems with the waterfall techniques are:
Risky and expensive.
Inability to deal with changing requirements.
Problems with late integration.
Always required extensive rework to make software usable
Business advantages of Agile development:
Benefits can be realized early.
First to market and early and regular releases.
Testing is integrated so there is early recognition of any quality issues.
Excellent visibility for key stakeholders ensures expectations are managed.
Customer satisfaction through project visibility customers own the project.
Incremental releases reduce risks.
Change is accepted, even expected.
Cost control - the scope and features are variable, not the cost.
Developers feel that they are part of the project and enjoy doing the work.
In agile development ou are using post-modernist methodologies. Agile is post-modern or post structural. Agile was designed to set aside the structured approach. That goal was the exact goal of post-modernism. Agile and quality-productivity are the most effective post-modernist movements.
Through the Looking Glass Worldview
Through the Looking Glass
In the book “Through the Looking Glass” Lewis Carroll is expressing fantasy but also he is picturing how to view parallel worlds. Now, although most parallel worlds are virtual (like the looking glass), not all of them are. My father insisted that Lewis Carroll was referring to nuclear physics when he wrote the book. So, it was then some kind of prophesy of the future. If you see the book as a study of parallel worlds then it could refer to nuclear physics as well as to the world of computer systems. To some extent all literature is a parallel world.
So can we develop a mathematics of parallel worlds from such a beginning? On the basis of the book we start with a rough trail; it is not quite a road yet. Of course, the whole concept and the advantage of starting where the book left off is: through the looking glass is a commonly understood parallel world.
The point of the book is that when you go through the looking glass, some things are reversed; and other things are just skewed. The world of “through the looking glass” has some similarity to the “regular” world. But we are often surprised by the things that are different. So we begin our study of the parallel worlds of computer systems analysis and development by examining the effects of going through the looking glass; the study of the difference between the regular world and the virtual world. We hope to see a mathematics that gives us a meaningful understanding of the world of system development.