You bought (or are now managing) JIRA, now what:
- Install it
- Configure it
Firstly, congratulations, JIRA is a wonderfully flexible and powerful tool that can enable teams by clarifying processes and simplifying workflows. This allow teams to focus and thus achieve more.
Getting started with JIRA can be quite a scary proposition. You may have inherited a JIRA server or be setting one up, you may have had a look around at the resources available. Likely you found the docs and said "wow, that's a lot of documentation!", after all there are 4 guides, a 101, Releases, Resources, FAQs, development tips, Tomcat security best practices and more. It's common to be asking "Where do I begin?" and "How do I get up and running quickly?"
You may also be responsible for rolling said JIRA server out to end users and ensuring everyone is able to use the tools. For most end-users, they want to learn what they need to know to do their job effectively using JIRA. They might want to pick up a few time saving tips to get tasks done faster. After all, a tool that is designed to track tasks should do that very well, freeing up time that can be better spent moving the team forward.
This is where ServiceRocket can help, we offer a range of JIRA training courses. Each course is based on our experience rolling out the products over the past 10+ years. We have taken the lessons learned in implementing solutions and organised them into courses, then delivered and evolved the materials based on trainee feedback. The courses are role based, they are interactive, they cover what each key group needs to know to make the most out of the software.
End-users take the Fundamentals course, which is a 0-60 course for JIRA. For those that have never seen the tool before it's perfect - it covers everything they need to know. For those that have used JIRA before it validates their knowledge - so they know what they are doing follows best practice and the fastest way to get tasks done. It also ensures there are no knowledge gaps for users who have self-learnt JIRA, because everyones knowledge is base-lined against the course.
When your users finish this course you know:
- They are baselined - everyone has a consistent level of knowledge about JIRA.
- Their fear of changing to a new tool is gone, they have seen it, seen what it can do, and played with it in a non-production environment where they won’t break anything.
- They have been taught by an expert, who can answer any questions in a comfortable, sharing and collaborative environment.
- You did not have to spend your weekends making slides, setting up environments and sample data, handouts, and organising training room facilities for your users.
For you and your Jira administrator’s group, there is the JIRA Administrators course, covering all you need to know about setting up projects and managing them in JIRA. Understanding the architecture and how it fits together, learning about schemes, how to configure them and how to apply them effectively.
For you and your advanced JIRA Administrators group, there is the JIRA Workflows course. It covers how to take the business processes you follow everyday and get them into JIRA. For a lot of companies this is a powerful alignment exercise, many teams don’t talk about the way they do things, the processes they follow, the steps they take to achieve a task. Bringing workflows into the spotlight help create clarity and focus on the steps your team takes to achieve their goals.
What do I do after training, am I on my own to roll out JIRA? Not at all, for many customers during the 10m training breaks an excited conversations begin about business processes and how to apply what they have learnt during the courses. This acts as a catalyst to create an opportunity to have an expert lead workshop in a structured way to help define the business processes. Once these processes have been white boarded, discussed, reviewed and agreed on, each one is added to JIRA. We recommend an agile approach, by adding one process at a time, then testing and getting feedback on it.
What happens next? Often what looks like the final solution on the white-board is not the same as the process you follow when you need to get things done, so feedback is taken and refinements are made, often to simplify the workflows.