How PMs work with Jira

How to create a new Implementation Project in Jira

Create Issues in Jira 

A few rules for creating a new issue in Jira: 

1. Minimum requirement: All Jira issues MUST have a Summary, Description, Assignees, and Priority 
2. During weekly stand-ups, deadlines for tasks are assigned or updated 
3. Discussions relating to the issues should happen on Jira and not in Slack

Refer to How to use Jira for Implementation team. 

Issues Hierarchy in Jira

We use 3 types of issues hierarchy:

1. Epic
2. Tasks
3. Sub-tasks

Epic: equivalent to a task group. We use Epics to organise the tasks into logical grouping (For example: A big milestone, a type of key deliverables)

• • Typically, our first-time implementation project steps are grouped into key areas of tasks such as the followings. These would then become the name of the epic:
    • Project Management
    • Data Sources integration 
    • Profile Stitching and Attributes
    • Data Destination integration 
    • Maintenance and Bug Fixes
  • For 2nd year onwards, our projects are typically defined by key deliverables which are scoped and priced with customers individually. Each of these deliverables can be organised into an epic. For examples: 
    • RFM analysis 
    • Add data source ABC
    • Implement lead scoring use case 

Important: Each Epic must be tagged with one of the following Labels: Implementation, Maintenance, PM. This is for the purpose of accounting and reporting. 

Task: a well-defined activity.

Important: All tasks must be associated with an Epic. 

Sub-task: not compulsory. A Task can be broken down into smaller, more measureable sub-tasks

 

Time Reporting in Jira 

We use an add-on in Jira called Appfire Timesheets for reporting of time.