5 ms·
For me this is a huge benefit: the engineering team, product management team, qa team, ux team, etc. can each see the things that are relevant to them in the wa
by chacham15 8y ago
For me this is a huge benefit: the engineering team, product management team, qa team, ux team, etc. can each see the things that are relevant to them in the way that they like while still being able to pass the tasks off to the other teams / track them if they would like. You have to put in work to make each flow work for each customer & make sure that the tags are standardized, but once thats in place its super easy (at least for my team)
- Aeolun 8y agoMy experience is that they can sort of see, the things that are sort of relevant to them. Jira is the definition of a jack of all trades, but master of none.
- ken 8y agoMy reading of this is: software development is still such a disorganized activity that the industry considers it acceptable for each organization to simply make up their own system. Jira is built to work for any such system, no matter how crazy, and your particular instance can change completely at any time (like if your manager reads the wrong blog post over lunch). This does not make me feel any better about Jira. It's like those videos of early attempts at flight, and Jira is bragging that they make flapping wings and spinning wings and triplane wings and bird-shaped wings -- whatever you want! Great for their company, not so great for me.