Working processes

What we’re trying to do at work:

  • test-driven development
  • pair programming
  • implementation docs on the wiki
  • code coverage stats (with cobertura) regularly generated via…
  • continuous integration (at the moment with CruiseControl, soon to move to Bamboo)
  • rapid software iterations (we suck at this right now)
  • totally transparent group activity

I think we’re doing quite well on these things, but I wonder if it looks different from the outside?

Leave a Reply

Your email address will not be published. Required fields are marked *