How to use SaaS tools, the better way

In this article, we will explore how to check how tasks are linked as well as the overall work schedule using Jira's roadmap feature, after creating a scrum board. If you haven't already created a scrum board within Jira, I recommend that you first check out this article: Project management using Jira scrum boards. In general, when working through a sprint, tasks tend to form links among themselves. The following is how a team using scrum may go through a software development process: Identify a problem Forge a hypothesis Draft a solution Add details to the solution Implement the solution Verify the hypothesis Analyze the result and retrospect While going through the above process, the team cycles through planning-design-development, during which task links form. This is not just for small tasks; if there are projects that must precede other projects, then links can form between projects as well. Using Jira, you can visually organize such links between tasks and projects, as well as work schedule and timelines. You can check in real-time the progress of each task, who the assignees are, and timeline changes when rescheduling occurs, which can help you reduce communication costs substantially. Changing default settings before using roadmaps Add Start date and Due date in issue fields Add the 'Start date' and 'Due date' fields in the issue fields settings page, as shown in the previous article Project management using Jira scrum boards. Change the way roadmap child-level issues are scheduled From the same board settings page, select the 'Roadmap' menu on the left-hand side, activate 'Child-level issue scheduling', and then select 'Schedule child issues by dates'.

With the advent of startups, there has been an increasing interest in the way startups work. As it became known that most successful startups used the agile methodology, more and more companies have adopted it. There are many project management tools that are used to implement agile, one of the most famous of which is Atlassian's Jira, popular with both small startups and large corporations alike. However, due to Jira's complicated features and high learning curve, many of you may be hesitant to start using it. In this article, I plan to provide an easy and comprehensive guide to starting a Jira project and actually using it in practice, so that even those of you using Jira for the first time can start using it with ease. We'll take a look at how to implement the scrum methodology of operating a sprint, one of the most widely used agile methodologies, along with real-life examples. (Agile is a comprehensive methodology for project management, while scrum is a type of framework used to implement agile.) Creating a scrum board project on Jira Let's start with creating a project, so that even a Jira novice can follow along. 1. Select 'Scrum' from the Software development category Select the 'Scrum' board from the software development category. 2. Team-managed vs Company-managed Once you have selected the Scrum board, you can choose between team-managed and company-managed projects. The team-managed option is for easy access to simplified features, while the company-managed option provides you with various customized features so that you can tailor the project to more diverse purposes. If you plan to manage various types of software projects, or if you need to aggregate other business tasks into a single board, then you should choose the company-managed option. On the other hand, one of the benefits of the team-managed option is that each team is free to customize its board to fit their individual needs without being limited by shared rules set as part of company policy. I recommend that you consider the 2 cases and choose the option more suited to your team. In this article, we will be choosing the company-managed option to guide you through how to manage multiple issues from different projects from a single combined board. 3. Set the project name and key Now, select the name of your project as well as the project key. The key is used as a marker to manage each per-task issue, so make sure to set it to a value such that you can easily tell which project an issue is in via the key.