1
/
of
1
Jerome Heath
Hermeneiutics in Agile Sytems Development
Hermeneiutics in Agile Sytems Development
Regular price
$39.99 USD
Regular price
Sale price
$39.99 USD
Shipping calculated at checkout.
Quantity
Couldn't load pickup availability
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 you 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.
Agile methodology sidesteps the structured and the detailed documentation part of a project. The concentration is on people: first the customers, then the developers. Structured methodology was trying to use "hard science" principles in code development. But users could not understand the science part of the process. So the users were asked some questions (by different people than the ones doing the coding) and then the team went into hiding. They had to develop the code without user interference since the user would not understand the science of the process. The code was developed in black box mode. Each module was a black box; the code was secret to everyone but the coder – the only requirement was that the code was to do only and exactly what the specs called for. Also the process requires extensive documentation. The black box and back room process is ripe for some kind of sleight of hand so the process needs extensive documentation; to prove the work was done scientifically.
The structured methodology was always behind schedule. With structured methodology the users or customers were always less than satisfied. Actually the code was always a surprise compared to what they expected. The back room and black box methodology would guarantee that kind of surprise.
Dr. Jerome Heath, Ph. D.(Also see books by Dr. Jerome Heath:
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 you 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.
Agile methodology sidesteps the structured and the detailed documentation part of a project. The concentration is on people: first the customers, then the developers. Structured methodology was trying to use "hard science" principles in code development. But users could not understand the science part of the process. So the users were asked some questions (by different people than the ones doing the coding) and then the team went into hiding. They had to develop the code without user interference since the user would not understand the science of the process. The code was developed in black box mode. Each module was a black box; the code was secret to everyone but the coder – the only requirement was that the code was to do only and exactly what the specs called for. Also the process requires extensive documentation. The black box and back room process is ripe for some kind of sleight of hand so the process needs extensive documentation; to prove the work was done scientifically.
The structured methodology was always behind schedule. With structured methodology the users or customers were always less than satisfied. Actually the code was always a surprise compared to what they expected. The back room and black box methodology would guarantee that kind of surprise.
Dr. Jerome Heath, Ph. D.(Also see books by Dr. Jerome Heath:
Share
