|
|
|
|
|
|
TeamHeadquarters is a team productivity suite. The software is used by organizations to plan, assign, manage, and track their work assignments, whether it's proactive project work, ad-hoc administrative duties, or reactive support incidents.
As a collaboration suite, TeamHeadquarters has 5 distinct 'tools':
Project Portfolio Management. The portfolio reporting capability supports high level aggregated reporting across any number of projects, without reliance on detailed work breakdowns and planning models.
Project Management. The project functionality offers task planning and tracking capability for projects of virtually any size. Your projects can be managed with financial tracking (for budgets, costs, and benefits), tasks, document libraries, status reporting, issue & risk tracking, defect tracking, and integrated time sheets.
Help Desk. The TeamHeadquarters ticket queues can manage support incidents for any number of distinct support desks distributed across any geographical scope.
Contact Management. Company contacts can be maintained in a collaborative setting, and related to projects and support tickets.
Document Management. Document libraries can be managed for virtually any part of TeamHeadquarters including projects, tasks, tickets, and contacts.
The function can be viewed in terms of the different tools making up the suite. These tools can be used individually, or used in various combinations as needed. For more information about one of the functions, click below on its name.
Another way to view TeamHeadquarters is based on the fundamental business activities supported by the software. The One Task List concept breaks down the barriers that distinguish different kinds of software and the type of work they support (e.g. project management vs. portfolio reporting vs. program management vs. help desk vs. risk management vs. defect tracking). With One Task List, we plan, execute, and manage all of a team's work in a single environment, regardless of what 'kind' of work it is.
For example, the One Task List approach can break down functional barriers in software by:
Enabling planning, costing, and aggregated 'initiative' or 'portfolio' reporting for Help Desk operations. Help Desk software typically lacks this type of proactive planning capability.
Allowing project work to be assigned, executed, and tracked using 'help desk' tickets, rather than formal project tasks. This approach encourages adoption of the software for management of the actual work, without dependence or impact on the formal work breakdown structure.
Facilitating the assignment and execution of internal, ad-hoc, and informal work that has typically been managed using email, sticky notes, and verbal requests. As a result, these 'distractions' can be prioritized in the same context as the project and support work.
One Task List is explained with theory, benefits, and practical examples in the Teamwork Fable by Entry CEO Barry Cousins.
