I find the problem is that engineering wants one work flow, product wants another, another department wants theirs, and so on.
As a CTO I have declared that Jira is owned by engineering and it is our developers’ process.
As a CTO I have declared that Jira is owned by engineering and it is our developers’ process.
I know everything that is in our main branch by looking at jira.
Product mangers and executives often want a very different view or workflow and it is hard to bend jira to work for everyone. Jira would need to have things like parallel workflows on a ticket and that would just get confusing and complicated.
it is not, as long as focus is on goals rather than on solutions (applies to everything). Nobody needs a view or a workflow. Everybody has jobs to be done. That is the starting point in process design.