Extreme Programming (XP)
Advertisement
Techopedia Explains Extreme Programming (XP)
In addition to the key values, XP methodology implementation also requires the support of the three principles of incremental change, embracing change and quality work. Twelve key practices also must be followed: Some traditional methodology practitioners criticize XP as an “unreal” process causing reckless coding. Several traditional software developers find XP inflexible with low functionality and little creative potential. Additional criticisms are that XP: Has no structure. Lacks essential documentation. Has no clear deliverables, i.e., realistic estimates are difficult because the entire project requirement scope is not fully defined. (This lack of detailed requirements makes XP highly prone to scope creep.) Needs cultural change for adoption. (May work for senior developers only) Is costly, i.e., requires frequent communication/meeting at the customer’s expense, which may lead to difficult negotiations. Has possible inefficiency from frequent code changes within various iterations. Of course, as with any development methodology, all this is very subjective and dependant on personal preferences.Related Question
What are the biggest uses of SQL today?Advertisement
Related Reading
- How Cloud Computing is Changing Cybersecurity
- Data Science: How to Successfully Create and Productionize Across the Enterprise
- International Women's Day: We Asked Why There Aren't More Women In Tech
- C Programming Language: Its Important History and Why It Refuses to Go Away
- Straight From the Programming Experts: What Functional Programming Language Is Best to Learn Now?
- The Ultimate Guide to Applying AI in Business