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:

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