{"id":154,"date":"2023-12-10T18:05:22","date_gmt":"2023-12-10T18:05:22","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=154"},"modified":"2025-12-31T10:22:03","modified_gmt":"2025-12-31T10:22:03","slug":"how-to-create-a-scrum-project-in-jira","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/agile\/how-to-create-a-scrum-project-in-jira\/","title":{"rendered":"Creating a Scrum Project in JIRA: Complete Guide"},"content":{"rendered":"\r\n

This blog\u2019s “How To Create A Scrum<\/a> Project In JIRA?” main idea is to guide project teams to make full use of JIRA to run a scrum project.<\/p>\r\n\r\n\r\n\r\n

Jira is a sophisticated tool which is highly designed to run Agile projects. With predefined templates, boards, reports and metrics, it is one of the most used tools to run Agile projects in the industry.<\/p>\r\n\r\n\r\n\r\n

Context :<\/strong>\u00a0We have explained how best to use JIRA in scrum project and what should be taken care of in the \u201cPlanning and Initiation\u201d phase of a project and \u201cExecution\u201d phase of the project with Scrum framework.<\/p>\r\n\r\n\r\n\r\n

Pre Requisites<\/strong><\/p>\r\n\r\n\r\n\r\n

Before we jump into the main topic, let\u2019s read through the list of prerequisites which have to be taken care of before starting using JIRA is scrum project.<\/p>\r\n\r\n\r\n\r\n

    \r\n
  1. New Project created with Scrum template ( Please select if the project is Team managed \/ company managed based on what is followed in your company )<\/li>\r\n\r\n\r\n\r\n
  2. A project group in JIRA is created for the development team and they are added to the project. Appropriate permissions are given to the team members<\/li>\r\n\r\n\r\n\r\n
  3. \u201cIssue Types\u201d are configured as per need<\/li>\r\n\r\n\r\n\r\n
  4. \u201cFields\u201d are configured and associated with the project created<\/li>\r\n\r\n\r\n\r\n
  5. \u201cWorkflow\u201d is configured as per need for all the issue type and the scheme is assigned to the project<\/li>\r\n\r\n\r\n\r\n
  6. \u201cComponents\u201d and \u201cLabels\u201d are pre defined in the project<\/li>\r\n\r\n\r\n\r\n
  7. \u201cBoards\u201d are created by applying appropriate settings<\/li>\r\n\r\n\r\n\r\n
  8. Estimation type \u201cHours \/ Story points\u201d is defined and configured in the screens and boards<\/li>\r\n\r\n\r\n\r\n
  9. And Of course, team members are trained on JIRA basics<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n

    Planning And Initiation<\/strong><\/p>\r\n\r\n\r\n\r\n

    This is the phase where the backlog is getting created after the discovery session \/ PI planning \/ release planning. Post story map creation, EPICS and STORIES are created and roughly estimated using story point estimation or T-Shirt sizing. Let\u2019s understand how to use JIRA for creation of a backlog and a few things we should take care of.<\/p>\r\n\r\n\r\n\r\n