alt Hacker NewsI 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.
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.
Sounds… political. You have cross-functional teams interfacing via a tool. It would be reasonable to co-design this interface, so that all user goals are taken into account. When engineering owns the tool, do they approach the configuration of JIRA the same way as they build the product?