This guide for beginners introduces you how to operate TRICHORD step by step. It will also give you the basic concept, notion of progress checks and project planning and monitoring procedures along with how to operate TRICHORD. Please read this guide before you start TRICHORD.

  Purpose of the Tutorial

This Tutorial is intended for users to efficiently master TRICHORD project management tool series of operations. In addition to how to operate TRICHORD, this Tutorial also describes the basic concepts of TRICHORD, progress check concepts, project planning and monitoring methods.


  1. TRICHORD Project Management Concepts
  2. Planning a Project
  3. Using TRICHORD to Manage a Project
  4. Using Niko-niko Calendar to Share Team Status
  5. Other Functions

  1. TRICHORD Project Management Concepts

TRICHORD is a project management tool that uses a timebox management method to perceive project statuses based on concepts called tasks and timeboxes. Project progress status is managed in such a way that a timebox is handled as one scope and project members share tasks that must be executed within the scope. This helps you constantly monitor project status and take prompt action when an issue occurs. Before discussing how to operate TRICHORD, let's talk about the basic concepts.

1-1. Timebox Management

The basic idea behind timebox management is to set up a timebox, which is a time frame that is divided into certain work periods, known as tasks, and then allocate the tasks that must be completed within the timebox. A timebox is a scope through which work progress status can be grasped. Team members manage tasks that must be handled within the time period.

  Figure 1. Timebox Management

Tasks inside a timebox are managed using three statuses: TODO (remaining work), DOING (ongoing work), and DONE (completed work). As shown in figure 2, if you visualize the status of tasks inside the timebox, the volume of TODO and DOING tasks can be understood intuitively.

  Figure 2. Tasks inside a timebox

1-2. Timebox Management in TRICHORD

In TRICHORD, since the aforementioned timebox management method is used for software development projects, the timebox concept has been expanded.

1-2-1. Grouping Tasks by Features, Stories and Tasks

Tasks are hierarchized to ease management. The top level is called a feature, in which one unit is a function to be implemented by software or is a big work item. For example, the first one could be a function such as a master database management function, while the latter one could be a project such as a system release.

Each feature contains multiple stories. Stories are used to implement features. Let's use the previous example. The master data management function must have multiple stories, for example, "add data must be possible", "change data must be possible", "deletion data must be possible", and so forth.

Furthermore, each story is comprised of tasks. Tasks are specific work items necessary to implement a story. For example, for "master registration must be possible", we can imagine specific work items such as "investigate the master database schema", "write master registration code", "write master registration test code", and "test master data registration."

During work planning, project managers or project members segment features into stories, and then stories into tasks.

1-2-2. Splitting a Timebox into Releases and Iterations

To make it easy to understand the work status, TRICHORD splits and manages a timebox, which is a management scope. Timeboxes are classified into releases and iterations and a project is divided into releases, which are big milestones. Further, releases are divided into iterations that are scopes in which the project is actually monitored.

  Figure 3. Splitting a timebox

1-2-3. Kanban Boards

Kanban boards are three types of views provided by TRICHORD to list timebox and task status.

Feature Kanban board
As shown in Figure 4, the progress status of features in the entire project can be understood by displaying the information for the entire project period, which is divided into multiple releases. In each release, features that must be completed within the release are managed using a card metaphor. Feature status can be understood by the information displayed on these feature cards.

  Figure 4. Feature Kanban board

Story Kanban board
As shown in Figure 5, the progress status of stories in iteration can be understood by displaying information in the release, which is divided into multiple iterations. In each iteration, stories that must be completed within the iteration are managed using a card metaphor.

  Figure 5. Story Kanban board

Task Kanban board
As shown in Figure 6, the status of tasks in a specific iteration is displayed. In a Task Kanban board, an iteration is devided into three statuses, Todo, Doing and DONE, and a card metaphor is used to manage tasks that must be completed. By observing how task cards are arranged, task statuses an be understood in a glance.

  Figure 6. Task Kanban board

You can switch the card size on Kanban board in two different sizes from context menu. "Full size" shows all detailed information in card and "Small size" shows only the names of cards in less than two lines. The size of each card can be changed individually. (Figure 7).

  Figure 7. Cards in Full size and Small size on Kanban board

  2. Planning a Project

Since timebox management does not depend on the development process, phases, timeboxes and tasks are mapped in a way appropriate for each development process. The following is an example of a project planning procedure.

