Showing 39 Result(s)

Create Custom Issue Type – Jira Tutorial [2019]

 

Follow the steps below  to Create Custom Issue type in Jira

Go to Projects > Open a Project >Go to Project Settings > Go to Issues Type > Click on Actions (Top-Right side) > Select Edit Issues Type (From Dropdown menu) > Click on Add Issues Type (Top-Right side) > Add Name, Description, and select a Type (i.e. Standard and Subtask) Click on ‘Add’ button > Click on ‘Save’ button.

Bulk Change Issues – Jira Basics [2019]

 

Follow the steps below to Bulk Change Issues in Jira

Go to Projects > Open a Project > Click on Backlog > Select Issues (Shift key + first and last Issue if they are in sequence OR Control/Command key + left mouse click on Issues)

Once you have selected the issues, Right-click on mouse> Click on Bulk Change > Select an Action/Option from the list > Click on ‘Next’ button > Choose a/an Option(s) from the List > Click on ‘Next’ button > Click on ‘Confirm’ button > Click on ‘Acknowledge’ button.

How to mention Jia Issues in a Comment ? – Jira Tutorial 2019

 

Follow The Step Below To Mention Jira Issues in a Comment

Go to Backlog > Select a Story/Task > Open it in New Tab > Copy the link from new Tab > Paste it as a comment.
OR

Go to Backlog > Select a Story/Task > Go to the Right Sidebar> Left mouse click on the name (at the top of sidebar) > Select Copy > Paste it as a comment.

To Add a Comment

Go to Backlog> Select a Story/Task >Go to the bottom of the Right Sidebar > Write your comment in Comment Section (at the bottom of Right sidebar)
OR
Go to Backlog> Open a Story/Task >Go to Comment Section of the story (in the bottom)> Write your comment in the Comment Box.

How to Display Due Date on Jira Board ? – Jira Tutorial 2019

 

Follow The Step Below to Display Due Date On Jira Board

Click on Issue/ Story in Jira Board (In Which Story You Want To Display Due Date) > Click on Show More > Find Due Date Option And Set Your Due Date

 

If  you do not see Due Date Option,  follows the step below:

Click On ‘+’ Sign (Left side) > Click on Configure Field (Top-Right side in Popup) > Click On Where Is My Field > Write Due Date in Search Bar > Click on Due Date option (if appears) > Go to bottom of the popup > Click on the link Kanban Default Screen Configuration > search Due Date in the search field (in the bottom) > Click on Due Date>Now you can Add Due Date by going into the issue.

 

If Due Date does not appear on the Story/Issue, follow the steps below:

Click on Three Dots (Top-Right side) > Go to Board Settings > Click On Card Layout >  Select the Field you want to add (i.e. Due Date field) > Click on Add’ button.

How to do Scrum with Jira – Jira Tutorial [2019]

Scrum has a Backlog and an Active sprint. Active sprint is what the team is working on and in the backlog, you can create tickets and sprints. You can create stories, tasks, bugs, etc. and move them to sprint through drag and drop.

To create a project, click on Create Project>Classic Project>(Choose) Scrum.

To start a sprint, click on the ‘Start Sprint’ button. A pop up will appear where you will enter sprint duration, start and end date, and Sprint goal and click on the ‘Start’ button.

To see reports, click on the ‘Reports’ side tab and select any of the reporting methods from the options.

enterprise

Common Pitfalls When Implementing Scrum for Enterprise

Hey guys, Anatoly from Define Agile here. We have a pretty serious topic today.  Brad asked me this question on Quora. Thank you. That is an amazing question.

“What are the common pitfalls when implementing Scrum at an Enterprise?”

Yes, of course, nothing is really easy. I’ve been able to implement Scrum multiple times in Fortune 500 Enterprises. However, there are definitely some issues. What are the most common ones?

change

I’ll start with the biggest one right away  – stakeholders. In a Waterfall organization stakeholders often are very reluctant to accept the change. So whenever one department says they want to do Scrum, stakeholders  usually say, “We don’t want anything to change in our process. So, how we communicate with you should stay the same”.

How to solve this ? What I find very useful is to get a “round table” with them, explain the new process, explain the benefits, make sure they understand Agile  well – that helps a lot.

Second issue – people in a team who used to work in certain way for years. This might be challenging. To solve this you need to establish trust, and really explain the value of Agile.

The third challenging thing is  that even though teams have direction to move to Agile, many people don’t understand what Agile actually is.

In order for you to move teams through the Agile transformation, all people in a team need to understand what Agile is and some people need to evangelize Agile, otherwise, it just does not work. We are not talking only about developers here – your manager, his manager need to understand it as well.

meet

This third point is exactly why companies like Define Agile exist. Our main goal when transforming any team is to teach Agile to everyone, so that if you are doing Scrum, any team member can be a Scrum Masters, and others can pass the Agile knowledge forward.

So If you are planning to go through an Agile transformation , I would highly recommend you to hire a partner to do this. It is a very important step, and if done wrong, can demotivate everyone.

 

Hope that helps,

 

Anatoly