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:

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