Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…
N/A
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
Progress Chef
Wrike
Editions & Modules
No answers on this topic
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
Progress Chef
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.
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
I think that Wrike is customizable enough to fit most needs, so I would generally recommend it as a starting point to anyone that is looking for a project management tool. Some people on my team don't like it, but I think that is moreso due to lack of exposure than any flaws in the tool itself. I predominately taught myself many of the features, and I found it to be straightforward. There is lots of great documentation out there, plus the community forums are incredible helpful as well. Wrike might not be THE perfect tool for every single need, but I think that there would be very few situations where it would ultimately be incompatible with a team's workflow needs.
Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
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.
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
It's easy as pie to use. I don't have any issues and only the oldest, most un-tech savvy of coworkers on my team seems to have issues with it. It's quick to pick up, intuitive, and effective. I have no criticism for it.
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.
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
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
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
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
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
We use both monday.com and Wrike. While Monday does have a better user interface, Wrike allows us to have more visibility into tasks where multiple people are collaborating. And also to receive project brief-ins and requests for new projects. We use both differently and I would say for us Wrike is more the collaboration tool than the day to day individual task management tool - and it works great.
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
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.
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.
