Jira Configuration & Implementation
So to get your team going and to ensure you apply some Jira best practices when configuring your Jira instance it is always a good thing to rather use a consultant in the beginning of your agile adoption. Why? Later will be more costly as you will have to incur extra expenses for migrations and configuration changes.
Due to the configuration capability of Jira we often see the tool exploding into all parts of the business. If you have setup your instance with an absence of best practices you will run into issues later as people do not fully understand how configurations impact other teams and how the configuration all hangs together.
People often also do not know how others use the tool within the organisation, so implementing best practices will assist with minimizing impact on others using the tool. No understanding is needed on how others in your organisation is using the tool, when making configuration changes specific to your team/division or area once best practices has been setup and applied.
We focus specifically on automation configuration and agile configuration of Jira.
Here are examples of some processes we have configured on Jira:
- Management of sales pipelines
- Recruitment automation and management
- Financial administration focused on going paperless
- Agile delivery management
- IT Service management (ITIL based)
- Agile portfolio and programme management
- Agile metrics, delivery and project budget monitoring
- Time capture
- Client Quotations
- Service Level Agreement monitoring and escalations
If you require other implementations or configuration that are not covered in the above list you are welcome to contact us in order to spec and implement your solution on Jira.
To see how we approach the management of these projects click here.