Using JIRA for Project Management

Using JIRA for project management is popular, especially among software development teams.

3) Value for money. We already have JIRA — why spend more money on another platform, if we can make use of the platform we already pay for?

These are good arguments. But, as you can guess, there are also cons to using JIRA for project management.

1) Non-R&D people in the organization don’t use it. Sure, the software team uses JIRA. But the marketing and design teams don’t — and for good reason. Once you have to teach some teams a new software platform, why teach non-software people a software platform, just for project management, when you can use a dedicated and intuitive platform for everyone instead?

However, when developing software, all of those tickets are actually linked, and dependent on other tickets too. Sure, JIRA lets you link tickets. But those links are simplistic, and they don’t capture the dependency network you know is actually there. This is why developers spend so much time discussing these dependency links, and the overall software project. That information and vision is not available in JIRA.

JIRA’s structure forces software development teams to plan their projects to conform to JIRA’s model. Using JIRA for project management actually bakes in an inefficiency into how you’ll manage your project. JIRA prioritizes task management. There’s no map, no overall structure for the project itself. JIRA breaks down the project into tasks, with its ticket model. You, as the project manager, are thinking about your project in terms of individual tasks.

That in turn pushes the team to complete tasks without thinking about how those tasks fit into the project as a whole. Creating great software requires a big picture model. It demands an integrational approach that links tasks to the overall vision of the application. Using JIRA as a project management tool leaves you lacking in the most important aspect of the project.

Proggio integrates seamlessly with JIRA, giving you the best of both worlds. Manage your software development with JIRA, while managing the project overall through Proggio. Instead of digging through tickets to figure out what’s going on, you have the projectmap showing you intuitively and visually exactly what progress has (or has not) been made — using your data from JIRA. Proggio is the big picture/integrational model that JIRA is lacking.

Proggio is the timeline and roadmap Jira is missing.

You might use Proggio over JIRA to create a roadmap. You might use it to bring real project management to the efforts contained in JIRA. With Proggio, you don’t need to root around through JIRA tickets to find the answer to “where are we holding?”

Proggio is your eye into the software development team. Software dev doesn’t have to be a black box. Proggio is the timeline and roadmap Jira is missing.

Related posts:

I invite Martine Weber Charlotte Zobeir Manasi Diwakar Gurpreet Dhariwal Amy Marley Simran Kankas Aurora Eliam, CMP to continue this ‘Never-Ending Poem’ thread with a poem about Peace.

Today we live in a very dynamic and unpredictable world. As reality shows things can change really fast. And we are talking not only about COVID-19 but about the safety of our health at all. And in…

One of the most exciting things you can do with your Bitcoins is to send them to a piece of paper. It sounds sort of mundane but think about it for a while. Before Bitcoin you, the average citizen…