How to structure work data in Teamhood?

Here we provide a quick guide how to pick the most suitable workspace structure based on the use case.

Essential structure or data hierarchy blocks in Teamhood are

teamhood data structure

Workspaces

Workspace is an ideal element to group people working together, this way you can control who has access and roles in the workspace. In most cases you should choose workspace based on function (i.e. sales, marketing, engineering, etc.), projects portfolio or simply whole organization (projects, admin tasks, etc.). Below you can see sample of Teamhood workspaces:

workspaces

Boards

Boards are key structural elements for workspace. Boards are ideal for grouping work items and then using boards to filter in other views.

Teamhood boards

Each board can be used to represent different project, client, group of people or process step. Examples:

marketing kanban structure
manufacturing kanban structure
Kanban project management
Agile software development kanban
Agile customer management

Rows

You can use rows to group different: teams, resources, project stages, work packages, classes of services, priorities, months, weeks, years, etc. Rows can come in handy when filtering work item data in views,

Rows

Workspace Views

Each workspace can have specific views to gain a different perspective on your work data. You can add views by pressing “+” sign near workspace title.

Workspace views are ideal when you need to view data from multiple boards. This is ideal for reporting or managerial overview.

Single Team task management

Go for single workspace and split different work stages into boards, and each board should be split into at least few rows, like in the example below:

Agile sales

Multiple team task management

Decide whether your teams collaborate on daily basis. If not choose separate workspaces for each team and then structure boards / rows accordingly.

Sales to marketing flow

If teams do need to collaborate on daily basis, chose single workspace and a dedicated board per team. You can make boards private to ensure only certain people can view work data.

Sales to marketing kanban

Project management – short and small projects

Duration: 1-6 months
Team: <5 people
Work items: <20

If you are running a significant amount of small projects every few months it is optimal to create a single workspace with boards to group/categorize projects if possible and rows either per project or even further grouping of projects.

Agile workspace

In case your projects are shorter than 1 month and they involve only couple of work items, it is better to put them all either in one or more boards and then use rows for further grouping and only top level work items to represent projects. Item templates can save a lot of time for standardized work.

Project management – medium sized projects

Duration: 3-24 months
Team: 5-25 people
Work items: 20-1000

If each project involves significant amount of work items and takes time to finish, it is optimal to create a single workspace per portfolio and then as many boards as there are projects. You can use rows for work packages or project phases.

agile projects

Project management – project program

Duration: >24 months
Team: > 25 people
Work items: >1000 work items

For large scope projects create a single workspace per program and use boards for separate projects or parts of project program. Rows can be used as phases or further breakdown of work.

agile project program

If you have questions or above guide is not enough contact us!

Teamhood uses cookies to improve your experience, personalize content and ads, to provide social media features and to analyze our website‘s traffic. By agreeing you accept the use of Cookies in accordance with our Cookie Policy.