Team HQ is a primary, web-based tool at LinkORB used for teamwide project and task tracking, status updates, internal wiki documentation, and much more. This document is focused on the project tracking tool and recommends best practices for project owners.
The following is a typical Team HQ project workflow:
Manage your own projects (i.e. projects you're the owner of) from the My Projects (Owned) dashboard. To view all projects you're part of, point your mouse cursor on the Projects navigation item and select Project list & search.
Saving a newly created project or opening an existing project from the projects page loads the project's WBS1 view by default. Click any of the tabs next to the WBS1 view to access that view.
WBS1 view: A table-style Work Breakdown Structure of the project. Each row of the table is a project card (work item). Each top-level card has a gray background while its sub cards have a white background. This makes it easy for team members to quickly scan the WBS.
See Using project cards to assign and complete project tasks for more information on creating, viewing, and editing cards from the WBS1 view.
WBS2 view: This is similar to WBS1 view except it organizes the project's Work Breakdown Structure into a nested list of cards and sub cards.
Description: A summary of the project's the purpose and description.
Dashboard: Currently active project cards organized into different sections in a grid based on their status an due dates.
List view: Stacked lists of cards in a project grouped by state, assignee, priority (prio), milestone, sprint, or component.
Kanban view: A grid of cards grouped by state, assignee, prio, milestone, sprint, or component.
A project's flow state indicates where the project is in it's lifecycle. Update a project's flow state as follows:
A project card is a work item. It's how we assign and track tasks for each project team member. See Using project cards to assign and complete project tasks and Team HQ project card best practices for more information.
Create a Team HQ project as follows:
Click the green Add Project button.
Fill out the form fields in the Add project settings page as follows:
Select the group that the project falls under in the field. If you can classify the project under several groups, please consult with the product owner before you continue.
Select the LinkORB Userbase ID (UBID) of the person responsible for the project in the Owner field.
In the Time Frame field, set the time frame in which you expect the team to complete the project. The Chief Executive Officer (CEO) and the PO will review this time frame later and possibly adjust it.
Write a detailed description of the project in the Description field. In describing the project, clearly define its:
If the project is a pitch, answer the following questions in the description:
If the project is in the Business case phase, add the link to the business case in the project's description. If the project does not have a business case, create a Business case as follows:
Click the green Save button.
While a project is ongoing, the P.O. and team members have a bi-weekly discussion to decide whether the project's priorities are still correct. During this discussion, they also:
In the last week of each quarter:
A work breakdown structure (WBS) is a hierarchy, which outlines the concrete partial results/products of a project. It organizes a project into smaller, discrete, more manageable components (phases, tasks, sub-tasks). A WBS gives insight into project details like:
See the The WBS1 view and WBS2 view sections of Using project views for more information.
To give an example of a WBS, imagine you and your team need to build a house. To complete this project successfully, you create a WBS as follows:
The image below illustrates the structure (WBS) of our example project so far.
Based on the current WBS, you can create a WBS dictionary that will look like the following:
Although often skipped in the planning process, a work breakdown structure or dictionary is a powerful tool to complete projects efficiently and on time.
Creating a project WBS benefits your team because it:
Before you delve into the fine details of a project's WBS, it's important to hone it at a high level. First, take these important preparatory steps:
To remove people from the team:
Any team member can propose a project at any time by creating a project and setting the project's flow state to Pitch.
You can enable a repository on a project-by-project basis. This process makes the most sense in larger/maintenance projects. To use a repository, do the following:
default-closed-card status: hiddento the *Config (YAML) block at the end.
We only use the configuration block (YAML) for advanced or experimental functions to see if they work as expected. Once they work as expected, we create user interface options for those settings.