Talk:UnitXP: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(32 intermediate revisions by the same user not shown)
Line 1: Line 1:
:'''Note: comments, account creation via DS SSO only.'''
== What it is ==
== What it is ==
<div style="background-color: white;color: navy;">
<div style="background-color: white;color: navy;">
Unit XP was coined, c. '98, as just my variant for Extreme Programming. I'm quite often acting as an entire IT function, whereas Agile/Extreme, etc. generally talk about teams, with non-IT personnel involved to be sure, but not in general with the IT worker set being a singleton. I can expound on this live, nothing more to say here. [[User:Root|Root]] 13:10, 29 March 2012 (UTC)
<br/>
<blockquote>
Unit XP was coined, c. '98, as just my variant for [[:en:Extreme Programming|Extreme Programming]]. I'm quite often acting as an entire IT function, whereas Agile/Extreme, etc. generally were talking about teams of at least two developers, with non-IT personnel involved to be sure, but not in general with the development team being an individual. <p>Humphrey's Personal Process is individual oriented, but it predates and is anti-thetical/oblivious to Agile or it's reason for being. <b>[[:en:Watts_Humphrey|<font color=darkgreen>Humphrey</font>]]</b> was in his 70s when Agile/Extreme came out but that's not likely to have inhibited there having been a retrofit. UnitXP was mine. Think he also did something addressing this century.</p>
<p>Humphrey's [http://www.informit.com/store/product.aspx?isbn=0321624505 <font color=darkgreen>last work</font>] (as co-author) appears on the basis of its TOC (use search function to access ) to completely ignore agile and the typically under capitalized projects which are by far the bulk of those undertaken. His typical project's staffing includes 10 programmers, individuals doing development so it's an order of magnitude off.</p> The recent CACM article confirms the continued lack of individual practitioner focus, the gap addressed. [[User:Root|Root]] 10:27, 19 July 2012 (UTC)</blockquote>
<br/>
</div>
</div>

Latest revision as of 08:27, 13 June 2015

Note: comments, account creation via DS SSO only.

What it is


Unit XP was coined, c. '98, as just my variant for Extreme Programming. I'm quite often acting as an entire IT function, whereas Agile/Extreme, etc. generally were talking about teams of at least two developers, with non-IT personnel involved to be sure, but not in general with the development team being an individual.

Humphrey's Personal Process is individual oriented, but it predates and is anti-thetical/oblivious to Agile or it's reason for being. Humphrey was in his 70s when Agile/Extreme came out but that's not likely to have inhibited there having been a retrofit. UnitXP was mine. Think he also did something addressing this century.

Humphrey's last work (as co-author) appears on the basis of its TOC (use search function to access ) to completely ignore agile and the typically under capitalized projects which are by far the bulk of those undertaken. His typical project's staffing includes 10 programmers, individuals doing development so it's an order of magnitude off.

The recent CACM article confirms the continued lack of individual practitioner focus, the gap addressed. Root 10:27, 19 July 2012 (UTC)