A lot of developers who have worked on ExtremeProgramming projects or strongly believe in XP principles end up finding themselves on projects where the customer or other team members don't really want to do XP.  The developers find themselves doing a lot of XP things without really "telling" the others.

Some things that you can always do (and nobody really needs to know):

	* ReFactoring
	* TestFirstDesign
	* IntegrateOften
	* OptimizeLate
	* AcceptanceTest''''''s (based on customer specs)

Some things that you can do if other developers are willing:

	* PairProgramming
	* PlanningGame (mainly IterationPlanning)
	* StandupMeeting
	* CollectiveCodeOwnership

Some things you probably can't do (correct me if I'm wrong):

	* CustomerIsAlwaysAvailable
	* No OverTime
	* ReleasePlanning

-- JavidJamae

----

You can often get the customer to do a ReleasePlanning by just asking them to prioritize things. But without both sides committing to it, they can at any time appear with a different (the "official") release plan, or something else that renders your planning useless.