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.
XDSD methodology is still in R&D phase, but you can read an introduction White Paper (70Kb PDF) published by TechnoPark Corp. a few years ago
Definition Of Done 15 April 2014
When tasks can be considered "done" and their implementation paid for? This post answers both of these questions.
No Obligations 13 April 2014
In XDSD projects we recommend to manage accountability of team members by clearly defining task scope and borders or responsibility
Github Guidelines 13 April 2014
This step-by-step manual helps you to start working with a Github-hosted project in the spirit of XDSD.
Bugs Are Welcome 13 April 2014
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
PDD by Roles 12 April 2014
The article explains how Puzzle Driven Development is seen by people in different project roles, specifically system analyst, architect, designer, programmer, and tester
How much do you pay per line of code? 11 April 2014
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.
Puzzle Driven Development 4 March 2009
Patent-pending methodology of breaking down big tasks into smaller ones is explained in the article, by example in Java