Development process

We will use Part-up and Github to manage the development process:
 * Backlog management: as the product owner, Ralph Boeije manages the issues and milestones (=prioritization). He starts a feature development part-up in the Part-up development tribe for a coherent set of issues. In these part-ups the budget and sprint timeline is specified. Of course, everyone is free to add voluntary contributions to the code.
 * Team formation: Existing teams or freelancers can propose their contribution to the part-ups that are created.
 * Development sprint: The team creates the relevant feature branche(s) (naming convention: "ft-" and starts a pull request right away to discuss the technical details and to link the commits to the issues. The part-up partners give regular updates about the development process on the part-up. The pull request on Github can be used to discuss the specific details and code reviews.
 * Merge: Before the DevOps part-up team will do a merge to the develop branch and deploy to staging, they check for the DoD and code quality. NB: later on, we will provide for a staging environment for each feature development team. If all is well, the feature is then deployed to acceptance by the Platform part-up partners.
 * Demo: At the start of the feature development part-up the demo is planned right away. The team demo's the feature to the product owner and if accepted, he will take care of payments.

Backlog grooming

 * Edge cases
 * Responsive
 * Data available or needs to be created
 * Integrations (external API)
 * User generated data
 * Randomness
 * Cross-browser compatibility
 * Internal API (e.g. matching)

Definition of Done (to be completed):

 * Translations integrated
 * Unit tests written for shared lib code (best practice is to start with a unit test before writing a single line of code)
 * Responsive HTML (where defined)
 * Feature branch verified by a team member before merging to develop
 * Deployed to staging environment
 * Tested all features on staging