Researching KTLO Work In Jira · Atlassian Everything

3d • Jira

Researching KTLO Work In Jira

Hey everyone,

This is a fairly specific piece of research I'm kicking off. As individual product/engineer teams scope out their quarterly planning in Jira, We successfully completed a rollout of a hierarchy structure which connects Initiatives>Epics>Stories etc. This is giving us cross vertical visibility on all work.

One topic that's arisen is how cross vertical teams such as platform, security etc who need to ensure that essential work is done by the individual Product & Tech spaces. This is essentially classed as KTLO work (essential security/maintenance/enhancement) work that falls outside of new feature delivery.

Some suggestions are that the security team would manage their own backlog from a ticket perspective, and clone these work items (epics/tasks/etc) and these would sit within the corresponding project spaces to be picked up and accounted for in sprint planning.

Has anyone had first hand experience of a similar situation and how was it managed, did tickets get cloned like the scenario above (which sounds very over-engineered) or is there a simpler solution? I get the cloning aspect so the Plat/SEC teams can track progress, but would love to hear any other perspectives!

0 comments

Researching KTLO Work In Jira