When planning the entire project: Planning releases and features
When planning a project, the entire process is divided into releases as necessary (it is OK to have one release equal one project). Then, according to the release notes (a list of functions that need to be provided in each release), functions to be implemented in each release and work items are listed as features and arranged in releases.

When planning a release: Planning iterations and stories
When each release starts, the release is divided into iterations. It is easy to perceive the project if the scope of iteration is short, for example one or two weeks. Next, features allocated to a release are divided into stories and these stories are allocated to an iteration.

When planning an iteration: Planning tasks
When each iteration starts, stories allocated to iterations are divided into tasks. When you place tasks in a timebox (iteration), you need to consider the problem processing capacity of the team. You must not plan tasks in such a way that the timebox overflows.

  3. Using TRICHORD to Manage a Project

Based on the previous explanation, this section describes specifically how to use TRICHORD to plan and manage a project.

3-1. Configuring and Installing TRICHORD

Configuring TRICHORD
TRICHORD is Eclipse RCP-based software. Progress status is managed by XML document groups called workspaces. Team members manage project status by viewing and changing file-shared workspace. By means of the change detection function and consistency management function of this workspace, TRICHORD supports updates by multiple users.

Installing TRICHORD
TRICHORD is installed by downloading and running an installation module. After installation, to run TRICHORD you must set the evaluation license or product license key.
For details, see FAQ: "How can I register a license?".

3-2. Creating a Project and Users

Creating a workspace
Immediately after installation, the Welcome to TRICHORD window appears. To start operation, right-click start TRICHORD. The window shown on figure 8 appears.
  Figure 8. Welcome to TRICHORD

This window is used to specify the workspace. Each workspace is an XML document group that is used to store project information. When creating a new workspace, specify a file-sharing space where all team members can view and update data. You can specify a previously created workspace.

  Figure 9. Creating a Workspace in the shared folder

You can create a Workspace in the shared folder. There are two ways to access Workspace in the shared folder with TRICHORD. For details, [Help]-[Help Contents], [参照]-[ウィザードおよびダイアログ]-[Selecting a Workspace].

Creating users
In TRICHORD, you can create users immediately after installation in order to allocate an ID to individual users to differentiate between them for tasks and Niko-niko Calendar. From the list in Preferences window, choose TRICHORD > User Management to start up User Management.

  1. From the menu, choose [Window]-[Preferences] to start up the setting window. (Figure 10)
  2. From the list in Preferences window, choose [TRICHORD]-[User Management] to start up User Management. (Figure 11)

Setting the default user
Specify the default user to be used on TRICHORD. To switch the default user to an previously registered user, choose File > Switch user to select yourself from the list of registered users. In this way, you can allocate your own user name for the workspace.

3-3. Creating Releases and Iterations

After a workspace is created, there will be nothing there. Choose the File > Open Kanban menu command to open a Kanban board. Doing so displays the following Kanban board template as shown in figure 12.

  Figure 12. Creating releases

Feature Kanban board
The workspace name is displayed on the tab. A release named New Release is created. Also, a feature named New Feature is created inside the aforementioned release.

Story Kanban board
New Release is displayed on tab. An iteration named New Iteration is created. Stories are not created.

Task Kanban board
New Iteration is displayed on the tab. Tasks are not created.

3-4. Creating and Changing Releases

According to the created plan, create multiple releases. Click the workspace tab to display a feature Kanban board. When a new release is created, only a release named New Release, which was set by default, is displayed. At this point, to change the release name and release period, edit the theme (release name) and release period in the property viewer in the lower part of the window.

  Figure 13. Release Property

To add a release, as shown in figure 14, click the release icon on the palette and then click the Kanban board. Use the aforementioned procedure to change the release name and release period.

  Figure 14. before releases have been created

In figure 15 two releases have been created.

  Figure 15. after releases have been created

Furthermore, you can detach the Property View (Where you edit properties of selected objects) from main window by choosing "Edit property" in context menu on a Kanban board. So you can have the "Property View" wherever it is convenient for you and modify properties.

  Figure 16. Editing on property view

3-5. Creating and Changing Features

Features are created on a feature Kanban board. An empty feature is created by clicking the feature icon on the palette and selecting (click) a release for which you want to create a feature. Feature properties can be set by updating the feature property view, which is displayed by clicking the target feature.

Item Description Initial Value
ID Serial no. for identifying object Serial no.
Name Feature content New feature
Status Feature Status (Todo/Doing/DONE) Todo
Full Story Size Total points of all associated stories 0.0
Completed Full Story Size Total points of associated stories that have been completed 0.0
Completed Percentage Completed percentage of associated stories 0.0%
Deadline Feature completion deadline End of release
Color Feature card color White (RGB {255,255,255})
Tag Feature card tag Blank
Comment Feature comment field Blank
  Table 1. Feature Properties

