Difference between revisions of "UnitXP"

From Cibernética Americano
Line 18: Line 18:
 
* <b>[[:en:Software development effort estimation|Sizing]]</b>
 
* <b>[[:en:Software development effort estimation|Sizing]]</b>
 
|
 
|
* [[:en:Software Development process|<b>Development Process</b>]]  
+
* [[:en:Software Development process|<b>Process</b>]]  
* <b>[[:en:Team software process|Team Process (Humphrey)]]</b>
+
* <b>[[:en:Team software process|Team Process]]</b>
 
|
 
|
 
* [[:en:Testing Maturity Model|<b>Testing Maturity</b>]]
 
* [[:en:Testing Maturity Model|<b>Testing Maturity</b>]]
* <b>[[:en:Personal software process|Unit Process (Humphrey)]]</b>
+
* <b>[[:en:Personal software process|Unit Process]]</b>
 
|
 
|
 
* [[:en:V-Model (software development)|<b>V</b>]]
 
* [[:en:V-Model (software development)|<b>V</b>]]

Revision as of 14:48, 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.