There is, of course, no shortage of management tools for Agile software development. But none of them seem to be targeted at developers, small teams, or first-level managers. They seem to attempt to implement in software everything in any particular Agile methodology (for example Scrum and XP). They attempt to manage across the entire organization, especially highlighting managing above the project to the program and enterprise levels and in doing so become mostly an effort tracking system where developers become resources and are simply required to enter time spent on tasks. They also attempt to track all aspects of development by integrating testing (test tasks and test results) and defect tracking. By being all things to all people, the eventual interface become useless for a developer in their day-to-day development. By trying to provide a "complete" picture of a project's status, their interfaces become a mass of "percent complete" statistics where any particular stat one is looking for is not quickly identifiable.
The project specification can be defined in word processor format as you would normally. By adding some special items, such as titled bulleted lists and highlighted text items, both a test suite and glossary can be written right into the spec. The Arbiter server will parse these documents and run the tests, reporting the results into the documents themselves. This allows the client to see project process.