First steps for your project
# What is it and how does it work?
GitScrum is a project management tool for agile teams
The start of the workflow in GitScrum is considered as the moment a user creates a new project in their account. On GitScrum, the projects are elements that derive from a company, which are owned by users.
You can access this list with more details in another material, but at this point, it is enough to know that by having a user account in the platform, you are already able to create new projects.
# Understanding the best practices
Bibliography regarding Project Management state that a project is elementary made up by five pillars, which are: Time, the Resources involved, the Scope of the job, the Goal of the project and your Need.
Each of these elements has an important role during the life of a project, and badly estimated resources can lead to crises and urgent needs with a high degree of difficulty to react to them, a badly designed scope or with a poor requirement survey can lead to great divergences during the project releases, which in extreme cases, lead the project to be terminated even before its conclusion.
The fact is that projects, when planned, are in a generous range of success indexes, and that is why on GitScrum the scope and schedule planning processes can be developed simply and practically, from the ground zero of your project, and we will see how below.
# How to create a Project?
To create a project in GitScrum you need to follow some very simple steps.
Notice that it is necessary to log in to the platform to access the panel you will see on the image below, so only follow this guide after you have logged in.
In any page on GitScrum, click on the option “Projects” on the upper menu, shown in the image above as Step 01, and you will be immediately taken to your projects page, where you can visualize all the projects to which you and your team are signed up.
Going to the project registry, click on the “CREATE PROJECT” button, shown on image as Step 02, and you will be directly taken to your screen to provide the first set of information about your new project.
In this new screen that appears, you can fill out five fields about your project to generate a richer registry in your documentation in the Project Management.
1. Project Name: In this first field, you just need to say what is the name of your project, that is, the ludic way in which you and your team will identify this project.
2. Code: The code field helps the team identify the project. In some teams, it is common to use external documents, and in some cases, a project might be linked to other records, such as contracts, etc. If in your organization there is a unique identifier defined for the project, you can use this field to keep this link.
3. Related Project: In this field, you will be able to relate a new project to another existing one. This field can be very useful for teams that work with large projects and choose to share the work into projects with a smaller scope, or in other cases, when there are many teams simultaneously working in the project, and like that, the manager can decide to make this subdivision. If you do not wish to create this relationship, choose the option “It’s a Master Project” and move on to the next field.
4. Visibility: A project’s visibility defines if a GitScrum user can or not access your project. If the setting was defined as a public project, any GitScrum user can see that project. Therefore, if you wish to have more privacy and secrecy, choose to create a private project, and like that, only those that you allow will be able to access your project. Learn more
5. Goals: Once you are almost done registering your project, you can use this field to define the goals of your project. Remember that the definition of goals is extremely important for further assessment of the results that will be obtained throughout time, and besides, sharing goals among the team is a great motivator for everyone when performing their jobs.
By filling at least the mandatory fields that correspond to numbers 1 and 4, you can finish the registration of your project by clicking the button “CREATE PROJECT” and you will be ready to start working with your new project.
# How to edit the project’s basic data?
If you wish to update any basic data of your project among those that you informed during the project registration, you just need to follow two very simple steps.
From any screen you are navigating in the project you want to edit, click on the “Settings” menu shown on the image below, and you will see the screen where you can update your data. On this screen, you can also set up some options for your project.
In this case, the information wasn’t collected at the initial project setup, and the following options are available in the registry page:
Show task identifier: When this option is active, all your tasks in the project will be displayed with a prefix in your name. For example, for the “Bake the cake” task, when this option is active, it will be shown as “#TK-1 Bake the Care”. Note that the number is automatically generated.
Maximum WIP per user: In this field, you can define what is the maximum number of tasks that a user can keep active. That is, the total tasks someone can perform at once.
# How to define a project’s team?
To define your team in this new project, you must access the “Settings” menu, which is available at the sidebar in every page while navigating at a project.
After accessing the settings menu, you must select the “Team” option, as shown on the image by number 2.
Next, you will be able to link the users of your organization to your new project.
# How to create quick tasks in the project?
You can create tasks on GitScrum in a very simple and quick way.
The first step is, from the access page of your project, access the “Project Options” menu shown by number 1 on the image below, and then click on the option “Create Task” shown by number 2.
Next, your screen will show a modal window for you to log tasks and your initial set of information, which are:
Task Title: In this field, you must register the task title in a way that the identification of the work that needs to be performed is clear.
Description: In this field, you can document the work that needs to be executed in details. It works as a support material for the person who will be later working in this activity.
Type: The type must be selected to identify how the work is being divided. Using this field enables the identification of the work that needs to be done and later, generates accurate reports and charts regarding the activity in the platform.
Effort: In this field, you must fill out the estimated effort for the task. It is important to highlight that the effort field, as well as the type field, can be set up for each project. That is, you can have a list with effort options and task types for each project, and you will see how to set it up in another section.
Assigned to: In this field, you must select the members of the project that must work in this activity. Note that it is possible to assign more than one member to each task.
Bug and Draft: When finishing the setup of your ask, you can classify it as a “bug”, which is extremely recommended for correction activities since later, it is possible to visualize metrics such as the bug rate of your project, for example. And you can also classify the task as a draft, and in this case, the task will be only visible when you have this setup.