XDSD is an open software development methodology that aims to reduce risks and improve quality in project of almost any size. At the moment, there are four fundamental principles:
- Everyone gets paid for verified deliverables
- Defects are planned and don't block delivery
- Quality-of-code metrics are CI gate conditions
- VCS commits to the master branch are prohibited
At this site, we publish our success stories and recommendations on applying XDSD to varios software projects. Interested in trying XDSD with your team? Email us.
Interested in improving XDSD? Help us, submit an issue to Github issue tracker.
Requirements engineering can be done incrementally with Requs open source controlled natural language
In this article, we discuss a very sensitive and important topic — who should get higher rates in extremely distributed projects.
This article lays out the most important and critical differences between XDSD and traditional software development methodologies, including Agile
This step-by-step manual helps you to start working with a Github-hosted project in the spirit of XDSD.
When tasks can be considered "done" and their implementation paid for? This post answers both of these questions.
In XDSD projects we recommend to manage accountability of team members by clearly defining task scope and borders or responsibility
Unlike a very common understanding of a software bug as something negative, XDSD encourages all team members to find and report as many bugs as possible, in order to improve quality of the end product
The article explains how Puzzle Driven Development is seen by people in different project roles, specifically system analyst, architect, designer, programmer, and tester
This article compares two projects and calculates their average costs per one line of code changed. The experiment proves economical advantage of a distributed development.
Patent-pending methodology of breaking down big tasks into smaller ones is explained in the article, by example in Java