Usage of JIRA is not painful

JIRA is an Atlassian tool. JIRA was basically designed to be used as a bug tracking tool. But,

with the advent of plugins built around JIRA tool, JIRA can be used as a Project

Management Tool.

Scrum master online training

I work for an Agile Solutions company called Leanpitch as an Atlassian tools expert. As

part of my consulting work, I have numerous discussions with various teams across

industries. Most of the people that I have met had initially feared of using JIRA. JIRA must

have been introduced by their higher management or process teams for various reasons:

streamlining the team activities, tracking purpose, report purpose, forecasting and so on.

If JIRA is intended to be used for these purpose, then why does the team hate to use it?

The reasons for team hating JIRA is because of the way its configured. JIRA is a highly

flexible and configurable tool. It let’s team to decide what their project has to be and how

their SDLC has to be. It also helps team to decide what each member in the team sees and

works on. It let’s team to configure whole of the project attributes as per their wish.

Thus, JIRA gives the power of configuring it according to the team’s need. But, with the

power comes the responsibility. The people who configure the JIRA has to do it properly.

For eg., when a project is created, the project manager/team lead or whoever is

responsible for the project should know what his/her team needs are. That has to be

communicated to the Admins who will configure it accordingly and the same thing is to be

known by whole project team.


I have heard developers say usage of JIRA reduces their productivity. It’s true that it does

take some time of developers as each developer has to update the JIRA issues. This will be

the case if JIRA is not integrated with tools that team is using for delivery cycle. For eg., if

a developer has to update the JIRA issue status once the code is checked-into the version

control, he has to log into JIRA and update the respective JIRA Issue. The developers I

have interacted with say that this is the most painful and unproductive thing that they

need to do. I completely agree with them. But, what people should also know is that JIRA

can be integrated with the Version control, Build tools, review tools and etc. Once the

tools are integrated with JIRA, developers needn’t log into JIRA for Issue updation. From

the Version control, we can make use of web hooks and push the commit message and its

related information to JIRA issue automatically. Similarly, we can push the Build results to

JIRA issues automatically. With this all that developers need to do is what they are happy

to do: just code and push the code to the version control and JIRA Issue will be updated

automatically.


Leanpitch Technologies PVT LTD
309- 4th B Cross Rd, HRBR Layout 3rd Block, Kammanahalli, Bengaluru, Karnataka 560043.

Comments

Post a Comment

Popular posts from this blog

Scrum Master interview questions

Scrum Master interview questions Before going through the interview questions below, ask yourself how good you know about  Scrum  and the role of a  Scrum Master . Go through some of the Leanpitch  resources  like  videos ,  blogs , and podcasts/webcasts to get more knowledge on the roles and responsibilities of the Scrum Master. The podcasts and webcasts are available on the Leanpitch mobile app for viewing.  Scrum Master interview questions : Of all the Scrum ceremonies, which one you can never skip and why? Which is the most useful ceremony in Scrum which you would like to tell and why? If one of the team members does not want to participate in the Scrum ceremonies, then how do you handle such situations? You have identified one good process for the team, which you think is good for the team, but then the team does not want to follow - what will you do as an SM here? If one of the team members is unable to complete his user stories, Consistentl...
Read more

The role of Tester in Scrum Team

The role of Tester in Scrum Team The role of a tester in the Scrum Team is elementary and straightforward but often misjudged. There are only three roles in Scrum, and they hold different responsibilities. The tester is part of the cross-functional  development team . The role of a tester is to contribute to the product quality just like any other development team member.  Advanced Certified Scrum Master  Who is a Tester? A tester is a person who is responsible for identifying the process to test the product and ensures that the product meets its specifications or requirements. Testers are " Customer Advocates " because they use and test the products from the customer perspective. They are responsible for finding out defects or bugs in the product, which is under test and thereby helping to improve the product quality. They are User proxies who are responsible for ensuring the product under development solves the problem of the users in the context they use.  Wrong A...
Read more

Crafting a Sprint goal

 Crafting a Sprint goal   The Sprint Goal provides a base for the team to negotiate the scope change that may arise during the Sprint. No changes would be made or accepted that would endanger the Sprint goal. The Sprint goal guides the development team on why they are building the Product Increment.  Advanced Certified Scrum Master    The goal conveys the purpose of the Sprint, which could be, What is the value that customers are getting out of this Sprint?  What are we going to validate in this Sprint?  What are we going to build in this Sprint?   The Scrum Team works together in crafting the Sprint goal during Spring Planning.    They discuss and understand the purpose of the Sprint. One of the outcomes of Sprint Planning is the Sprint goal. If the team does not have a clear understanding of the goal, then it is not possible to get their buy-in. If the goal is raw, it needs to be refined to come to a clear understanding.    T...
Read more