DevOps Tools require a different approach
Share task status to improve collaboration and artefact traceability
Removing silos is exhausting. Pulling together discrete functions, working for years in their own bubble and evolving unique ways of performing tasks is hard work.
Work duplication, lack of common tools and shared data impede collaboration.
The 5 hurdles Jira Implementation Fastrack overcomes
1. Too many processes and tools for one task
A good example of this is requirements gathering or story points. Within the same organisation, and even within the same project teams, there are team members working together on the same tasks but using Word, Excel, Visio, Powerpoint, and Email.
There can be multiple templates and no file naming conventions. These problems are further compounded by the absence of version control. Poorly designed and poorly administered Sharepoint/Google Drive etc. directories kill productivity.
If your people spend more time searching for the correct template or the right version of a document than engaging the business you know something needs to be changed.
2. Each duplicate tool has its own champion and “emotional attachment”
You want people to have a sense of ownership for tasks but, on occasion, this can be counter productive. Don’t mistake ownership for a process with ownership for a tool.
✓ Process knowledge is where the value lies, not in its codification.
✓ New ways of working may require new tools, but not always.
✓ Existing tools should plug into modern tools’ architectures or be replaced
It is mindset, process and then tools – not the other way around. Don’t allow tools decisions taken years ago to compromise new ways of working.
3. Too many ways of communicating task status
The list of communication tools is long. Slack, whatsapp, email, Jira notifications, Skype, Twitter, the phone… How do you cut through the noise? Establishing a set of policies and guidelines can help:
✓ Only urgent communications should be on a slack channel where your slack id has to be called out specifically.
✓ We recommend that email is used as little as possible and that only one ticketing system be employed.
✓ Remove duplicate tools: for example, Slack and Skype for Business.
✓ Only have one ticketing system.
4. No information radiators
Older ways of working meant that everyone engaged in the design and delivery of a product focused on their piece of the project with no regard for overall team performance or value to the customer.
✓ Encourage individuals out of their silos
✓ Create awareness for people of what is happening to their left and right
✓ Whiteboards and post-its are a great start
5. Existing tools have no APIs or webhooks
Organisations may have invested heavily in certain tools Such investments may have required lengthy evaluation and implementation periods.
Today’s tools are changing constantly. Proprietary tools with upfront licence fees are no longer viable.
If your organisation is dependent on such tools it is time to engage with the vendor and establish if they have plans to ‘open up’ their product, introduce a SaaS edition and monthly subscriptions.
If not, you should consider downloadable try-and-buy SaaS tools which can be stood up and down within days. Make sure there is a third party marketplace with multiple add-ons for your unique requirements. You can read more about our tools strategy on our Atlassian Licence and XebiaLabs License pages.
How we can help
Jira Implementation Fastrack is based on the Atlassian toolset to address the challenges as outlined.
The Jira Implementation Fastrack helped FBD to view the entire SDLC (process and tools) in one sitting. This session enabled us to identify inefficient workflows, tool duplication and the opportunity to increase collaboration across the teams. I’d recommend Jira Implementation Fastrack to those who are trying to implement an Atlassian architecture that is sustainable.
Subhendu Mohapatra, Manager – Release and Environments at FBD Insurance
+ Surface your specific issues by bringing together SDLC stakeholders in a workshop.
+ Understanding who is doing what and how they are doing.
+ For each of define, plan, code, test,release deploy and support.
+ Our experts compare the as-is picture with best practice.
+ Workshop outputs drive a business case for change.
+ Exposes the cost of silo’s and move towards an Agile culture.
+ Articulate your to-be architecture.
+ POC YOUR workflows. Documents are dry where workflows implemented in new tooling helps build a coalition of the willing in your organisation.
+ Bring people with you. Individuals who have been wedded to one isolated product can now see for themselves how newer tools will make their day-to-day tasks more productive.
+ The ‘to-be’ architecture document becomes a strategic roadmap and an expression of requirement for additional tooling.
+ We don’t just hand over sample workflows we build them with your team
+ Initial delivery is a start point for your admins.
+ Supplemental classroom based training may be required.