
This section is a platform - a base for creating and managing the main artifacts of our platform. Here you can create tasks, create a backlog from them, plan a sprint, and set goals.
Team Products - A list of products your team is working on. If there are several products, then you can switch between them with swaps. Immediately after the switch, the content under the product will be updated.
Product Ideas is a special tool for capturing product ideas. It's very simple: you just write down your ideas within a category.
The product backlog is a tool for displaying product tasks. You can prioritize tasks as well as view task details.
Active sprint - if there is an active sprint, you can look at its tasks in the form of kanban, as well as the number of story points in the context of each task status.
Product Sprints - You can view a list of product sprints, view details of already completed sprints, and create a new sprint.
Business goals - in this section you can set goals for your products, as well as select tasks that will allow you to achieve this goal.
Product Increments is a section where you can see what tasks have been completed within past completed sprints.
Product support - a section with which you can create, view the details of a user case. Also in this section you can transfer tasks between 3 support lines, and view tasks in kanban mode.
Product quality - a section in which test cases are created for the functionality of the product. Also in this section there is a functionality that allows you to pass these cases any number of times.

This section is necessary for fixing thoughts and hypotheses, on the basis of which tasks will be created. To write down an idea, you need to click the add idea button on the ideas screen, and then select an idea category. Categories are created for the convenience of classifying ideas - so that there is order.

The product backlog is the main tool for displaying and managing product tasks. in this section, you can create, delete, and prioritize product tasks.
if you need to see the tasks of another product, swipe the product list menu at the beginning of the product section.

Task filtering is necessary in order to display a list of tasks that match your requirements.
But it is important to remember that after filtering, the prioritization mechanism is blocked and becomes unavailable.

The detailed information page contains a lot of useful information: description, type, priority, completion status, list of subtasks, storypoint score, information about the performer, as well as the status of the backlog update request for this task.
From this screen, you can create a discussion stream for this pama issue if you need to discuss some details with team members.

The tasks of a running sprint are displayed on a kanban board for easy management of their status. Clicking on a task opens a screen with details for that task.

With this section, you can create a new sprint, plan it with the team in PamaSync interactive mode, and close it.
Clicking on a sprint will open the sprint details screen, which contains information about the goals, dates, and tasks that were completed in that sprint.

To fulfill a business goal, you need to complete several tasks performed in several stages. To set goals on the platform, there is a separate type of task - business goals.
In this section, you can create a goal, while specifying the conditions for fulfilling this goal, a description, and an owner.
You can add a task to a goal on the task detail view screen.

In Scrum, each sprint should end with the creation of a product increment - new functionality that users will see.
This section allows you to see what features were released after each sprint.

Product support is a simple and convenient tool for working with helpdesk tasks.
Here you will find tasks 1, 2, 3 lines of support, a kanban board that displays all tasks.

This section provides functionality for creating and managing functional testing test cases.
When creating a test case, you specify the tasks that will be tested, as well as the steps that the tester needs to go through.

A functional tester can select the required test case from the list and then go through its steps with the expected and actual behavior of the system. If an error is found at some step, the tester fixes it and immediately creates a defect.