Extreme Programming (XP).

Extreme Programming (XP), a framework for agile project management, is used in software development. It teaches everything, from how to organize projects to develop software to how to increase developer productivity and how to collaborate on code. Extreme Programming is an agile framework, which means that it encourages frequent releases, iterative and customer involvement. It is similar to Scrum but XP is more prescriptive than Scrum. XP focuses on code simplicity, how it is written and deployed, and how developers work. This means that XP can only be applied if you work for a software development company. Project Management Frameworks and Methodologies
This article is only a small portion of the story about project management. We cover it in great detail in our flagship ebook. We appreciate you subscribing. All newsletter subscribers can download this (and many other ActiveCollab Project Management Guides). Download the Ebook We are unable to subscribe you at the moment. Please double-check your email address. If issue still persist, please let us know by sending an email to [email protected] Try Again What’s at the core of Extreme Programming (XP)
XP can be compared to Scrum, but with a layer of coding best practices. This is the easiest way to understand it. XP is an agile framework that teaches you how to code. XP believes that software development is hard. This is what the tests will tell you. If you are smart, you will write them first so that you know when you are done. You’ll be stuck thinking you might be done but not knowing how close you are. LISTENING – First, you need to understand the problem. Then you will need to know what numbers to use in the tests. This is something you won’t be able to do by yourself. You’ll fall under the weight of your own assumptions. Software is all about listening, testing, coding, designing. Anybody who claims otherwise is selling you something. Kent Beck, creator of Extreme ProgrammingPROJECT LIFECYCLE in XP
Small releases – work is delivered to customers in small cycles. If a feature takes longer, it is broken down into multiple cycles.
Pair programming – All production code should be written on one computer by two developers. This will increase code quality and reduce the number of bugs. It will also save you from future bug fixing. Collective code ownership – everyone has access and can fix any problems. You should also remember that any code you write can be used by others so make sure your code is clear and easy to understand. Bu