Significant back and forth between developers and designers just to get clarity about a feature.Problems that should be caught in QA slip through to staging or production.Tickets have to be significantly rewritten during grooming sessions.The first step is admitting there’s a problem. Overloaded teams, corporate inertia or process entropy can result in the system breaking down. In these cases, Jira quickly goes from help to hindrance. Most commonly, tickets are badly written, incomplete or, worst case, shouldn’t even be tickets. Jira is often misused and poorly managed. The hardware or the software is rarely the problem. No one is going to get the #jiraandchill hashtag trending on Instagram. It’s enterprise productivity software, and we tend to hate on the tools we’re assigned. This is a bit unfair to a product that sets the standard for productivity across multiple industries. The word “Jira” is likely to elicit a groan from designers or developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |