Jira - A Necessary Evil?

Jira - A Necessary Evil?

Because there's no easy way in telling you this, I'll just share it straight away... Next week I'll be setting up a Jira environment for the product teams I'm coaching...

Yes... Jira! The issue & project tracking system for software teams created by Atlassian. It's pretty easy to find negative quotes or memes about Jira. Below is the result of a few minutes searching the internet...

  • "Jira, where user stories die..."
  • "Jira isn't just an information refrigerator, it's an information crisper: cold, out of sight, and only noticed when turned rotten."
  • "Jira, the word that strikes fear into the soul of a developer."

Only a couple of months ago I proudly tweeted about a team I coached. They suggested to stop using Jira because they preferred their physical Scrum board and backlog over a digital tool. It was a joyful moment and I considered myself an awesome coach.

However, next week, for a different program I will be setting up Jira again... But why??? Isn't the first value of the Agile Manifesto "Individuals & Interactions over Processes & Tools"? So why am I - an Agile Coach who takes his profession seriously - support using a tool such as Jira? (or any other tool that tracks things no one looks at).

Well... the honest answer is... I don't have any alternatives...

Life Was Great!

My previous team that stopped using Jira was located on the same location. We've had our own team space. The Product Backlog and roadmap were visualized on a wall where everyone could see it. A physical whiteboard was used to track our Scrum Sprints. Every morning we huddled together for our Daily Scrum. During the day the tasks - written down on post-it's - would flow across the Scrum board. Transparency was all over the place, it was one big "inspect & adapt party". Life was great!

A Common Misunderstanding

So why use Jira? Well... the program I'm currently coaching consists of multiple teams working across different locations (in different countries)...A physical Product Backlog therefore isn't a viable alternative. The Product Backlog needs to be shared in a location that everyone can continuously access. That location will be Jira...

Let's go back to the Agile Manifesto. Yes, the first value is "Individuals & Interactions over Processes & Tools". A common misunderstanding is the manifesto states that processes and tooling are evil. They are not. Processes and tooling are fine, but they should enable teamwork, collaboration and offer transparency. Processes and tools should encourage interaction between individuals.

A physical Scrum board is a great tool that supports these elements. It visualizes the product- and sprint backlog, offers transparency about the progress and invites everyone to share possible impediments, improvements and success!

Pitfalls of Using Jira

Some pitfalls of using a digital Scrum board with the Product- and Sprint Backlog are:

  • The Product Backlog becomes way too large to manage;
  • Communication is done via the tool instead of face2face;
  • The Jira workflow dictates the teams way of working;
  • The Sprint Backlog is updated in such a way nobody notices any progress;
  • Energy drops, the euphoric moment of a "done" item isn't celebrated anymore.

Overall, transparency decreases and the inspection and adaptation that ignites improvement becomes more difficult. Transparency, inspection and adaptation form the core of Scrum. You don't want a process or tool that blocks the heart of Scrum. It's asking for problems!

A Necessary Evil?

But, as mentioned before, sometimes a digital tool might be necessary when working with distributed teams. Therefore I am going to support the configuration of Jira next week. To end this blog post a bit positive: at least I'm aware of the pitfalls... And I do have some ideas on how to make the best out of this situation. For example, using a large touch screen to visualize the backlog. Whenever the status of an item changes, encourage the team to update the status via the touch screen. It's almost like using a physical Scrum board. Let's just find a way of working that copes with the mentioned pitfalls in the best possible manner.

Closing

Do you recognize my struggle? Ideas on how to deal with them are more than welcome! Just sharing your experiences is also highly appreciated!


Jira is just a tool. It will become what the team and agile coach made if it. Our primary is physical board and our secondary is Jira. For distributed teams we use realtimeboard to simulate a physical board.

Attila Alko?

DevRel & Agile Coach & Agile Software Development Advocate

8 å¹´

During CSM Training in 2009, our Great Scrum Trainer James Coplien said something similar "Jira is no 1 tool for information hiding and developed with waterfall mindset". Almost 7 years passed, many new versions of jira released, even in 2016, I second this thought.

Rein Hummel

Sr Digital Product Owner TripPlanner @Air France KLM , certified Scrum Master, Product Owner, SAFe Agilist

8 å¹´

Great article!

赞
回复
Maurice Pasman

????????????????????????.?????? | entrepreneur in cybersecurity

8 å¹´

"Individuals & Interactions over Processes & Tools" does not mean there shouldn't be any processes or tools. Just that they should not be more important than individuals and interactions. And from an information security perspective, a I consider a physical scrum board a nightmare. There is no way to see who added which story and when it was moved to what state. To prove this point, I like to randomly add tasks to scrum boards I find hanging in various places :-).

要查看或添加评论,请登录

Barry Overeem的更多文章

  • The Making Of The Brand-New Professional Scrum Master II class

    The Making Of The Brand-New Professional Scrum Master II class

    Finally! With the “embargo” lifted by Scrum.org, we can now share with you the incredible journey that Christiaan…

    13 条评论
  • About the Professional Scrum Master II Class

    About the Professional Scrum Master II Class

    This week Scrum.org launched the brand new Professional Scrum Master II class! For the past eight months, together with…

    14 条评论
  • Myth 14: Refinement is a required meeting for the entire Scrum Team

    Myth 14: Refinement is a required meeting for the entire Scrum Team

    Scrum is intended as a simple, yet sufficient framework for complex product delivery. Scrum is not a one-size-fits-all…

    19 条评论
  • Unleash local know-how with a User Experience Fishbowl

    Unleash local know-how with a User Experience Fishbowl

    Unleash local know-how with a User Experience Fishbowl rather than relying on external “experts” Organizations often…

  • An Essential Practice for Entrepreneurs

    An Essential Practice for Entrepreneurs

    Last week Bauke, Max, Jelrik, Christiaan and I got together for our monthly meetup as part of “The Liberators Friends”.…

    4 条评论
  • Peer coaching with Liberating Structures

    Peer coaching with Liberating Structures

    Liberating Structures are 33 easy-to-use structures for interaction in groups of any size. They enhance relational…

    7 条评论
  • Myth 13: The Scrum Master can’t remove people from the Scrum Team

    Myth 13: The Scrum Master can’t remove people from the Scrum Team

    Scrum is intended as a simple, yet sufficient framework for complex product delivery. Scrum is not a one-size-fits-all…

    99 条评论
  • My Hope for the Future of Scrum

    My Hope for the Future of Scrum

    This week I got interviewed by Marcos Lopez at Agile-Lean Ireland in Dublin. Marcos offered me some interesting…

    6 条评论
  • The Liberators: Unleashing Organisational Superpowers

    The Liberators: Unleashing Organisational Superpowers

    Today marks the official founding of The Liberators. We, Barry Overeem and Christiaan Verwijs, wanted to start a…

    24 条评论
  • Your Scrum Master Journey @KPN iTV

    Your Scrum Master Journey @KPN iTV

    This week Christiaan Verwijs and I facilitated a workshop at KPN iTV in which Scrum Masters could provide a pitch for…

社区洞察

其他会员也浏览了