{"id":32338,"date":"2023-10-11T04:10:08","date_gmt":"2023-10-11T04:10:08","guid":{"rendered":"https:\/\/www.process.st\/templates\/how-to-use-a-jira-epic\/"},"modified":"2024-03-05T14:28:47","modified_gmt":"2024-03-05T14:28:47","slug":"how-to-use-a-jira-epic","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/how-to-use-a-jira-epic\/","title":{"rendered":"How to Use a JIRA Epic"},"content":{"rendered":"\n
\n

Access JIRA and navigate to project<\/h2>\n
\n Access JIRA and navigate to the project in order to start working on the Epic. By accessing JIRA, you will be able to view and manage all the tasks related to the project. \n <\/div> \n<\/section> \n
\n

Identify and select Epic from JIRA menu<\/h2>\n
\n Identify and select the desired Epic from the JIRA menu. This will allow you to work specifically on that Epic and its associated user stories. \n <\/div> \n<\/section> \n
\n

Understand Epic summary and its details<\/h2>\n
\n Take the time to understand the summary and details of the selected Epic. This will provide you with important information about the goal and scope of the Epic. \n <\/div> \n<\/section> \n
\n

Review Epic's requirements and constraints<\/h2>\n
\n Review the requirements and constraints of the Epic. Understanding these will ensure that you are aware of any limitations or specific conditions that need to be considered while working on the Epic. \n <\/div> \n<\/section> \n
\n

Approval: Requirements Review<\/h2>\n
\n
\n
\n Will be submitted for approval:\n <\/div> \n <\/div> \n
\n
    \n
  • \n
    \n
    \n
    Review Epic's requirements and constraints<\/span> \n
    \n Will be submitted\n <\/div> \n <\/div> \n <\/div> \n <\/div> <\/li> \n <\/ul> \n <\/div> \n <\/div> \n<\/section> \n
    \n

    Break Epic down into smaller user stories<\/h2>\n
    \n Break down the Epic into smaller user stories. This will help in organizing and managing the work more effectively, as well as enable better tracking of progress. \n <\/div> \n<\/section> \n
    \n

    Create and connect issues to populate user stories<\/h2>\n
    \n Create and connect issues to populate the user stories. This step will ensure that each user story has a specific issue assigned to it, making it easier to track and manage. \n <\/div> \n<\/section> \n
    \n

    Assign team members to each user story<\/h2>\n
    \n Assign team members to each user story. This will distribute the workload among team members and ensure that everyone is assigned specific tasks to work on. \n <\/div> \n<\/section> \n
    \n

    Set priorities for user stories within Epic<\/h2>\n
    \n Set priorities for the user stories within the Epic. This will help in determining the order in which the stories should be completed, ensuring that the most important ones are given priority. \n <\/div> \n<\/section> \n
    \n

    Create a timeline for completing user stories<\/h2>\n
    \n Create a timeline for completing the user stories. This will provide a clear plan and schedule for completing each story within the Epic, helping to ensure timely execution. \n <\/div> \n<\/section> \n
    \n

    Approval: Timeline Creation<\/h2>\n
    \n
    \n
    \n Will be submitted for approval:\n <\/div> \n <\/div> \n
    \n
      \n
    • \n
      \n
      \n
      Create a timeline for completing user stories<\/span> \n
      \n Will be submitted\n <\/div> \n <\/div> \n <\/div> \n <\/div> <\/li> \n <\/ul> \n <\/div> \n <\/div> \n<\/section> \n
      \n

      Update Epic status regularly<\/h2>\n
      \n Update the status of the Epic regularly. This will allow you to track the progress of the Epic and identify any issues or delays that need to be addressed. \n <\/div> \n<\/section> \n
      \n

      Coordinate with team members for smooth execution<\/h2>\n
      \n Coordinate with team members for smooth execution of the user stories. This will involve regular communication and collaboration to ensure that all team members are aligned and working towards the common goal. \n <\/div> \n<\/section> \n
      \n

      Track progress of user stories in Epic<\/h2>\n
      \n Track the progress of the user stories in the Epic. This will involve monitoring the completion of each story and updating the status accordingly. \n <\/div> \n<\/section> \n
      \n

      Manage changes to user stories or Epic<\/h2>\n
      \n Manage any changes that arise in the user stories or Epic. This will require careful documentation and communication to ensure that all team members are aware of and can adapt to the changes. \n <\/div> \n<\/section> \n
      \n

      Approval: Changes Management<\/h2>\n
      \n
      \n
      \n Will be submitted for approval:\n <\/div> \n <\/div> \n
      \n
        \n
      • \n
        \n
        \n
        Manage changes to user stories or Epic<\/span> \n
        \n Will be submitted\n <\/div> \n <\/div> \n <\/div> \n <\/div> <\/li> \n <\/ul> \n <\/div> \n <\/div> \n<\/section> \n
        \n

        Resolve dependencies and blockers<\/h2>\n
        \n Identify and resolve any dependencies or blockers that may arise during the execution of the user stories. This will involve addressing any challenges or issues that may hinder the progress of the work. \n <\/div> \n<\/section> \n
        \n

        Perform necessary testing after completion of user stories<\/h2>\n
        \n Perform necessary testing after the completion of each user story. This will help ensure that the implemented solution meets the desired requirements and functions as expected. \n <\/div> \n<\/section> \n
        \n

        Close user stories upon successful completion<\/h2>\n
        \n Close each user story upon successful completion. This will mark the completion of the individual user stories, allowing the team to focus on the remaining work. \n <\/div> \n<\/section> \n
        \n

        Close Epic upon completion of all user stories<\/h2>\n
        \n Close the Epic upon completion of all user stories. This will indicate the successful completion of the entire Epic and its associated tasks. \n <\/div> \n<\/section> \n
        \n

        Approval: Epic Closure<\/h2>\n
        \n
        \n
        \n Will be submitted for approval:\n <\/div> \n <\/div> \n
        \n
          \n
        • \n
          \n
          \n
          Close Epic upon completion of all user stories<\/span> \n
          \n Will be submitted\n <\/div> \n <\/div> \n <\/div> \n <\/div> <\/li> \n <\/ul> \n <\/div> \n <\/div> \n<\/section>\n","protected":false},"excerpt":{"rendered":"

          Access JIRA and navigate to project Access JIRA and navigate to the project in order to start working on the Epic. By accessing JIRA, you will be able to view and manage all the tasks related to the project. Identify and select Epic from JIRA menu Identify and select the desired Epic from the JIRA […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"\ud83d\udccb","cover_icon_url":"","tasks_count":"21","template_description":"","template_id":"vcSqyK7apqVX4vtm4KVKfQ","task_0":"Access JIRA and navigate to project","task_slug_0":"access-jira-and-navigate-to-project","task_1":"Identify and select Epic from JIRA menu","task_slug_1":"identify-and-select-epic-from-jira-menu","task_2":"Understand Epic summary and its details","task_slug_2":"understand-epic-summary-and-its-details","task_3":"Review Epic's requirements and constraints","task_slug_3":"review-epics-requirements-and-constraints","task_4":"Approval: Requirements Review","task_slug_4":"approval-requirements-review","task_5":"Break Epic down into smaller user stories","task_slug_5":"break-epic-down-into-smaller-user-stories","task_6":"Create and connect issues to populate user stories","task_slug_6":"create-and-connect-issues-to-populate-user-stories","task_7":"Assign team members to each user story","task_slug_7":"assign-team-members-to-each-user-story","task_8":"Set priorities for user stories within Epic","task_slug_8":"set-priorities-for-user-stories-within-epic","task_9":"Create a timeline for completing user stories","task_slug_9":"create-a-timeline-for-completing-user-stories","task_10":"Approval: Timeline Creation","task_slug_10":"approval-timeline-creation","task_11":"Update Epic status regularly","task_slug_11":"update-epic-status-regularly","task_12":"Coordinate with team members for smooth execution","task_slug_12":"coordinate-with-team-members-for-smooth-execution","task_13":"Track progress of user stories in Epic","task_slug_13":"track-progress-of-user-stories-in-epic","task_14":"Manage changes to user stories or Epic","task_slug_14":"manage-changes-to-user-stories-or-epic","task_15":"Approval: Changes Management","task_slug_15":"approval-changes-management","task_16":"Resolve dependencies and blockers","task_slug_16":"resolve-dependencies-and-blockers","task_17":"Perform necessary testing after completion of user stories","task_slug_17":"perform-necessary-testing-after-completion-of-user-stories","task_18":"Close user stories upon successful completion","task_slug_18":"close-user-stories-upon-successful-completion","task_19":"Close Epic upon completion of all user stories","task_slug_19":"close-epic-upon-completion-of-all-user-stories","task_20":"Approval: Epic Closure","task_slug_20":"approval-epic-closure","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[29,113],"tags":[],"class_list":["post-32338","post","type-post","status-publish","format-standard","hentry","category-healthcare","category-medical"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/32338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=32338"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/32338\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=32338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=32338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=32338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}