NELKINDA SOFTWARE CRAFT

XP Elements

XP Value	What it says
Communication	It is important to have communication in and around the team for knowledge sharing, problem-solving, team bonding, and team coordination.
Simplicity	XP encourages the simplest possible solution, making you think YAGNI approach.
Feedback	XP expects shorter feedback loops so that things get handled as quickly possible.
Courage	XP helps to have a courage element to seek real concrete answers which ultimately lead to the right feedback at the right time.
Respect	XP fosters humanity and productivity ensuring to value everyone's contribution with respect.

XP Principle	What it says
Humanity	People developing Software need to feel safe, included, growing, and satisfaction with their contribution to work.
Economics	The important fact any point in time is business value, meeting business goals, and serving business needs.
Mutual Benefit	XP focuses on practices that benefit everyone now, and in future as well. Like, automated testing, simple-readable code.
Self-similarity	One solution can be applied to another place and it might fit, or it might be a good start to know that the situation demands totally unique solution.
Improvement	XP brings excellence in Software Development through improvement. The aim is not really perfection but continuous refinement to reach there.
Diversity	Teams need diversity in perspectives, skills, opinions, and ways of solving the problems. XP teaches to respect the opinions of each other and have smooth communication to agree upon the most efficient way in such diverse teams.
Reflection	Reflection comes after action and is often necessary to understand feelings about actions, improvements in the actions.
Flow	Continuous flow is important in Software Development to get consistent and faster feedback.
Opportunity	Problems are opportunities for change. Part of being extreme is consciously choosing to transform each problem into an opportunity: of personal growth, deepening relationships, and improved Software.
Redundancy	Redundancy is not always bad. It can be wasteful but should not be removed when it serves a valid purpose.
Failure	If you fail, you learn something valuable. Repeated failures bring you to different solutions and lead to a better solution ultimately.
Quality	We can’t make a compromise on quality. Higher quality demands often bring higher productivity and effectiveness, and also a sense of satisfaction as you feel proud about your work.
Baby-steps	Tempting for big steps is natural when we try to solve big problems. Here, XP distinguishes by promoting baby steps to achieve the right solutions consistently. For example, Test-First Programming.
Accepted Responsibility	Responsibility can not be assigned, it can only be accepted. XP practices reflect accepted responsibility by suggesting for example, who implements a user story, also unit tests it.

XP Primary Practice	What it says
Sit Together	The more face time you have, the more humane and productive is the project.
Whole Team	People need a sense of Team.
Informative Workplace	Make your workspace about your work.
Energized Work	Work as many hours as you can work productively and can be sustainable.
Pair Programming	Writing code with a pair on a single machine (analyze, design, code, test together).
Pairing and Personal Space	While pairing personal space and individual differences should be respected so that pairing works comfortably and productively.
Stories	Plan using units of customer-visible functionality.
Weekly Cycle	Plan work a week at a time.
Quarterly Cycle	Plan work a quarter at a time. Once a quarter, reflect on the team, the project, its progress, and its alignment with larger goals.
Slack	In any plan, include some minor task that can be dropped if you get behind.
Ten-Minute Build	Automatically build and test in 10 minutes. Build which takes more than 10 minutes will be used less often and leading to less feedback.
Continuous Integration	Integrate and build a complete product. The longer you wait to integrate, the more it costs, and more unpredictable the cost becomes.
Test-First Programming	Write a failing automated test before changing any code. It creates a rhythm - test, code, refactor and repeat all again.
Incremental Design	Invest in the design of the system every day. XP teams are confident in their ability to adapt the design to future requirements.

XP Corollary Practice	What it says
Real Customer Involvement	Including Customers in the development process fosters trust and encourages continuous improvement.
Incremental Deployment	Find a little piece of functionality you can handle right away. Deploy it. Incremental deployments save human and business costs.
Team Continuity	Keep effective teams together. By mostly keeping the teams together and yet encouraging a reasonable amount of rotation, the organizations get the benefits of both stable teams and consistently spread knowledge and experience.
Shrinking Teams	As a team grows in capability, keep its workload constant but gradually reduces its size. This frees people to form new teams.
Root-Cause Analysis	When a defect is found, eliminate the defect and its cause. Use for example 5 Whys technique.
Shared Code	Until the team has developed a sense of collective responsibility, no one is responsible and quality will deteriorate. The team needs to have collective ownership by practicing pair programming, continuous integration.
Code and Test	Maintain only the code and test as permanent artifacts. Generate other documents from the code and tests.
Single Code Base	There is only one code stream. You can use a temporary branch but always prefer working on master. If you have multiple code bases in place, put a plan in place for reducing them gradually.
Daily Deployment	Put new software in production every night. Any gap between what is on a programmer’s desk and what is in production is a risk.
Negotiated Scope Contract	Moving in the direction of negotiated scope gives you a source of information with which to improve.
Pay-Per-Use	Money is the ultimate feedback. The pay-per-use system is one which charges on every single time system is used. The information generated by them helps us improve Software Development.

Abbreviation	Long Form
XP	Extreme Programming
YAGNI	You Ain't Gonna Need It