Project HQ with software development in mind, though there's nothing that ties Project HQ specifically to software development. Behind Project HQ's layout is the idea of a workflow for projects. This section will explain the process of this workflow.
Projects & Milestones
At a high level, a project can be divided up into various milestones. These milestones are development goals, which once achieved would add a certain level of functionality to your project. For instance, one of the milestones for Project HQ was the 0.1.3 release, which added the ticketing system to the project.
Milestones are not necessarily set out in a particular order, nor do they need to be dependant on other milestones. A project could, for instance, have 2 or 3 concurrent milestones, with a development team assigned to each milestone.
Task Lists & Tasks
The next level down from a milestone is a task list. As per it's name, a task list contains a list of (hopefully) related tasks. Multiple task lists can belong to the same milestone. This allows the work in a milestone to be sorted into lists of related tasks.
Each task would then be a unit of work. This could be as small and simple as adding a link to a page (for instance) or as complicated as a whole feature, though it is recommended that you keep the size of tasks down to small, easy to implement, chunks of work.
Tickets
Even though a project is complete, it is not always the end of the road. The ticketing system in Project HQ helps you manage any issues that arise after the completion of the project.
The ticketing system allows files to be attached to tickets, and source code and images are displayed for the user.
