{"id":4065,"date":"2021-04-23T11:50:26","date_gmt":"2021-04-23T09:50:26","guid":{"rendered":"https:\/\/www.actonic.de\/staying-organized-with-jira\/"},"modified":"2023-03-29T11:53:47","modified_gmt":"2023-03-29T09:53:47","slug":"staying-organized-with-jira","status":"publish","type":"post","link":"https:\/\/actonic.de\/en\/staying-organized-with-jira\/","title":{"rendered":"Staying organized with Jira"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text]<\/p>\r\n

Atlassian has developed the project management software Jira to help you to overcome exactly these challenges of your everyday work life. Jira helps you as a guide, similar to a map during hiking, to conquer the workload. The tool provides you a route through tickets, sprints and stories and gives you guidance in complex work routine. But to arrive safely at your wished destination, you have to use these instruments in the correct way. Otherwise, you could deviate from the right route.<\/p>\r\n

This article is serving you as an orientation for effective usage of Jira in project management. We will deliver useful best practices, which will improve your project management and team work drastically.<\/p>\r\n

[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][heading title=”Sprint planning” heading=”h2″ font_weight=”” el_id=”1619169739520-27becf9a-8b4c”][vc_column_text]<\/p>\r\n

You can prevent typical problems in project work with Jira in advance, through the right sprint planning and the correct creation of tickets.<\/p>\r\n

These are the three most important tips:<\/p>\r\n

    \r\n
  1. Conservative sprint planning:<\/strong>
    It is important to pay attention to<\/span> planning your sprint rather conservative. If you drag a high amount of tickets in your new sprint, it could happen, that you lose the overview about the tasks and the priorities. Through a properly and realistically planned sprint you avoid half completed tasks and can focus on the most important tickets.<\/li>\r\n
  2. If time is left, grab tickets from the backlog:<\/strong>
    You can use the length of two working days as a benchmark for the amount of time to include into your weekly sprint. This may sound a bit low first, but it is always useful to plan in some time for meetings and unpredictable delays. If there is some time left at the end of the sprint, you can always pick more tickets of your backlog or of future sprints and work on them.<\/li>\r\n
  3. Prioritize tickets – Order tickets by their urgency:<\/strong>
    It is useful to rate your tickets in your sprint planning with a priority and sort them by their urgency. This helps keeping an overview and an eye on tickets which the highest urgency. If you want to start a new ticket, you can choose directly the most urgent one. If you work with prioritization, you can be sure, that the most important tickets are finished at the end of the sprint.<\/li>\r\n<\/ol>\r\n

     <\/p>\r\n

    Best practices in sprint planning<\/h4>\r\n