From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Planning your implementation - Jira Tutorial

From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Start my 1-month free trial Buy for my team

Planning your implementation

“

- Before we set up Jira and talk about specific settings, I wanted to give you a list of specific strategic items to think about. In this chapter, we'll discuss 35 decisions to make and actions to consider to ensure a successful application implementation. Now, some of these are things to consider at the time of initial setup, but if you're already using Jira, that's okay. Better late than never. Other items are intended to address long-term and ongoing challenges. Let's make this into a little game. Give yourself one point for each decision you've already considered or implemented. Your goal is to get all 35 points. We'll start with three important, but easy decisions to consider. Decision one, whether you've just started with Jira, or you've been using it for years, such a powerful and useful application should not be directed by a single person. You'll want a governance or steering committee who can establish standards and support both the application and its users. Do you have an advisory board? If not, now's a great time to create one. And here's a tip. Users who set the application strategy may be different from those who perform maintenance and administrative functions. I suggest delegating these duties to users who understand Jira and care about its health, not just to fellow application admins. Decision two, decide how Jira will mainly be used. Will it be for software development, tracking business tasks, or team to do items, support and service, planning and implementing strategic company priorities, or all of the above? And remember, JIRA is for everyone, Marketing, legal, customer service, product, finance, facilities, and other teams can use it to track their tasks too. Decision three, decide who's responsible for the application. Who will make initial and ongoing configuration changes? Who will maintain the application? Who will vet and install third party apps. For server and data center, who will perform upgrades? And who will ensure application, server, database, and network stability? Who would you contact if Jira was down? How would you notify users of an upcoming change? Jira should have application support and on-call support, just like any other critical application at your organization.

Contents