TeamWork is the central collaboration hub for your project. Stakeholders and project teams work and benefit together from each others knowledge and experience.

When to use TeamWork

Business analysts use TeamWork during requirement analysis. Grouping requirements and documenting ownership or stakeholder priority are just a few of the activities where analysts are facilitated by TeamWork. Freestyle notes and session minutes can be stored in TeamWork for distribution in the project team.
Project managers plan sprints or iterations according to the implementation priority and order. Work can be assigned to specific team members or to groups, making it obvious to all project members what needs to happen right now. Project progress is captured in TeamWork so the team knows if they are on track. 
Engineers use up-to-date information about planned work, related documentation and requirements. They document their findings and progress in TeamWork during their workday. Also engineers can reuse existing models from previous projects or a centralized store from within TeamWork.
Testers and end users use TeamWork's progress indicators and stored documentation to test system functionality when it has been implemented.

Access to TeamWork is controlled to ensure high quality data to work with. Authorizer handles access control for projects as it does for production systems.

What are your benefits

Stakeholders and project teams gain many benefits using TeamWork, here are two of them.

A higher quality system is created according to the latest information available. Information is always up-to-date since TeamWork provides team members with notes, remarks and session notes. No more hunting down the 'missing' document. Team members have access to the actual project progress, engineers know which requirements still need stakeholder validation before they can be implemented. Also the test team knows which requirements are implemented and thus can be tested, of course they also have the requirements and documents needed to perform those tests.

The system can be delivered sooner. Team members no longer spend time looking for needed documentation, related remarks or references session notes. Since less implementation mishaps are made due to incorrect documentation, less time is spent fixing those mishaps. System documentation is compiled with and from TeamWork, this guarantees that the correct information is used and dramatically speeds up documentation effort.