3-6. Creating and Setting Iterations

Setting an iteration
After dividing a project into releases, you next further divide each release into iterations. By double-clicking a release on a feature Kanban board, a story Kanban board corresponding to the release opens. In this Kanban board, one iteration called a New Iteration is already created. Clicking this iteration opens the property view for the iteration. In this view, you can change items such as the iteration name.

  Figure 17. property about an iteration

Item Description Initial Value
ID No. for identifying object Serial no.
Theme Iteration theme New iteration
Period Iteration period (start - end) One week from the day after the end of the previous iteration
Velocity Total size of completed stories 0
Total Story Size Total size of stories 0
Total Estimated Tasks Total of estimated tasks within the Iteration 0
Total Task Remaining Total of remaining tasks within the Iteration 0
  Table 2. property about a iteration

Creating an iteration
To create a new iteration, click the iteration icon on the palette and then click the blank part of the story Kanban board. At this stage, you create the number of iterations you need.

3-7. Creating and Setting Stories

Creating a story
You need to create stories on the previously described story Kanban board. To create a story, click the story icon on the palette and then click the iteration for which you want to create stories. Repeat this step as many times as you need.

  Figure 18. Story Kanban board

Setting a story
Clicking a story on the story Kanban board displays the property view of the clicked story in the lower part of the window. In this view, you can change items such as the story name. The story size of set items is the number of work points required to complete the story. You can set these points using unique units such as hours, days and so forth, according to the project management policy. Normally, you enter the number of days that will be required to complete the story.

Item Description Initial Value
Feature Name Feature that includes this story Default feature in this release
ID No. for identifying object Serial no.
Name Content of story New story
Size Story size 1.0
Task Estimate Total Estimate total of tasks associated with this story 0
Initial Story Store created before starting the release true
Status Story status (Todo/Doing/Done) Todo
Color Story card color White (RGB {255,255,255})
Tag Story card tag Blank
Comment Story comment field Blank
  Table 3. property about a story

3-8. Creating and Setting Tasks

Next you need to set tasks that should be monitored in the project. Multiple tasks are associated with one story, which is a higher-order concept. At a work site, these tasks are used to confirm project progress.

Creating a task
Of the multiple iterations displayed on the story Kanban board, double-clicking an iteration in which you want to create tasks opens a task Kanban board. Task Kanban boards are divided into three portions, Todo (remaining work), Doing (ongoing work) and DONE (completed work). To add a task to a task Kanban board, click the task icon on the palette. After that, click the Todo section to create a task. To create multiple tasks, hold down the shift key and click once for each task you want to create.

  Figure 19. Task Kanban board

Setting a task
Next you need to add a story name, task name and estimate associated with a task. When you select a task, the property view in the lower part of the window changes to the task you selected, in which you can change the settings. For story name, from the list select a high-order story of the task. Now estimate the number of work points. You can set these points using unique units such as hours, days and so forth, according to the project management policy. Normally, you enter the number of hours that are required to execute the task. The color can be set but since the color allocated to the high-order story is set at the left of the task card, grouping is performed by that color. If there are common value items in multiple tasks, you can set them collectively. Select the frame (Marquee) icon on the palette and use the frame to marquee around multiple tasks. Then, change the desired item in the property view to input the item collectively.

Item Description Initial Value
Story Name Story associated with this task Blank
Task Name Description of a task New task
Status Task status (Todo/Doing/DONE) Status of lane where the task was created.
Remaining Remaining tasks 1.0
Estimate Estimated tasks 1.0
Elapse Achievement of tasks Blank
Initial task Task created before the iteration starts true
Signed up User who started the task Blank
Date created Date on which the task was created Current date
Date started Date on which the task was started Blank
Date completed Date on which the task was completed Blank
Deadline Task completion deadline date Blank
Ticket URL URL of Trac ticket created as card Blank
Color Task card color White (RGB {255,255,255})
Tag Task card tag Blank
Comment Task comment field Blank
  Table 4. property about a task

3-9. Project Progress and Monitoring

In TRICHORD, the status of an ongoing project is managed in each Kanban board.

Task Kanban board: Manages the daily progress of tasks.
Story Kanban board: Manages the progress of all of the stories in an iteration.
Feature Kanban board: Manages the progress of all of the features in a release.

