Item: Wrike
Rating: 3
Author: Verified User

Use Cases and Deployment Scope

We use it to create tasks and bugs for developers to implement. Our product managers and support teams create these tasks and put them in the back log. The product manager then gives them priorities and assigns them to the developers to work on. The developers work on them while leaving any questions they need answered in the comments section. They move the task along the pipeline as it gets worked on, reviewed, then released.

Pros and Cons

Tracks task history
Integrates with GitHub
Allows for customizations

Speed of application
Organization (finding specific tasks can be difficult)
Needs better integration with GitHub

Return on Investment

I don't know how much money we spent but it was not worth it

Key Insights

Do you think Wrike delivers good value for the price?

Are you happy with Wrike's feature set?

Did Wrike live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Wrike go as expected?

I wasn't involved with the implementation phase

Would you buy Wrike again?

Other Software Used

GitHub, Beekeeper, Slack, Microsoft Visual Studio Code

Likelihood to Recommend

As a developer we obviously work with a lot of code. Wrike would be far useful being able to reference that code in GitHub. It also was very confusing and hard to navigate. Issues feel like they're all over the place. On the other hand product and customer service seemed to really love using it.

Not for developers

Overall Satisfaction with Wrike