Conference Management Theory In Practice

Theory used in practice

• eXtreme Programming - used for almost all programming
  • Pair programming
  • Collective code ownership (also see this log enty)
  • Constant refactoring (as far as possible with a large team and our own branch)
  • Person swapping per team
  • Do the simplest thing that could possibly work; try to implement things following the KISS principle and then iteratively develop the application into something better. This principle was important to us since we had too little time and manpower (working with 6 instead of 8 teammembers) to finish this as a completely well-rounded application.
  • (...)
• Subversion - used during the whole project: used it for our own programming and use to save all pages and edited pages made by the conference: adding papers, adding reviews and publishing papers.
• JIRA - used for bugtracking
• Requirement definition
• UML State diagram (an own interpretation of an ...)
• Design specifications
• Unit tests are made

Theory planned to use in practice

• Use cases? - especially used by user authentication
• Prototype

• Model(ling)
• Project planning
• Requirement elicitation
• Requirement specification
• Test cases
• JUnit