Is Asana better to use than JIRA for small teams / short life cycle projects?

English Forum Tips and Tricks
, , , ,
1

As part of research I’m conducting for my thesis, borne out of the frustration of using Project Management Tools (that are more suited for larger projects / large teams) to handle smaller projects with small teams, I’m trying to understand if there is an correlation between the suitability of particular methodologies (eg Kanban/SCRUM) & tools (eg Asana or JIRA) for smaller teams.

In your experience what is the ideal team size or project size (as in lifecycle/timeframe) for the methodology you use? Do the tools you use, help or do you feel sometimes that they get in the way (especially for smaller projects / smaller teams) and you’d rather switch to a pencil, notepad and a simple to-do list?

If you have any insight or opinions on this, I’d be most grateful for your input in this questionnaire please. It should take 2-5 minutes.

In my company, we tend to run short projects (<4 weeks) run by small teams (<4 people). And each team can have up to 5 concurrent projects. In many regards, we’ve found that SCRUM is cumbersome and we are now modifying the way we are using JIRA to make it feel less burdensome. We’ve experimented with Asana and a few other tools such as ClickUp, and from our experimentation that some of these feel more nimble / flexible than JIRA.

Thanks very much for your help.

2

Welcome to the forum @premb0 ,

I tried Jira, and ran away screaming.

I think - by now - Asana is flexible enough to use for any of the ‘methodologies’ you mention. Be it project (collection of work that can be considered done) or process (work flowing in a repeatable pattern)

Conversely, I’ve seen people use Outlook - of all tools - to manage a process more successfully than how most are using Asana.

I’m an improvement proffessional and Asana expert, and I’d be happy to offer a free initial consult if it helps you choose. Let me know if you’d like to take me up on that.

1 Like