Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Wrike
Score 8.6 out of 10
Mid-Size Companies (51-1,000 employees)
Wrike is a project management and collaboration software. This solution connects tasks, discussions, and emails to the user’s project plan. Wrike is optimized for agile workflows and aims to help resolve data silos, poor visibility into work status, and missed deadlines and project failures.
$240
per year 2 users (minimum)
Pricing
Azure DevOps
Wrike
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Wrike Free
$0
per month per user
Wrike Team
$10
per month (billed annually) per user (2-15 users)
Wrike Business
$25
per month (billed annually) per user (5-200 users)
Apex
Request a quote
per month per user
Pinnacle
Request a quote
per month per user
Offerings
Pricing Offerings
Azure DevOps
Wrike
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Every premium plan begins with a 14-day trial period.
I've used monday.com in the past for project and task management for a large team. Wrike is better suited when it comes to integrating with our development tools (such as Azure Dev Ops integration) as monday.com didn't offer that functionality. I also prefer the calendar …
Wrike has a much deeper feature set than Trello, though does cost significantly more. Azure Devops is better suited to developer workflows out of the box but overall, I would be inclined to use Wrike due to the simpler UX/UI.
When balancing needs of Roadmap Planning, Program Management, Project Management, Work Management, Queue Management, Ticket Management, I think Wrike hits the perfect balance of usability and configurability with the power to scale effectively while maintaining governance, all …
Features
Azure DevOps
Wrike
Project Management
Comparison of Project Management features of Product A and Product B
Azure DevOps
-
Ratings
Wrike
8.0
917 Ratings
3% above category average
Task Management
00 Ratings
9.1908 Ratings
Resource Management
00 Ratings
7.7780 Ratings
Gantt Charts
00 Ratings
7.8637 Ratings
Scheduling
00 Ratings
8.4793 Ratings
Workflow Automation
00 Ratings
7.9785 Ratings
Team Collaboration
00 Ratings
8.6908 Ratings
Support for Agile Methodology
00 Ratings
7.7504 Ratings
Support for Waterfall Methodology
00 Ratings
7.9453 Ratings
Document Management
00 Ratings
7.6763 Ratings
Email integration
00 Ratings
7.8683 Ratings
Mobile Access
00 Ratings
7.9660 Ratings
Timesheet Tracking
00 Ratings
7.7427 Ratings
Change request and Case Management
00 Ratings
7.723 Ratings
Budget and Expense Management
00 Ratings
7.6326 Ratings
Professional Services Automation
Comparison of Professional Services Automation features of Product A and Product B
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
I believe it's well suited if you have multiple jobs/projects that you need to keep organized. We work with multiple job types from print/creative to web, copy and digital ads so it helps us stay organized. I don't think it would be suitable for a company that doesn't have a lot of jobs to manage. We average over 1,200 requests a year.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
I wish that Wrike had more drag and drop functionality that would be connected to assignee and also I wish that the finish date of a task would update to the date where you checked completed. It does not do that. Also finishing a task doesn't move the start date of the next task it "protects your time in that way", but our management team wants us to quickly see what we have down the pipeline rather than having to scroll down the list of upcoming tasks.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
It does take some time and work to really understand and use it properly, but I think the accessibility to help and documentation make that completely feasible. Once you know how to use it, I find it to be very user-friendly, and have very few complaints.
Over two years of (almost) daily usage without outages. Don't remember any errors. I give it 9 only because some Wrike plugins (for online document edit) are based on NPAPI architecture. These types of plugins are being phased out in new browsers, and NPAPI plugins are disabled by default in recent versions of Chrome so you have to do some browser adjustments when you switch browsers or move to another computer.
Wrike tasks loads fine, but I hate clicking files and wait for a bit of time since it is powerpoint or word, Wrike assumes I want to open those on Wrike. My suggestion is to link it to office 365 so we do not need Wrike based decoder for PPTX and DOCX
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
During my learning phase with Wrike, I initially struggled with setting up automation rules and request forms. However, Wrike support was always my go-to, resolving issues within seconds or minutes. Their assistance made the learning process much easier. My best experience was receiving step-by-step screenshots to follow, with the support team on standby until I was completely satisfied.
I love the Wrike training options. Wrike Discover has tons of courses, learning plans, certifications, etc. This is an area where Wrike definitely shines! I wish these resources were more in your face for new people, because it seems like a lot of coworkers didn't know all of this training was available to them.
There are a lot of bells and whistles in Wrike, and not all of it is easy or intuitive to understand once it's plopped in your lap. It's easier when there are a few choice people who understand Wrike as a platform and articulate it in such a way where it makes it easy to pass it along to others in the group
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
Jira did not at all help us get our work done as content creators. I think that was because Jira wasn't quite right for our uses. Wrike fits our needs so much better. I can't tell you enough the relief I felt when we adopted Wrike and I never had to use Jira again.
The sky is the limit for what can be done in Wrike. We started with 1 use case and within 5 months we migrated several key business practices over to Wrike because they were easier to manage. Use cases so far: process improvement, management review, corrective actions, maintenance requests, month-end financial closing, and document management. As we grow, it's easy to imagine putting even more into Wrike where it becomes a cornerstone for how we do business
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
Different teams (e.g., contracting, compliance, provider relations) can view updates in real time, comment directly on tasks, and escalate items when needed.
Wrike allows us to template the contracting process (from intake to signature) to ensure consistency across payers and reduce administrative overhead.
Leadership can see the status of negotiations at a glance, identify bottlenecks, and prioritize resources accordingly.