5 exercises on reading Jira epics and quarterly roadmaps — understand ticket hierarchy, identify blockers and dependency chains, and evaluate risk when deadlines are at stake.
Roadmap hierarchy at a glance
Quarter — business planning cycle (Q1–Q4); stakeholders read at this level
Epic — groups related stories toward a product goal; spans multiple sprints
Story / Task — individual deliverable; assigned to a developer; completed in 1–3 sprints
Blocker — a ticket that prevents another from progressing; escalate immediately
Dependency chain — Q3 depends on Q2 → Q2 delay cascades to Q3 and Q4
0 / 5 completed
1 / 5
🗺Epic DASH-200 with Roadmap
EPIC: DASH-200 — Analytics Dashboard (Q2 2024)
Owner: Product Manager (alex.reed@example.com)
Goal: Give business analysts a self-service dashboard to monitor KPIs without engineering support
Target Completion: End of Q2 2024 (by 2024-06-30)
Status: In Progress (60% complete)
Child Tickets:
DASH-301 [DONE] Build dashboard data model and API endpoints
DASH-302 [DONE] Create chart rendering components (line, bar, pie)
DASH-303 [DONE] Implement date range filter
DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)
DASH-305 [IN PROGRESS] Build KPI summary cards
DASH-306 [TODO] Implement real-time data refresh (WebSocket)
DASH-307 [TODO] Role-based access control (RBAC) for dashboard views
DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304
DASH-312 [TODO] Export dashboard data to CSV
Quarterly Roadmap Context:
Q1 2024 [DONE] Data pipeline and ETL infrastructure
Q2 2024 [CURRENT] Analytics Dashboard (this epic)
Q3 2024 [PLANNED] Mobile app dashboard (depends on Q2 completion)
Q4 2024 [PLANNED] Predictive analytics module (depends on Q3 data model)
Risks:
- DASH-310 (auth migration) is blocking DASH-304; estimate 3 sprints to complete
- Q3 Mobile dashboard is time-dependent: delays in Q2 will push Q3 start date
Read the epic. Which ticket is currently blocking another ticket from progressing, and what is the blocked ticket?
DASH-310 (auth migration) is the blocker for DASH-304 (saved filter presets).
The epic clearly marks: "DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)" and "DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304"
What a blocker means in Jira/Agile:
A blocked ticket cannot proceed until the blocking ticket is resolved
DASH-304 is "In Progress" but has stalled — work cannot continue until DASH-310 is done
The ticket should have a "blocks/is blocked by" link between DASH-310 and DASH-304
Impact chain: DASH-310 is TODO and estimated to take 3 sprints → DASH-304 cannot finish → potentially affects the epic's Q2 completion target.
What to escalate in planning: DASH-310 should be reprioritised to the top of the backlog. Its completion unblocks DASH-304, which keeps Q2 on track.
EPIC: DASH-200 — Analytics Dashboard (Q2 2024)
Owner: Product Manager (alex.reed@example.com)
Goal: Give business analysts a self-service dashboard to monitor KPIs without engineering support
Target Completion: End of Q2 2024 (by 2024-06-30)
Status: In Progress (60% complete)
Child Tickets:
DASH-301 [DONE] Build dashboard data model and API endpoints
DASH-302 [DONE] Create chart rendering components (line, bar, pie)
DASH-303 [DONE] Implement date range filter
DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)
DASH-305 [IN PROGRESS] Build KPI summary cards
DASH-306 [TODO] Implement real-time data refresh (WebSocket)
DASH-307 [TODO] Role-based access control (RBAC) for dashboard views
DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304
DASH-312 [TODO] Export dashboard data to CSV
Quarterly Roadmap Context:
Q1 2024 [DONE] Data pipeline and ETL infrastructure
Q2 2024 [CURRENT] Analytics Dashboard (this epic)
Q3 2024 [PLANNED] Mobile app dashboard (depends on Q2 completion)
Q4 2024 [PLANNED] Predictive analytics module (depends on Q3 data model)
Risks:
- DASH-310 (auth migration) is blocking DASH-304; estimate 3 sprints to complete
- Q3 Mobile dashboard is time-dependent: delays in Q2 will push Q3 start date
The roadmap states: "Q3 Mobile dashboard depends on Q2 completion." The epic is currently 60% complete with the Q2 deadline of 2024-06-30 approaching. What is the business risk?
A Q2 delay cascades into Q3 and potentially Q4 — this is a dependency chain risk.
Each quarter's work depends on the previous quarter completing. If Q2 misses 30 June:
Q3 mobile dashboard start date shifts right
Q3 completion date shifts right
Q4 predictive analytics (which "depends on Q3 data model") is also delayed
60% complete with blockers is a red flag: Of the 9 child tickets, 3 are DONE (33%). Two are "In Progress" but one (DASH-304) is blocked. Four remain as TODO including DASH-306 (WebSocket — complex), DASH-307 (RBAC — security-critical), and DASH-310 (the blocker itself).
The hardest work (real-time refresh, auth migration, RBAC) is still ahead. 60% by story count does not mean 60% of effort complete.
Key terms: dependency chain, downstream impact, milestone, critical path, story count vs. effort estimate, risk cascade
3 / 5
🗺Epic DASH-200 with Roadmap
EPIC: DASH-200 — Analytics Dashboard (Q2 2024)
Owner: Product Manager (alex.reed@example.com)
Goal: Give business analysts a self-service dashboard to monitor KPIs without engineering support
Target Completion: End of Q2 2024 (by 2024-06-30)
Status: In Progress (60% complete)
Child Tickets:
DASH-301 [DONE] Build dashboard data model and API endpoints
DASH-302 [DONE] Create chart rendering components (line, bar, pie)
DASH-303 [DONE] Implement date range filter
DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)
DASH-305 [IN PROGRESS] Build KPI summary cards
DASH-306 [TODO] Implement real-time data refresh (WebSocket)
DASH-307 [TODO] Role-based access control (RBAC) for dashboard views
DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304
DASH-312 [TODO] Export dashboard data to CSV
Quarterly Roadmap Context:
Q1 2024 [DONE] Data pipeline and ETL infrastructure
Q2 2024 [CURRENT] Analytics Dashboard (this epic)
Q3 2024 [PLANNED] Mobile app dashboard (depends on Q2 completion)
Q4 2024 [PLANNED] Predictive analytics module (depends on Q3 data model)
Risks:
- DASH-310 (auth migration) is blocking DASH-304; estimate 3 sprints to complete
- Q3 Mobile dashboard is time-dependent: delays in Q2 will push Q3 start date
DASH-307 covers Role-based access control (RBAC) for dashboard views. It is currently TODO and has no blockers listed. Why might a tech lead argue this ticket should be prioritised before DASH-306 (real-time refresh)?
Security before features — RBAC should be in place before building data-streaming features that could expose sensitive data.
If DASH-306 (real-time WebSocket refresh) is built and shipped before DASH-307 (RBAC):
The real-time data stream may be accessible to users who should not see certain KPIs
Retrofitting RBAC onto a live WebSocket system is more complex than building it into the WebSocket handler from the start
A security audit or pen test after Q2 might require rework of the WebSocket layer
The principle: security first, then features. Access control should be foundational — built before the features that it controls. This is sometimes called "secure by design" or "security by default."
RBAC in a dashboard context:
Role: Admin, Analyst, Viewer
Admin → sees all KPIs, can edit saved filters
Analyst → sees all KPIs, read-only
Viewer → sees only public/summary KPIs
RBAC vocabulary: role, permission, resource, policy, principle of least privilege, security boundary, access control list (ACL)
4 / 5
🗺Epic DASH-200 with Roadmap
EPIC: DASH-200 — Analytics Dashboard (Q2 2024)
Owner: Product Manager (alex.reed@example.com)
Goal: Give business analysts a self-service dashboard to monitor KPIs without engineering support
Target Completion: End of Q2 2024 (by 2024-06-30)
Status: In Progress (60% complete)
Child Tickets:
DASH-301 [DONE] Build dashboard data model and API endpoints
DASH-302 [DONE] Create chart rendering components (line, bar, pie)
DASH-303 [DONE] Implement date range filter
DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)
DASH-305 [IN PROGRESS] Build KPI summary cards
DASH-306 [TODO] Implement real-time data refresh (WebSocket)
DASH-307 [TODO] Role-based access control (RBAC) for dashboard views
DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304
DASH-312 [TODO] Export dashboard data to CSV
Quarterly Roadmap Context:
Q1 2024 [DONE] Data pipeline and ETL infrastructure
Q2 2024 [CURRENT] Analytics Dashboard (this epic)
Q3 2024 [PLANNED] Mobile app dashboard (depends on Q2 completion)
Q4 2024 [PLANNED] Predictive analytics module (depends on Q3 data model)
Risks:
- DASH-310 (auth migration) is blocking DASH-304; estimate 3 sprints to complete
- Q3 Mobile dashboard is time-dependent: delays in Q2 will push Q3 start date
The epic goal states: "Give business analysts a self-service dashboard to monitor KPIs without engineering support." Which TODO ticket most directly delivers on the "without engineering support" part of the goal?
DASH-304 (saved filter presets) most directly enables self-service — analysts configure their own views.
The goal keyword is "self-service... without engineering support." Let's evaluate each ticket against this:
DASH-306 (real-time refresh) — improves data freshness; still requires engineering to have built it. Doesn't reduce need for engineering involvement in setup.
DASH-307 (RBAC) — access control is managed by engineers/admins. Actually increases the engineering setup required (someone must define roles and assign them).
DASH-304 (saved filter presets) — lets an analyst configure their own dashboard view (e.g., "EMEA sales, last 30 days") and save it for reuse. Without this, analysts ask engineering to set up a dedicated dashboard for each use case. With it, analysts are truly self-served.
DASH-312 (CSV export) — reduces the need to ask the data team for custom reports. Also a strong "self-service" feature, but secondary to DASH-304 for interactive analysis.
Reading epic goals: Good epics have a clear, testable goal. Evaluate each child ticket against the goal to understand why it exists and which tickets are most valuable.
Key terms: self-service, autonomy, persona goal, KPI, filter preset, business analyst
5 / 5
🗺Epic DASH-200 with Roadmap
EPIC: DASH-200 — Analytics Dashboard (Q2 2024)
Owner: Product Manager (alex.reed@example.com)
Goal: Give business analysts a self-service dashboard to monitor KPIs without engineering support
Target Completion: End of Q2 2024 (by 2024-06-30)
Status: In Progress (60% complete)
Child Tickets:
DASH-301 [DONE] Build dashboard data model and API endpoints
DASH-302 [DONE] Create chart rendering components (line, bar, pie)
DASH-303 [DONE] Implement date range filter
DASH-304 [IN PROGRESS] Add saved filter presets (blocked by DASH-310)
DASH-305 [IN PROGRESS] Build KPI summary cards
DASH-306 [TODO] Implement real-time data refresh (WebSocket)
DASH-307 [TODO] Role-based access control (RBAC) for dashboard views
DASH-310 [TODO] Migrate dashboard API to v2 authentication ← BLOCKER for DASH-304
DASH-312 [TODO] Export dashboard data to CSV
Quarterly Roadmap Context:
Q1 2024 [DONE] Data pipeline and ETL infrastructure
Q2 2024 [CURRENT] Analytics Dashboard (this epic)
Q3 2024 [PLANNED] Mobile app dashboard (depends on Q2 completion)
Q4 2024 [PLANNED] Predictive analytics module (depends on Q3 data model)
Risks:
- DASH-310 (auth migration) is blocking DASH-304; estimate 3 sprints to complete
- Q3 Mobile dashboard is time-dependent: delays in Q2 will push Q3 start date
The epic has 9 child tickets in total. Three are DONE, two are IN PROGRESS (one blocked), and four are TODO. Which statement best describes the hierarchy shown in the roadmap?
Quarter → Epic → Child Ticket (Story/Task) — this is the standard Jira planning hierarchy.
The roadmap reveals three levels of planning:
Quarterly Roadmap (top level): Q1, Q2, Q3, Q4 — business planning cycles. Each quarter has one or more Epics. Stakeholders think at this level ("what are we delivering in Q2?").
Epic (middle level): DASH-200 Analytics Dashboard. Groups related stories/tasks that together deliver a product goal. Usually spans multiple sprints. Product managers own epics.
Child Tickets / Stories (bottom level): DASH-301 through DASH-312. Individual deliverables assigned to developers. Completed in 1–3 sprints each. Developers own stories.
Why the hierarchy matters for reading roadmaps:
A delay at the story level (DASH-310) → blocks another story (DASH-304) → may delay the epic (DASH-200) → may shift the quarterly target → may cascade to next quarter (Q3)
Stakeholders read at the epic/quarterly level; developers read at the story level