Tasks on GitScrum
# What is it and how does it work?
In this material, you will see how to create and manage your tasks on GitScrum. There are many possibilities in a single task to optimize the work and performance of your team. After creating your project, you can start documenting your tasks in the platform, and this guide will give you a great view of how to do it in the best way possible.
# Understanding the good practices
On project management studies, specifically regarding the scope, it is said that the tasks are the smallest work package considered in a project. That way, the work must be fragmented until the moment that the team judges it as an ideal specification of the work, to then move forward. A hypothetical example we can consider is the development of a website which scope can be defined in a few pages, such as: “Home,” “About us,” “Contact Us,” “Products.” At this moment, a work package was broken down into four others. If the team wants, these four packages can be broken down once again. For example:
- Main Slideshow;
- Recent YouTube videos;
- Main products;
- Institutional text;
- Pictures of the organization;
- Mission of the organization;
- Product list;
- Most purchased products;
- Most viewed products;
- Contact form;
- Clients’ testimonies;
After this breakdown, we will have an even bigger number of tasks, which provides more control over the scope and schedule of the project. However, the leader of the project must always make sure that the tasks have a congruent “size,” because besides the example above, if there was yet another breakdown, the daily operation of this scope could become excessively consuming.
# How to create a task
To create your tasks on GitScrum you must access the project to which scope you will add this task. From the access to the project, you can click on “Project Options” (Step 01), and then choose the option “Create Task” (Step 02), and then you will see the setup page for your new task.
On the page that appears, you can fill out some fields regarding your task, in order to generate more information in your project. These sets of information are:
A - User Story: GitScrum enables you to link a task to a User Story that is part of your project by selecting it at the provided list. You can understand more about this feature in its specific section.
B - Sprint: Sprints are fractions of the time schedule and group a certain scope. For that to happen in GitScrum, you only need to select in this field to which sprint the task is linked. You can also learn everything about sprints in its specific material.
C - Task title: In this field, you must fill out the title of your task in a clear and objective way. Try always to specify names for the tasks in a way that there is no doubt about the work to be executed.
D - Task Description: When necessary, you can use this field to provide more details about the work that must be performed in this task. You can add useful links and any other text information in this field.
E - Task type: In this field, you can select the type of task that is being created. GitScrum suggests a list of standard types when a new project is created. However, you are free to customize this list according to your needs.
F - Task Effort: In this field, you can fill out the effort estimation for each task. And as with the types, GitScrum suggests a specific list of options following quick principles.
G Assign to: In this field, you can assign specific people to perform the task that is being created. All the members of the project team will be available to be linked to a project task.
H: Finally, you can add the BUG options, which shows that this task is a BUG, or you can highlight it as a draft, and in this case, it will only be available to you.
After going through these steps, your task will be created, and from that moment on, you will have new interaction features with your team. You can also add more information about the task.
# How to edit and manage a task
After creating a task on GitScrum, you will have access to some very interesting new features that will facilitate the management of the work that needs to be developed, as well as the team’s internal communication. To have access to these new options, you must click on a certain task. See how to do it on the board planning and the task page on the images below.
Checklists can be used in many different ways, according to your need, such as task requirement premises, which can be validation items for the completion of the work. GitScrum enables you to create many checklists in a task.
By using GitScrum, you can manage the time spent performing a task. On the Tracking tab, you can add time entries, such as the day the work was performed, as well as the start and end times. That way, GitScrum will calculate all the registered entries, showing the total time invested in this task.
This is a great internal communication tool. With comments being made directly on the tasks, the activity log is much more effective, and all conversations among the team are logged practically, with easy access for future queries.
The same way as the comments, GitScrum enables you and your team to attach support files on the tasks, such as templates, or any other type of support material, which can be attached to a task, facilitating the future execution of the work.
The labels are a way of grouping tasks. You have the freedom to create as many and which labels you wish. While each task can only have one type, it can be related to many labels. Therefore, with this communication, your tasks will be sorted as they’ve never been before.
# Task Dates
A great way to measure the work progress in GitScrum is by taking the most advantage of the sprints, which you can learn about in another material. One way to increase even more the time control and management in your project is by using the start date and end date parameters in your task. That way, you can always confront the data in these fields with the tracking time information, generating more knowledge to your team.
This feature can and must be used every time your team feels the need to break down a large task into small steps to optimize your management, facilitating the control of the work progress. The subtasks are like normal tasks. However, they carry with them their link to their mother task, making it easier to identify it at the board planning and also at the task view.