UnitXP: Difference between revisions
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
* [[:en:Extreme Programming|<b>XP</b>]] | * [[:en:Extreme Programming|<b>XP</b>]] | ||
| | | | ||
* [[:en:Pragmatic Programmer| | * [[:en:Pragmatic Programmer|Pragmatism]] | ||
* [[:en:Software Craftsmanship| | * [[:en:Software Craftsmanship|Craftsmanship]] | ||
|} | |} | ||
<html><iframe src=/AkStore2/custom/UNITXP.html width=98% height=1750></iframe></html> | <html><iframe src=/AkStore2/custom/UNITXP.html width=98% height=1750></iframe></html> | ||
Revision as of 07:42, 24 December 2013
See discussion page for definition of the term. Work relations are essentially economic and you can, to the extent these are well formed, appropriate to the development situation, ignore the discipline of software development in an enterprise that is variously dependent on it. For the gap, I've assembled the material below. Process Dashboard for Teams is a useful free tool that is antithetical to agile which is a limited reaction to social conditions in the production of software. Once these conditions, as for example in large software development projects, are removed we are back to the general case of software development the earlier literature addresses. In the case of single developers or very small teams and under actually prevailing small shop conditions (2012), however, agile techniques are generally practically the only available ones with failure as a prevailing mode of outcome in varying proportion to the mismatch of resources/values in the project.
