I wonder if principles in Extreme Programming apply elsewhere in life? For example:
DoTheSimplestThingThatCouldPossiblyWork encourages us not to over (or under)-engineer;
AskTheCode because it knows;
ListenToTheCode;
ModelFirst plus SpartanUserInterface helps us concentrate on real customer value
ExtremePlanning suggests quickly building a map of the whole imagined system and incrementally refining it
The PlanningGame formalizes the rituals and roles of planning
CountDownToRelease discusses how to use the ExtremePlanning practices when you're getting close to release
ExtremeReuse - adopting third party software and making it XP-compatible by building tests
TossIt - making projects trim and keeping projects trim
SystemMetaphor - how we communicate the system to ourselves and others
XpSimplicityRules
OnceAndOnlyOnce
ExtremeDocuments - we do documentation, sometimes differently
SupportCrisis - what to do until the doctor comes
IncrementalDelivery
LazyOptimization and EarlyProfiling
OpenWorkspace
Results in...
IterativeDevelopment - tends to be a natural result of ContinuousIntegration and ContinuousIntegrationRelentlessTesting and DoTheSimplestThingThatCouldPossiblyWork at each iteration
DynamicDesign - from RefactorMercilessly and short Code-Compile-Debug cycle
FewerWorkHours [important]
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment