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:

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