Creating Sub-Epics in JIRA Core
In a previous article I discussed creating a Business Epic within a JIRA Core customized Project to capture key business stakeholder requirements to support the selection, configuration and go-live launch of a business team calendar solution.
In this article, we're going to take a look at creating business Sub-Epics in a JIRA Core customized project. Business Sub-Epics are created to provide more detailed requirements information of some aspect of a previously defined Business Epic.
Continuing on with elaborating on the business requirements for configuring the Team Business Calendar application, let's review the parent Business Epic in JIRA:
The "Team Calendar Application" Business Epic above captures all of the key high-level requirements provided by stakeholders. We will now create a series of Business Sub-Epics that will provide more detail and elaborate on the high--level requirements captured in the Business Epic:
The six (6) Business Sub-Epics listed above elaborate, or provide more detailed information on the business requirements that were captured in the parent JIRA Business Epic.
Examining a JIRA Sub-Epic Record
For example, Business Sub-Epic 1.0 "Manage Team Calendar Administration" elaborates on the calendar administration requirements captured in the Business Epic:
Let's have a closer look at Sub-Epic RSD-51 Manage Team Calendar Administration that further elaborates stakeholder requirements in parent Epic RSD-42 Team Calendar Application.
Sub-Epic: Header Section
The top portion of the Header section of Sub-Epic RSD-51 contains self-explanatory information, as shown above in the Summary, Type and Status fields. Other data fields require some explanation.
The Affects Version/s field displays the name of the planned release where all of some of the User capabilities, features and functions described by Business User Stories associated with the Sub-Epic, will be available.
The Component/s Field displays one or more data tags chosen by the members of the Team Calendar configuration team that describes the nature of the Sub-Epic (Team Calendar) and planned Agile Scrum Sprint (Sprint 1) when work associated with the Sub-Epic is targeted. Components in JIRA are useful for segregating information by tags, for the purpose of notification, searching and reporting.
Story Points (14) is a measure of the amount of effort it will take the Team Calendar Configuration team to complete configuration of all Business User Stories associated with the Sub-Epic.
Sub-Epic: Description Field
The Description field is divided into paragraphs that describe the various Administrator capabilities and features that will be needed by the Team Calendar Administrator when the Calendar is in daily use, or Production.
The Goal and objective paragraph captures the overall business requirement that needs to be satisfied one the Team Calendar application has been configured for Administration use. This requirement was extracted from the set of requirements that was used to selected the Team Calendar solution.
The Solution paragraph describes a suggested approach to be used to administer the Team Calendar.
The Benefits paragraph serves as a reminder of the benefits of a centrally administered Team Calendar, in case questions arise among the configuration team or stakeholders regarding the administration approach.
User/Entities & Roles describes the groups of business stakeholders and other users that will interact with the Team Calendar. Listing users, groups of users and entities (automated interfaces and 'Bots) supports the development of Business User Stories.
Functionality and Features describes capabilities that Team Calendar Administrators should have once the Sub-Epic has been satisfied, through the completion of supporting Business User Stories.
Scenarios provide insights into typical use cases that Team Administrators will experience, supporting the development of associated Business User Stories for the Sub-Epic.
Assumptions provide additional information that may assist the configuration team during the configuration or acceptance testing of the Team Calendar application. This paragraph can serve to document responses to business stakeholders about specific Team Calendar Administration practices and processes.
Out-of-Scope can address Team Calendar administration practices, processes and issues that are outside of the focus area of Team Calendar Administration configuration. Information added to this paragraph can be managed in business operational documents for the organization.
The Reference section provides web links to information that is useful to Team Calendar configuration team members, stakeholders and Users. Files may be uploaded to include internal policies, procedures or best practices documentation.
Sub-Epic: Links to Supporting Business User Stories
The Team Calendar Administration management Sub-Epic required five (5) Business User Stories to fulfill the requirements of the Sub-Epic:
Note that the text for each Business User Story (BUS) summary text includes an associated numeric identifier which ties the BUS to a section of the Team Calendar application requirements documentation.
In the next article, we'll explore creating Business User Stories in JIRA to implement Sub-Epic Team Calendar configuration requirements.