3-9-1. Managing Tasks

By moving task cards in a task Kanban board, you can change the status between Todo, Doing, and DONE. Project members and managers can check the Kanban board to grasp the remaining and ongoing tasks and their volumes. Also, changes in remaining tasks can be checked on the burn down chart. In the burn down chart, daily remaining tasks are plotted and displayed on a downward line graph. Project members and managers understand changes in progress by looking at the way the graph moves down.

Operating a task Kanban board
To change the task status, open the task Kanban board allocated to the work period. Immediately after setting, all task cards are placed in Todo status. When project members have started their own task, use drag and drop to move the task card from Todo to Doing. At this time, the task properties are automatically updated. As updated items, the operation date is entered for Date started and the member ID is set for Signed up.

  Figure 20. Task Kanban board and cards

If the work period for a task runs multiple days and you want to manage the process in more detail, enter information such as how long it takes to finish the remaining task in Remaining. If you want to add special items that occur while working on the task, you can enter comments on the back side of the card. To flip over a card, click the icon you want to flip over. By directly editing the back of the card, you can enter comments (comment can also be entered from the Comment field in the Properties view).

  Figure 21. flip over icon

In addition to flip over, you can perform stack alignment, grid alignment and multiple selection using icons or a mouse gesture. For details of the operation method, see the section on mouse gestures in the manual.
When a task is completed, use drag and drop to move the task card from Doing to DONE. In this stage, the Completed check mark on the task card is displayed and the Date completed field is set to the date on which the task card was moved to DONE. Also, the work remaining becomes zero. As necessary, enter an elapse point in the elapse property.

In this way, change task statuses as needed to continually make it possible to grasp task statuses based on the Kanban board and take action if there is a problem in a task being worked on for a long time or a task has not been started for a long time.

Managing Task kanban among multi users
Task Kanban boards are usually shared and modified by multiple users. So we provide this merge function to help multiple users to work on a same Kanban Board more efficiently. With this merge function, when someone adds a new Task or updates Task Information, TRICHORD detects the modification and let others to import the new or updated information for each TRICHORD. By using "Auto merge to Task Kanban", TRICHORD updates the latest TASK information at a specified time interval. For details, see "Reference -> Setting -> TRIHCORD" in the manual.

"Auto merge to Task Kanban" is not available in following two cases.

  • When multiple users modified the same Task at the same time.
  • When the iteration period has been changed.

In above cases, TRICHORD cannot merge it automatically so it shows a dialog message to tell you that there is a conflict. (Figure 22) By pressing [OK], you can import modifications that another made over your changes. If you press [Cancel] button, an icon appears on the card to indicate that there is a conflict in Task. (Figure 23)

  Figure 22 Conflicting dialog

  Figure 23 Icon of conflicting card

Displaying a task list
Tasks displayed in card format on a Kanban board can be displayed in list format, as shown in figure 22. The list can be displayed by clicking the list tab in the task Kanban board. This view is used primarily when you want to edit remaining tasks retroactively. In this view, you can change a task name or remaining task but cannot create a new task.

  Figure 24 Task List View

Searching for tasks
You can use the search function to search for a specific task (you can also search for a particular story or feature). To search for a task, select Search from the menu to start the search function and then set search conditions and execute a search. The search result is displayed in the lower part of a Kanban board. The default display format is hierarchical format (Figure 25) but you can display the results in list format as well (Figure 26). To display the results in list format, click the list icon inside the red frame in figure 24. In list format, you can select data from the list and then copy and paste it into Excel to use as calculation data. For details, see "Pasting a card into an Excel table" in the manual.
  Figure 25 Hierarchical format

  Figure 26 List format

Using a task tree to understand the relationship between features, stories, and tasks
In TRICHORD, because they are divided, it can be difficult to use a Kanban board to understand the relationship between features, stories, and tasks. This view helps you to understand the relationship between them.
Normally, an outline is displayed in the left pane. Double-clicking here displays a tree. A task tree displays the hierarchical relationship between features, stories, and tasks. When you double-click a feature, story or task on the tree, the corresponding Kanban board opens and is the focus.
If the Task tab is not displayed, right-click the Kanban board icon (in the upper right hand corner of the Kanban board) and select reset from the displayed list to reset the view. This operation displays the Task tab.

  Figure 27 Task view

