Standard software engineering techniques typically focus on strict rules governing the behavior and roles of management, developers, and customers. What if your team lacks software engineering experience and a formalized management structure, and has to deal with rolling requirements? Sound like a nightmare situation? Relax! Not all hope is lost.

Presented here is how we capitalized on our strengths and minimized our weaknesses while creating a sophisticated code-base with a minimal number of developers using Trac, an enhanced wiki and issue tracking system for software development projects. Developers interested in how smaller development teams (we have only 3) successfully implement large projects will find this presentation both enlightening and frightening.

By the end of the presentation, you will learn: how to configure Trac to use it in a time-efficient way, what plug-ins you want and don't want, how to structure the wiki, ways to use subversion commit messages to cross link tasks and code changes, methods to organize tasks as tickets into manageable chunks, and other tips and tricks to simplify the life cycle of the project. We will also cover ways to structure the project with an eye to easier deployment.