Overall Satisfaction with Wrike
We used Wrike in conjunction with JIRA and Pivotal Tracker as a project management tool for our product launches. Wrike was used primarily by the client engineering team and as a reference to others inside the larger engineering/marketing team. Wrike has a great directory architecture and the Gantt charts work well for deadlines/progress across multiple campaigns.
- Great Gantt chart. You can look at the progress of multiple projects and sub-projects with ease.
- Fantastic directory hierarchy and structure. It's easy to navigate in and out of multiple projects or work on them simultaneously.
- Ease of use. Basic features are easy to use and intuitive.
- Bug tracking is more intuitive and simpler in JIRA/Pivotal.
- Random slowdown of web application (not downloadable app) several times a day.
- Activity log can be cluttered if you have a lot of campaigns/projects being run.
- We were using JIRA and Pivotal Tracker for everything, including the client engineering team. That didn't seem to help out as much, since we were mixing client work with backend engineering tasks. Once we made the separation, the efficiency of our product output increased, but I'm not sure by how much.
I have used Jira, Pivotal Tracker, and Kanbanpad. We used Jira and Pivotal Tracker in conjunction with Wrike. In essence, Wrike provided a great client/project management tool, while Jira and Pivotal helped us track bugs and keep on track with our SaSS application, respectively.
Wrike is great for: marketing campaigns, multiple projects, a mixed team (engineers and non-engineers), and projects being run simultaneously (Gantt chart is fantastic for this). It is not so great for: tracking velocity across a single, a large project (Pivotal is much better for this), bug tracking - option is available, but specific tasks get lost within larger projects. JIRA and Pivotal do a better job of tracking these, in my opinion.