Working on the preliminary version of the project and review article

Jira

An important competency of a technician (engineer) includes time management techniques, whose primary purpose is to increase the efficiency of time utilization. Planning is particularly interesting especially in cases when there are multiple tasks. Attention management for important events over time can be implemented at various levels of complexity or intelligence (from the simplest recording of tasks on paper, electronically, through reminders on mobile including visual/audio notifications, using dedicated applications such as calendars, diaries, with the ability to set priorities in the context of tracked goals, etc.).

For this reason, we will try planning and managing our own activities using the Jira tool. This tool's provided functionality exceeds the needs defined by the task list below. Within the MIP course, we will not fully utilize the provided capabilities, especially those for teamwork. However, it is an opportunity to become familiar with an environment that you will certainly use during your studies or professional life.

Jira is a software tool for bug/issue tracking in software development or agile project management, developed by Atlassian. Jira supports and facilitates the process of project and requirements management, offering flexible and user-friendly tools for managing and tracking workers in performing tasks. It is oriented towards supporting the achievement of expected performance on a project. Jira is offered primarily as a cloud service. Jira Cloud for teams up to 10 users is provided free of charge.

Tasks:

1. Register at https://www.atlassian.com/software/jira/free
2. Create a cloud site at <yourSiteName>.atlassian.net. Choose an appropriate name derived from the specification of your framework topic. Some names may already be taken.
3. From the available templates, select Scrum
4. Rename the preset "SCRUM Sprint 1" to "Exercise No. 4"
5. Define/Create a new issue as type Task. Take the task text from the task list for Exercise No. 4
6. Double-click on the created task to edit its properties: Assign the created task to yourself (Assignee)
7. Gradually add all tasks from Exercise No. 4 to the first sprint
8. Set the sprint duration to one week as it occurred according to the calendar and start the sprint
9. In menu->Board, move individual tasks in columns (Todo, In progress, Done) relevant to their status. The goal is to have all tasks from Exercise No. 4 in the Done state and column
10. Create a new sprint named "Exercise No. 5". Edit all tasks from Exercise No. 5 in it as "issue type task"

Integration of issues and code (Jira vs GitHub)

Issue keys are unique identifiers for each task you track in the Jira system. A Jira issue key is a "ticket number" for a task defined in Jira. It consists of a project key (up to 10-letter project ID), a hyphen, and then a sequential number. It must be in the commit message for the integration between Jira and GitHub (or GitLab or Bitbucket) systems to work.

Tasks:

1. Perform these tasks as a team. For this purpose, you need to have one shared GitHub repository created. Each team member will also create an individual local copy of the Git repository on their machine. In addition, create a shared "Jira" cloud site at <yourSiteName>.atlassian.net. Use the built-in "Software development template" named Scrum. Derive the necessary names from your project name.
2. Together in Jira, create/edit tasks in the backlog related to work on the project and review article. Try to exhaust/think of as many as possible. If you forget some, you can edit them later. Get inspired by the requirements for evaluating the final version of the project.
3. In Jira, create a new sprint, e.g., sprint_1_week_5.
4. Move from the backlog to the newly created sprint those tasks that relate exclusively to the Working version of the project. Decide on the complexity of each task. Do this by assigning corresponding Story points (Story point estimate). Subsequently, associate each task with a specific team member, ideally according to preference or "by drawing straws". Start the sprint: sprint_1_week_5.
5. Then continue working on the project and review article.
6. Commit each task defined in the sprint "sprint_1_week_5" locally to Git and then to the shared cloud repository on GitHub in the following way: git commit -m "<Issue key, task number> <actual message text>"
7. Finally, before the end of the exercise, save all changes to the document committed to the local repository to a file named git_log.txt. Use the command git log > git_log.txt for this. Make sure that the file was created in your local repository and its content corresponds to reality.
8. Continuously indicate the status of task implementation on the board (Board tab).