Rob's Thoughts
LinkedIn
  • roblkdeboer.com
  • Engineering Management
    • Introduction
    • Developer Productivity/Experience
    • OKRs
    • People Management
      • 1:1s
      • Work Logging
      • Onboarding
        • 30-60-90 Day Plan
        • Onboarding Documentation
    • RFCs/Design Docs
    • The -ilities
  • Product Management
    • Introduction
    • Running an Agile Team
    • Prioritisation Framework
    • Backlog Grooming
    • Product Requirement Documents
    • Ticket Templates
      • User Stories
      • Tasks
      • Bugs
      • Example Backlog
  • Resources
  • Personal Projects/POCs
    • WhatsApp Anyone
Powered by GitBook
On this page
  1. Product Management

Ticket Templates

How I bridge the gap between product and engineering

PreviousProduct Requirement DocumentsNextUser Stories

Last updated 1 year ago

There is often a miscommunication or misunderstanding between product and engineering. Product managers may struggle to explain exactly what it is they want or they may not include all the edge cases for their feature. On the other side of that, engineers might not be able to fully explain details that they require or they don't have enough business context for their task.

This can be resolved by having clear tickets or chunks of work that the engineer can execute. This requires both product and engineering to be in sync and to have a common standard of documentation.

I will be explaining my templates in the context of Jira as it is the only project management software I have used. However, these templates and principles though be extendable to any form of task tracking software.

Refer to for more details on Jira issues

here