Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

5 pitfalls when using Atlassian Jira

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Jira Atlassian is a great ALM tool for managing your Agile environment. It provides a friendly workspace for Agile teams and has some informative out-of-the-box reports that allow teams to easily apply root cause analysis.

At the program level, there are several easy ways to achieve aggregated data reports and epic progress boards. The relatively new Jira portfolio also has some interesting features that enable larger organizations to manage their program, including shared planning, shared releases, progress, and mitigation plans.

Visiting many organizations that use Jira as their main tool for their Agile environment, I decided to summarize 5 common pitfalls it is best to avoid.

  1. Less is more, avoid heavy configuration
    Agile is about teams that work together with trust and a common mission. Therefore the workflow configured should be as simple and as short as possible to reflect lean value stream rather than handoffs.
  2. Don’t work for Jira, let it work for you
    Avoid complex issue cards that are full of information. Always ask why you need this data and retrospect its benefit over time. Otherwise, it’s just another field the team needs to add and the daily overhead is bigger than the value.
  3. Work in a trusting environment, don’t limit the work to a specific role
    Some organizations set restrictions in the workflow for specific roles. For example – only QA/PO can move a story to do. Such configuration usually is a manifestation of mistrust from management and annoys the team on a daily basis when trying to keep Jira up to date.
  4. Focus on team deliveries, not on personal tasks
    Sub-tasks should help the team align about the work to be done towards the delivery of an end-to-end story. It is not meant for leaders to micromanage individual utilization. Teams should avoid estimating sub-tasks and log work on task progress. The burndown chart that leans on “log work” is misleading and shifts the team’s focus from the actual deliveries.
  5. Use the tool wisely to gain its benefits
    Jira has some great out-of-the-box reports that are based on data the team should update. It would be a shame not to use them due to inattentiveness.
    For example:
    – Estimate all stories and drag them into the sprint container before starting the sprint to create a reliable velocity and sprint report
    – Update the story status in addition to the sub-tasks to gain real visibility on WIP and progress

So use Jira wisely and keep it simple to serve your organizational needs without over-configuration and with keeping personal interaction as first priority.
Work iteratively, start with a simple configuration, let your teams see the value, and improve with time.

Subscribe for Email Updates:

Categories:

Tags:

Risk Management on Agile Projects
Achieve Business Agility
System Archetypes
Agile India
Agile
Software Development
Jira Cloud
ROI
Scrum Primer
Kanban 101
Software Development Estimation
Pomodoro Technique
Agile Assembly Architecture
Jira Plans
Slides
SAFe Release Planning
WIP
Reading List
Scrum Master
Product Management
The Agile Coach
Scrum and XP
LAB
Story Slicing
Games and Exercises
GanttBan
Agile Program
chatgpt
TDD
ART Success
Planning
Continuous Planning
Scrum.org
IT Operations
Agile Release Planning
Agile Release Management
Nexus Integration Team
Legacy Enterprise
Agile Project
speed @ scale
User stories
Portfolio for Jira
speed at scale
PI Objectives
Lean Agile Leadership
Kanban Game
Agile Product Ownership
Agile Community
Covid19
Scaled Agile Framework
Lean Agile Organization
Professional Scrum Master
Scrum Master Role
Agile Development
Scrum Values
Large Scale Scrum
SPC
Effective Agile Retrospectives
What Is Kanban
Accelerate Value Delivery At Scale
Agile Marketing
Agile Exercises
Lean Software Development
POPM
AI
agileisrael
Program Increment
Nexus vs SAFe
Agile Outsourcing
Systems Thinking
Lean Agile Management
Continuous Integration
Agile Techniques
Legacy Code
System Integration Environments
Kanban Basics
NIT
Limiting Work in Progress
Presentation
ATDD vs. BDD
Lean-Agile Budgeting
AgileSparks
Product Ownership
Agile Contracts Best Practices
Development Value Streams
ScrumMaster Tales
Continuous Improvement
Hybrid Work
System Team
Kanban Kickstart Example
Implementing SAFe
Professional Scrum with Kanban
Frameworks
Self-organization
lean agile change management
SAFe DevOps
EOS®
Agile Basics
SA
Agility
Scrum With Kanban
Agile Israel
AI Artificial Intelligence
Value Streams
Engineering Practices
ATDD
Enterprise DevOps
Lean Risk Management
Lean and Agile Principles and Practices
Scrum
Amdocs
Agile and DevOps Journey
Process Improvement
Managing Projects
Kanban
Business Agility
RTE
PI Planning
Managing Risk on Agile Projects
Sprint Iteration
Perfection Game
LPM
Tools
Applying Agile Methodology
A Kanban System for Software Engineering
Lean Budgeting
Risk-aware Product Development
ARTs
Lean and Agile Techniques
Agile in the Enterprise
Acceptance Test-Driven Development
Quality Assurance
Tips
Iterative Incremental Development
QA
An Appreciative Retrospective
Atlassian
Manage Budget Creation
Kaizen
Releases Using Lean
The Kanban Method
Coaching Agile Teams
Agile Delivery
Risk Management in Kanban
Agile Testing Practices
Principles of Lean-Agile Leadership
Test Driven Development
Lean-Agile Software Development
Agile Israel Events
Agile Product Development
Change Management
ALM Tools
Jira admin
Certification
Atlaassian
SAFe
Spotify
Built-In Quality
Video
Operational Value Stream
Scrum Guide
Elastic Leadership
Code
Sprint Retrospectives
Implementation of Lean and Agile
Lean Agile
Continuous Delivery
Nexus and Kanban
Lean Startup
Certified SAFe
Continuous Deployment
Nexus
Jira
LeSS
BDD
predictability
Kaizen Workshop
Introduction to ATDD
Nexus and SAFe
Webinar
Lean Agile Basics
Agile Risk Management
Agile for Embedded Systems
RSA
Entrepreneurial Operating System®
Artificial Intelligence
Agile Games and Exercises
Agile Mindset
DevOps
Agile Games
Daily Scrum
Introduction to Test Driven Development
Agile Project Management
Rapid RTC
Advanced Roadmaps
RTE Role
Sprint Planning
Professional Scrum Product Owner
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart