XpLite, as proposed,  is a heavier methodology than XP.  The name XpLite implies XP with something taken out and is misleading.

Derivative related names water down the XP message.  We must find other ways of TransitioningToExtremeProgramming.

Suggested Alternate Names:
	* XpJr
	* MyFirstXp
	* ProgrammingInModeration
	* BunnyRunProgramming
	* SemiXp
	* FirstPowderRunProgramming
	* HelloXp
	* XpWithExtraCream
	* NotSoExtremeProgramming
	* XpWithTrainingWheels
	* XpForDummies (sorry)
	* XpWithWeightsOnYourAnklesAndWrists  ''I sense a certain discomfort.  Don't hold back.  Tell us how you really feel...''
	* PartialXp
	* RUP with XP Added (or whatever your core process is)
	* ''RUP + XpLite ?  (As you say, XpLite is not a stand alone methodology)''
	* XpWithoutTheXpart
	* LowerCasexP
	* NotAsExtremeAsYouWannaBe
	* NotQuiteFearfulProgramming
	* TastesGreatLessFulfilling
	* XpMarbels
	* MiniXp  ''(Per Dr.Evil's "Mini-me"  ;-)''
	* NotVeryExtreme-Programming
	* WO (Roll back one letter from XP)
	* CogentDevelopment
	* XpPlusplus
''[Please feel free to delete and/or add names that are just silly!]''
----
On the other hand, having Xp in the name should make it harder for XpLite to be seen as a serious alternative to Xp, as it might if it had a completely different name.  Do you use Sunos or Solaris?  If it has a different name people might think it is something different.  The names XpLite or XpJr stop that from happening, and XpLite is the less childish of the two.  IMHO.

Why shouldn't it be a serious alternative for alternative situations? Then again, I don't really know what this XpLite is. If it is at all like XUP, it should be pretty cool. I didn't think Xper's had a monotheistic view of the world? Isn't it possible to (just as Xp did with other methodologies) take from Xp and end up creating a different but equally good alternative? 

Personally, I dont' think Xp should be in the name because, then, it will always be compared to Xp in a way that will inhibit its individual growth. I would like to see an alternative to ExtremeProgramming called something like CogentDevelopment -- this takes the emphasis from extreme to rational and from programming to development. To be honest, other stakeholders in a project really feel left out when the process name makes the programming roles seem most important. In my world, the customer and QA technician, even the build master is as important as the programmer.
-----
Should we call this page "AlternateNamesForPrettyAdventuresomeProgramming" (PrettyAdventuresomeProgramming) or "AlternateNamesForAlmostExtremeProgramming" (AlmostExtremeProgramming)?