UnitXP: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 2: Line 2:
<div style="background-color: black; width: 90%";>
<div style="background-color: black; width: 90%";>
<div style="position: relative; top: 10px; left:10px; background-color: white; color: black;">
<div style="position: relative; top: 10px; left:10px; background-color: white; color: black;">
<blockquote>See discussion page for definition of the term. At bottom, working relations are basically economic and you can, to the extent those relations 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.</blockquote></div></div></html>
<blockquote>See discussion page for definition of the term. At bottom, working relations are basically economic and you can, to the extent those relations 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.
<b><a href=http://www.processdash.com/functionality-team>Process Dashboard for Teams</a> 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 are removed we are back to the general case of software development the earlier literature addresses.
</blockquote></div></div></html>
{|
{|
|
|
Line 9: Line 11:
|
|
*  <b>[[:en:CIMM|CIMM]]</b>
*  <b>[[:en:CIMM|CIMM]]</b>
* <b>[http://www.processdash.com/functionality-team Process Dashboard for Teams]</b>
* <b>[[:en:Dynamic systems development method|Dynamic Agile]]</b>
|
|
*  <b>[[:en:Dynamic systems development method|Dynamic Agile]]</b>
* <b>[[:en:MoSCoW Method|MosCow]] </b>
* <b>[[:en:MoSCoW Method|MosCow]] </b>
*  <b>[[Programmer]]</b>
|
|
*  <b>[[Programmer]]</b>
* <b>[http://programming-motherfucker.com Programming] [[Motherfucker]]</b>
* <b>[http://programming-motherfucker.com Programming] [[Motherfucker]]</b>
* <b>[[:en:Software development effort estimation|Sizing]]</b>
|
|
* <b>[[:en:Software development effort estimation|Sizing]]</b>
* [[:en:Software development process|<b>Software Development Process</b>]]  
* [[:en:Software development process|<b>Software Development Process</b>]]  
* <b>[[:en:Team software process|Team Process (Humphrey)]]</b>
|
|
* <b>[[:en:Team software process|Team Process (Humphrey)]]</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 (Humphrey)]]</b>
* [[:en:V-Model (software development)|<b>V model</b>]]
* [[:en:V-Model (software development)|<b>V model</b>]]
|
* [[:en:Extreme Programming|<b>XP</b>]]
* [[:en:Extreme Programming|<b>XP</b>]]
|}
|}
<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 20:10, 11 May 2012

See discussion page for definition of the term. At bottom, working relations are basically economic and you can, to the extent those relations 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 are removed we are back to the general case of software development the earlier literature addresses.