Explore Extreme Programming (XP) and its core principles—communication, simplicity, feedback, courage, and respect. Discover its rules, preparation, management, design, coding, testing, and developer tips for success.
Let’s start by asking what is Extreme Programming? Also called (XP).
Extreme Programming is designed for enhancing your software.
We will be covering what exactly Extreme Programming is and have a run through of how it works, starting with the principles of it to the values that are behind this system, to the procedures that have been best practiced.
These are the 5 foundations that are key points towards extreme programming, and what it needs for it to be able to work successfully for you and your company. This will cover how one can use extreme programming and what you might need.
Everyone is included in the community and have frequent conversations daily. We will create code as a team. As a team, we will create the best methods and tackle bugs as they happen together.
This will increase the investment’s value. We will only do what is needed and asked of us and no more than that, taking baby steps towards our goals and fix failure as they appear. We will produce something we support and will do the upkeep long term for the consumer.
We will work on each section as a team and as a community that enjoys creating. We will need to review the developments early on to help reduce issues that might come up at a later stage. Furthermore, we will communicate about our project as a team and adapt to it, this can not be the other way around.
We will be honest about the progress that has been made. Documentation of failure is not accepted as it is not something we conduct in the project. Nothing is feared as we all work together.
Everyone will get the respect they deserve as a teammate, and everyone will get that respect back. Everyone in the community contributes in some way or another this can even just be enthusiasm towards the project. The team respects the consumer and is reciprocated back from the consumer. Higher-ups acknowledge our rights to accept responsibility.
This iteration of Extreme Programming Rules, first published by Don Wells in 1999, were originally intended to help counter the claims against Extreme Programming, with saying’s that it fails to support some of the disciplines necessary for current development.
A concept for a healthier balance between work, with developers on a project is the statement that no-one is required to work more than they normally schedule. The concept of “crunch time” is frowned upon and the same is said about overtime, when developers are looked at to work extreme over-time near the end of a project to get it finished at the right time.