Query related to best practices to use JIRA project

Question

I want to understand what the best practices recommended by Atlassian for below scenario's

Problem - one-jira-per-customer) approach or its better to have Segments specific ( example we have search or r&P and SQ various segments) JIRA projects its very confusing which is the best and the most efficient way to handle these.Are there better ways in JIRA to use lable or something else where we can have better way of managing these Please share more insights .

Current way - we use (one-jira-per-customer) approach and have separate projects per customer

Solution - Required from Atlassian ( with best practices relevant in industry)

Brant Schroeder · Answer

@rishi.dutta Based on what you shared this is how I would set it up based on some assumptions.  Let me know if you have any questions.

I would construct processes to meet specific needs of your three teams.

* Team One - Support (Assumption - First line of defense that handles issues, bugs, etc.) 
* Team Two - Professional Services (Assumption - Handle projects, product enhancements, operational work, etc.) 
* Team Three - Customer Channel Managers (Assumption - Need to know what is happening, communicate with the customers, help provide insights on competing priorities from the customers, need insights into everything, etc..)

Base in the teams and the assumptions.  I would do the following.

Jira Service Management - Support would primarily work here.
I would setup a Jira service desk so that I can have an intake process for all requests. (Bug Feature Request, etc.)  You could also use it to raise requests about work you are doing operationally to keep customers informed.

I would build out solid processes on how each request type needs to be handled, SLAs, and what teams are involved.

I would develop a change management process on how to handle new requests.  Once this is in place you can test it out internally and then use it to establish standards with the customers.

All of these processes can be built out in Jira Service Management Workflows to help ensure that they are followed.  Remember to keep them as simple as possible.

Jira Software - Professional Services would primarily work here.
After requests have gone through the change control process and are approved to move forward you can create a linked Epic or Story in Jira that can then be used to track the work.  For larger projects you can create a project to track all the work and link it back to the service management issue through an issue in the project.  You might also have a project for all the operational work to help quickly report on it.

Then the professional services team can work on the product enhancements, major fixes, projects in this space and keep the support team and customers updated on the work through the Jira Service issue.

When issues comer in from the service desk they would need components placed on them to identify the company the work is for, I would suggest creating other components for things that are important to track and having issue types for things like break fixes, maintenance, enhancement requests, etc.  You should also have workflows that help ensure high quality work that follows internal processes.

You can use boards and / or sprints to help organize work and track it's progress.  This can help keep your team members focused on the work that needs to get done and ensure it is moving forward in a timely manner.

Boards, Sprints, Dashboards - Customer Channel Managers
My customer channel managers would be informed about everything that is happening through the boards and / or sprints.  I would also create custom dashboards were they can see issues in the service desk and the Jira projects for specific customers.  This will allow them to communicate with the customer, ensure proper priorities are in place and your teams are working the proper work and help them see the bigger picture.

rishi.dutta · Answer

Hi Brant

Sharing my response for your questions

Q Are all the customers having the same type of work done?

No not necessarily

Q What type of work are you doing for your customers?  Is this work one-time, ongoing or just a project?

Its a combination of one time work and some reoccuring work plus Bugs and Feature enhancements

Q How many teams do you have that work with the customers?
I would say 3 teams ( support , professional services and Customer channel mgrs)

How do you like to organize your teams work?
To be honest that is where we are struggling how to organise any best practices or based on your observations would be appreciated

Brant Schroeder · Answer

@rishi.dutta Welcome to the Atlassian community

Can you provide a little more information about the following:

* Are all the customers having the same type of work done? 
* What type of work are you doing for your customers?  Is this work one-time, ongoing or just a project?
* How many teams do you have that work with the customers?  
* How do you like to organize your teams work?