You’re using JIRA and Confluence…On Purpose??? (Find A Bird: Part 2)
I’m not sure how most people organize thoughts about a new application idea, but I decided to use JIRA. The product we all love to hate. Its overly complex, administering it can be a nightmare and sometimes their product decisions seem downright illogical. With all that, I still chose it. Why? Mainly because I’ve been using it almost daily for the last 4 years to manage user story tickets, bugs, sprints and releases and its comfortable. Its also just better for software projects. When I produced a podcast and Youtube channel, Asana was a far superior tool for that task, but for software, JIRA just makes sense.
What I like:
Github Integration: The ability to link tickets directly to my repository streamlines organization significantly.
Customizable workflow: The first thing I did was tailor the board to my solo workflow. I switched from sprints to a Kanban board, intending to release as soon as issues are resolved. I also added a 'testing' column – a feature I believe JIRA should include by default.
Backlog: As a product manager, I've spent considerable time in the JIRA backlog. It's an excellent tool for keeping track of upcoming tasks.
Confluence: It took me a while to appreciate Confluence. Initially, it seemed like an overly complex version of Google Docs. However, while managing a massive feature from ideation to release, I realized its value. Confluence was indispensable in keeping everything organized, far beyond what individual tickets or a single document could manage. (Refer to the Confluence screenshot below for an example).
Finding old issues: Having previous experience with JIRA, I know how valuable JQL (JIRA Query Language) is for locating old tickets. This feature is crucial for understanding past decisions. If this project continues, future team members might wonder, "Why did Matt make this decision?" Proper documentation in JIRA will provide them with answers.
Works great for teams: Although I’m working solo on this project, I anticipate collaboration from more experienced developers who share a passion for birding. Setting up everything according to best practices from the start is crucial.
Its FREE: JIRA's Free plan offers a comprehensive set of features with few restrictions. However, there are some drawbacks to this plan, which I discuss in the 'What I Don’t Like' section below."
What I don’t like:
Limitations of the Free Plan in Sharing: One significant limitation I discovered after nearly completing the project setup is the inability to share tickets with non-members on the free plan. In contrast to the paid plans, where sharing tickets with stakeholders is straightforward, the free plan restricts public link sharing. This has been the most frustrating aspect for me.
Cost Escalation with Team Expansion: JIRA remains free for up to 10 users, but the costs escalate quickly beyond that. If this project grows and remains open-source, transitioning to GitHub for issue tracking might be more financially feasible.
Overly Complex System: JIRA's high level of customization is a double-edged sword. While it allows for great flexibility, setting up workflows and configurations is complex and time-consuming. It typically requires a dedicated administrator or a user with significant experience to manage and maintain the system effectively (not it!…)
Steep Learning Curve: Introducing JIRA to non-software engineering teams has been challenging, with a 0% success rate in my attempts. Its steep learning curve offers little benefit for non-software projects. In contrast, tools like Asana, Monday, and Clickup have proven more user-friendly and effective for general productivity and project management.
Barriers for Non-Technical Team Members: JIRA's software-centric design poses significant challenges for non-technical team members. It is primarily suited for technical teams accustomed to similar tools, which can impede cross-functional collaboration in a diverse team environment."
Despite its acknowledged shortcomings, I chose JIRA as the project management tool for my 'Find A Bird' project primarily due to my extensive experience and comfort with the product. Over the last four years, my daily professional activities have revolved around JIRA, deeply ingraining its functionalities and nuances in my workflow. This familiarity outweighs the challenges posed by JIRA's complexity and learning curve, especially given its strong suit in software project management. While the constraints of the free plan and the potential barriers it creates for non-technical team members are notable, the platform's robustness in issue tracking, customizable workflows, and integration capabilities align seamlessly with my project's needs. In essence, the decision to utilize JIRA is grounded in leveraging a tool that I know inside out, ensuring that project management for 'Find A Bird' is both efficient and effective, even in the face of JIRA's acknowledged limitations.
