Scribd
Upload
5 views8 pages

Jira Project Tracking Update:: Epics, Stories, Bugs, and Current Backlogs/To-Dos

The document outlines the project tracking framework in Jira, detailing the structure of Epics, Stories, Bugs, and Sub-Tasks to streamline project management. It emphasizes the importance of estimation and tracking progress through time spent on tasks and maintaining a backlog of current items. Next steps include linking existing backlogs to relevant Epics and conducting daily stand-up meetings to monitor progress and address any blockers.

Uploaded by

manishtalele1410
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views8 pages

Jira Project Tracking Update:: Epics, Stories, Bugs, and Current Backlogs/To-Dos

The document outlines the project tracking framework in Jira, detailing the structure of Epics, Stories, Bugs, and Sub-Tasks to streamline project management. It emphasizes the importance of estimation and tracking progress through time spent on tasks and maintaining a backlog of current items. Next steps include linking existing backlogs to relevant Epics and conducting daily stand-up meetings to monitor progress and address any blockers.

Uploaded by

manishtalele1410
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Jira Project Tracking Update:

Epics, Stories, Bugs, and Current Backlogs/To-Dos


Projects and Work Tracking in Jira

• As part of our efforts to streamline project management, we’ve created several key
projects in Jira, including:

• Development Projects (mPolic, Yatharth, Rakshak etc)

• Production Support Projects (To track bugs, Change Request reported by


Product Support Team)

• Operational Efficiency Projects (Track operational related tasks)


How We Will Track Progress

• Epics: represents a large body of work that can be broken down into smaller
tasks (Stories, Bugs, or Tasks). In our case, we have created modules (Welfare,
Smarty Duty, Service Book etc.) as Epics

• Stories: represents a user story or specific requirement that is typically part


of a larger Epic. In our case Product Feature, Enhancement, Bugs will
represent Story. As team members, you will create and update Stories with
detailed descriptions, acceptance criteria, and any relevant attachments.

• Bugs: are issues that arise when something doesn’t work as expected or
breaks in the system. If you encounter an issue that needs fixing, log it as a
Bug, and it will be tracked separately from Stories. Please make sure to
provide clear steps to reproduce the bug, its impact, and priority.
How We Will Track Progress

• Sub-Tasks: is a smaller, more specific unit of work that is created under a


parent issue (Story, Bug, or Epic). Sub-Tasks allow us to break down complex
tasks into manageable components.

• Examples: Story: "Develop User Authentication"

• Sub-Task 1: Set up database tables for authentication

• Sub-Task 2: Implement backend logic for login functionality

• Sub-Task 3: Write unit tests for authentication module


Estimation and Effort Tracking

• Estimation: All team members will provide time estimates for each Story,
Bug, and Sub-Task they are working on. This helps us plan our workload and
monitor progress. The estimation can be done using Original Estimation.

• Tracking: As work progresses, please make sure to update your issues with
the actual time spent and any adjustments to the original estimates. This will
allow us to keep track of our overall project health and identify any
bottlenecks or issues.
Current Backlogs and To-Dos

• Please list down key items currently in our backlog and the immediate to-
dos that we will be focusing on:

• Backlog for Development Project:

• mPolice (New Feature Development)

• Feature1 - Create user authentication system

• Feature2 – Capture thumb impression

• Bug – Fix authentication failure under specific conditions


Next Steps

• Move all existing backlogs (including New Features, New Enhancements, and
Bugs) which are assigned to you and link them to the relevant Epics.

• The team is expected to break down each Story and Bug into manageable
Sub-Tasks that can be completed within 1 to 2 days (as mentioned in the
previous slide).

• We will hold daily stand-up meetings to discuss the following:

• What was accomplished yesterday?

• What is planned for today?

• Are there any impediments or blockers?


More questions on Jira?

Please reach out to me on +91 9987023723 or through email.

You might also like