Using Jira for Project Management & Agile Collaboration on scale
Using Jira for project management and agile collaboration is widespread and popular, especially for teams. With the following configurations and enhancements a standard Jira installation can be transformed into a scaled agile project management and collaboration platform.
Jira software is designed for Scrum, but with its Kanban board functionalities, it has been used as a task management solution for project teams and other working parties.
The main reason for Jira’s success story in the past was that it was very inexpensive for small teams, and this combined well with the many offered benefits:
- Everyone is using it.
Atlassian, the vendor of Jira, has more than 200.000 customers with 25 or more users. Why using another platform for project management, when you can use a de-facto-standard solution like Jira?
- Jira is optimised for Scrum and Kanban.
With these methods it is easy to keep on top of managing the progress of a team.
- Value for money.
Why should we spend more money on other solutions?
These are strong arguments for utilising Jira.
But there are two aspects that we must not ignore. Our world is not purely agile and what works for a small team, doesn’t necessarily work on scale.
- Communicating quickly becomes chaotic and nervous on a large scale.
Kanban, Backlog and Sprints are methods to stabilise the organisational context of a team. Well, vanilla Jira should be additionally configured for a non-Scrum-Team-Backlog planning. However, not everything can be fixed with configuration: It is not possible to work with many – let’s say 30 or more – people on the same Kanban board. Kanban just doesn’t work on scale. Alignment between teams or projects need to be ensured otherwise.
Especially in remote, cross-time-zone, cross-location or program initiatives there is a specific need to ensure frequent alignment between the teams in terms of planning, progress and review of the results in order to manage interdependencies on a regular basis.
- Jira is missing a timeline view and tasks are not part of a plan
Sequential process organisation through workflow control is increasingly unsuitable for agile collaboration. But without a timeline every card in Jira is a standalone topic, not meant to be part of a task sequence flow. Complex projects or programs cannot be managed with deadlines across different teams when no one sees a timeline or roadmap. Kanban boards are great for in-team co-ordination – and they are terrible for planning projects on scale. On scale you need the supporting structure of a plan.
For project planning a plug-in like BigPicture for Jira needs to be installed and configured.
Now, that you have fixed Jira for alignment and planning on scale, it’s worth to think about configuring and enhancing Jira to a fully-fledged collaboration platform.
- In a big Jira installation it is impossible to find attachments in Jira
Finding working documents and files in a big Jira installation can be a nightmare, because the build-in JQL-search doesn‘t include attachments. In addition to that, if you need some structure for your documents in progress – what is the case in projects where we normally produce documentation – vanilla Jira has nothing built-in but refers to Confluence-Wiki as a separate software solution.
- Every ordinary chat system always misses the point
Jira is great in organising communication around cards. But why is it sending notifications to Email-addresses? This seems like harnessing a horse to a car. What is really needed on a scaled Jira platform is to link people-chats to Jira cards where asynchronous communication is needed. If you now believe this is what you can do with a channel in Slack or MS Teams as well, then I would wonder if you could work with countless channels like you can with countless Jira cards.
- Individual task management is still a waste of paper
People bring ring binder, paper sheets or old school notebooks to meetings to take away their to-do‘s or take notes for their own better understanding. That‘s how people keep focus and optimise their own work. Unfortunately, taking notes on paper counteracts the agile principle of transparency and valuable information on paper can get lost for the solution thread of a Jira card. An individual notebook need to be digitized and integrated in Jira.