Using the Daily Burn Down Chart to understand the remaining tasks in an iteration
Changes in remaining tasks are displayed in a burn down chart. As shown in figure 26, a burn down chart that graphs the daily remaining tasks is displayed in the Daily Burn Down Chart on the left side of the tool. In the chart, the vertical axis is the total remaining tasks and the horizontal axis is the plotted remaining man hours by date. Team members and managers can use this chart to grasp work tendencies. Also, you can press Ctrl+M to maximize the size of the burn down chart.

  図28 Daily Burn Down Chart

3-9-2. Managing Stories

Using stories, you can manage the progress of work in a release based on a story Kanban board and Iteration Burn Down Chart.

Managing a story in a story Kanban board
You can open a story Kanban board by selecting it from the tree or double-clicking the desired release in the feature Kanban board. As shown in figiure 29, when the tasks under control are all completed, a check mark on the story cards inside a story Kanban board indicates that the tasks are completed. Also, ongoing stories are indicated by circulating arrows (ongoing means that even though only a small number of tasks are under control, one task is still in Doing status).

  Figure 29 Story Kanban board

Using an Iteration Burn Down Chart to confirm the progress of a story
The remaining stories in a release are displayed in the Iteration Burn Down Chart. An Iteration Burn Down Chart is a graph of the remaining stories in each iteration. In the chart, the vertical axis is the remaining stories (the total of the size set when creating stories), and the horizontal axis is the iteration where completed stories in the iteration are plotted. When all tasks in a story are completed, the remaining stories are reduced by this size and the chart is updated. As shown in figure 30, an Iteration Burn Down Chart is displayed on the right side of the tool. Managers can use this chart to grasp work tendencies from a wide aspect. Also, you can press Ctrl+M to maximize the size of the Iteration Burn Down Chart.

  Figure 30 Iteration Burn Down Chart

3-9-3. Managing Features

Using the feature Kanban board to manage the progress of a feature
In order to grasp the status of tasks under control, as shown below, in feature cards status is represented by colors so that the progress of stories under control can be understood at a glance. Also, a graph is provided to make it easier to grasp the progress level. This view is the top view primarily used by project owners and project managers who manage multiple projects.

About numbers x and y displayed on a feature card, x is the total size of the completed stories and y is the total size of stories under control. The bar graph on the card changes according to the ratio between story size and completed story size.

Image Background color Description
Todo_feature White Todo feature
Doing_feature Skyblue Doing feature
DONE_feature Green DONE feature
AT_feature Red Uncompleted feature for which the deadline is expired

  Figure 31 A parking lot chart view about feature

  4. Using Niko-niko Calendar to Share Team Status

As shown in Figure 32, by using Good, OK, and Bad status to enter their qualitative status themselves, which is similar to making diary entries in Niko-niko Calendar (, team members can share the atmosphere of the team, which cannot be easily captured and represented numerically. Click the open perspective icon of TRICHORD to open the Niko-niko Calendar perspective, in which members are displayed on the vertical axis and the date is displayed on the horizontal axis.

  Figure 32 Niko-niko Calendar(Customized icon)

When you double-click a day, the setting window shown in figure 31, in which you can enter the status and a short comment. Short comments are displayed when focus is placed on each mark in the calendar. Also, other members can add comments. This calendar allows team members to share the overall mood and feeling of the team and deepen communication by mutually adding comments. Members can customize member images and status icons used in the calendar. For details about customization, see the manual.

  Figure 33 Paste feeling dialog


  5. Other Functions

Using WebReport to view multiple projects statuses
TRICHORD provides WebReport, which is a tool lets you view burn down charts and task lists in web based content. WebReport loads workspace files that are specified by an independent program then generates HTML in where you specify. You can select plural workspace files and make them in one Web content. WebReport is stored in TRICHORD Install folder and is available by using Command line or GUI. Please refer to manual for more details.
WebReport is stored in the folder where TRICHORD is installed and can be used either from a command line interface or a GUI. For details, see the manual.

Trac connection
Trac tickets, which are widely used for ticket management, can be loaded into a Kanban board as TRICHORD tasks and users can monitor changes in status using the visual effect of Kanban board and reflect the completed status in the repository. For details, see the Trac section in the manual.

Mind Map connection
TRICHORD can mutually connect with Astah Professional Mind Map. Users can paste TRICHORD cards to Astah Mind Map or paste topics from Astah Mind Map to TRICHORD Kanban board. For details, see the Mind Map Connection section in the manual.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Mind Map is a registered trademark of the Buzan Organisation Ltd.
Other systems and products are each maker's registered trademark.
(C) Copyright Change Vision, Inc. 2007-20012. All Rights Reserved.