Coyote Developments is a small independent games developer based in Croydon, UK. It has been running since August 98.

The ExtremeProgrammingCorePractices that Coyote have adopted are:

* TestDrivenDevelopment via ProgrammerTest (UnitTest)
**Coyote's internal library code has unit tests. Some of the modules were written test first.
* WholeTeam
**This hasn't been formally adopted but is somewhat necessary as there is currently not that much space
* PairProgramming
**Coyote spend more time working on legacy code than on original code. For legacy code the team occasionally pair debug or pair modify, but mostly PairProgramming is limited to new code.
* ContinuousIntegration
**This has always been common practice at Coyote.
* DesignImprovement (RefactorMercilessly)
**This is not always possible as modifying the code base makes merging more difficult. Internal library code is improved in this way.
* SmallReleases
**More often than not this is a requirement of a publisher or external developer contract. A typical schedule requires releases monthly although release frequency usually increases near the end of the project.
* SimpleDesign
* CollectiveCodeOwnership
* CodingStandard
**Although Coyote has an internal standard for coding, the standard (where it is possible to find one) of the existing code is adopted when working on legacy projects.
* SustainablePace (FortyHourWeek)
**Coyote operates a FlexTime policy. When deadlines force the Coyote developers to work overtime, they take time off in compensation as soon as possible.

Coyote also now documents its projects using an internal Wiki.

Coyote's company details on MobyGames:
* http://www.mobygames.com/company/sheet/companyId,3112/

Coyote's website:
* http://www.coyotedev.com/