Best way to use Jira For Software developing Company

Question

I am using Jira to manage the projects in a software developing company. I am pretty sure that Jira is as robust as other Project Management software in terms of managing the project. I want to know what is the best practice to use Jira in managing projects for a software developing company. If there is any video tutorial or something that would be more helpful.

Biswash Lamsal · Answer

Thank You so much for the feedback. That is really helpful.

Nikola Perisic_rh4g7m · Answer

Hello @Biswash Lamsal

To manage the Jira for software development teams, I would say to do this:

* I assume that developers will be working in Scrum, so use a Scrum template
* Make the navigation bar for the developers in the project to make sense by adding developer related options such as Development, Code, Deployment, Releases. Development section allows you to connect your Jira with either GitHub or Bitbucket. This will help developers to see their commits, branches and pull requests. Of course with that you would have to either user Bitbucket or GitHub as extra products
* Customize the board swim lanes (using company-managed project) where you will define the Assignee as the measure where each developer will have their own section that they can focus on.
* Create quick filters that are related to developers - issues that are soon in due, critical issues, issues that are unassigned, since in Agile methodology, developers should be self organized and assign the issues among them selves.
* Create easy to understand workflow, don't add too much statuses, keep it simple
* Create unique dashboards that stakeholders can use to see the progress of the developers (optional), you can utilize the total issues completed by each assignee, resolved vs created chart - this is only an option if the managers need to focus on the results driven data
* Remove necessary options in navigation bar (Forms, Shortcuts, etc.)
* Limit the permissions on who can do what: who can delete issues, who can edit all of the issues and more important big impact permissions, these shouldn't be handed for anyone