If your small org has less then 4 dev teams and less then 4 devs per team. Just use paper tickets and tape. Jira sucks and is a lame excuse to hire 10 more people to manage it.

  • 3
    May not be Jira. A 1-person in-house built tracker is ok
  • 0
    Good luck measuring performance and identifying points of improvements after each sprint or quarterly or yearly reviews by going over duck taped paper tickets
  • 0
    @bioDan We would get a lot further with that then we would the time wasted in jira. Even trello would suffice. Jiras a heavy, dated mess that you sink time and training into just to make more unmanageable.
    Let me put it this way if you need new employees to manage an app that manages an app that manages an app, it’s time to rethink. Keep in mind I’m talking about small businesses. The same goes for perhaps salesforce. A small organization of 15 people may not need some thing as robust as salesforce costing them 50 K a year along with a salesforce admin at 120 K a year along with sf integration applications totaling 70 K a year. It’s all a very cool way for our managers and scrum Masters to feel like they have purpose but it is the furthest thing from agile imaginable
  • 0
    I believe in getting shit done, not Pittling with 3rd pastry apps
  • 0
    @dUcKtYpEd well, as a CTO, Product Manager, Developer, and co-founder of a 12 people company where 7 of them are devs, i beg to differ.

    Yes there is a learning curve i had to go through to learn JIRA as a manager (after some experience i had using it as a developer in a previous company), but the benefits of using it correctly outweights all other options i checked.

    I manage the JIRA, and i would love to be able to hire a product manager to do that instead of me. Its plenty of work and its somewhat time consuming (especially at the beginning).

    But its integrated with GitHub and Slack, overall works as intended, and I can manage and monitor issues from a very wide macro perspective to a micro perspective with relative ease. I had no complaints so far from the development or QA teams and we use it daily in our standup meetings. Also in sprint plannings, sprint reviews, and quarterly reviews, managing the changelog, versions, and release notes.

    I dont use confluence.
  • 1
    @dUcKtYpEd if tou are a developer and you need to manage the board but are not in a management position - that is clearly wrong. But it would be more of an organization structure and protocol issue rather than the fault of JIRA.

    My devs only need to move tickets from column to column and occasionally add a comment or report an issue (if they wish). But other than that their interaction with JIRA is on a very minimal level and shouldnt be more than abot 20 minutes a day (where 15 of those minutes are in a standup meeting with the rest of the dev team)
  • 1
    The GitLab issue tracker works fine for us. Jira might just be too fat.

    Also it really depens on the people.
    If too much of the non-devs are technophobes, there needs to be someone who updates the tracker on their behalf...
  • 1
    I dunno man, it took me a couple of hours to set up some of the stuff I wanted, but it's been quite helpful so far.
  • 1
    @bioDan im glad to hear it works for you. Thing about jira is it can be done very right or wrong and has alot of complications. There are products that capitalize on the fact that they are smoother, faster and more organized than jira. Look at backlog and clubhouse. For small teams id still prefer and have had the most success with smaller suites like trello where i can pull in just enough lightweight extensions to measure whats needed.

    Does trello provide a manager a complex suite of reports needed to show his boss that hes doing something impactful? Maybe, maybe not to the fullest potential but it puts emphasis on the devs doing and the workplace not being jira centric. My place of employment and two places prior we're jira centric. Both scrambled over jira and getting it how they liked it day in, day out. The devs had to conform to this obsession with the product. Big reason I left both.

    Im a programmer, not a jira flexer. I''ll never pretend to be otherwise
  • 0
    @ars1 first glanse it has whats needed. My complaint is where it goes over time and complexity added. My complaint is the jira centric atmosphere which is a contradiction to agility in our line of work.
Add Comment