scm

One of the issues with with dogfooding your own projects to accelerate development might be the lack of control and feedback from the specifications and requirements process. To try and mitigate this effect, automated testing should be done, that is specification, feature and behavioural testing. Call it what you will, but the basic idea is to get a common understanding between the stakeholder, project owner and developer to understand what is being built and to write automated tests collectively to ensure that it is being delivered.

Apart from the obvious unit testing code which could be fun trying to convince a team to use. There are things known as ‘Continuous Integration’ processes and servers. The basic idea is to continually build and test your product automatically and report on successful and failed builds. I’ve known about this methodology for long time now but I’ve never bothered to install a CI server since it was always for myself.