OpenText Vibe (formerly Micro Focus Vibe) is a web-based team collaboration platform developed by Novell, and was initially released by Novell in June 2008 under the name of Novell Teaming. Novell's acquisition by Micro Focus was completed in April 2015.
N/A
Teamwork.com
Score 7.8 out of 10
N/A
Teamwork.com is a project management platform built specifically for client work. The platform helps users deliver work on time and on budget, eliminate client chaos, and understand profitability. Teamwork.com’s customers track and manage their projects with a suite of integrated solutions such as helpdesk, collaboration, knowledge sharing and customer relationship management add-ons, enabling Teamwork.com to be the ‘one-stop shop’ solution for business owners. Headquartered in Cork,…
I think Micro Focus Vibe is very well suited for organizations that work in a team collaboration front and have to share documents. I think this really shines in organizations that have a standard set of information that gets lost in the sauce because of the sheer amount of people in an organization. In this case, the Wiki is very helpful in this setting. I wouldn't quite recommend this site for video production houses unless you are patient enough to correlate your needs to the many many features available through Vibe...because it all boils down to patience.
Teamwork is awesome for teams who need a flexible tool that supports all types of projects. Since it supports kanban it makes visualizing the work to be done and the work in progress very easy. The Gantt chart support is decent and helps to understand how a team is doing when it comes to getting work done in a given time frame. Teamwork isn't a great option for companies that have a bunch of projects going simultaneously due to the way Teamwork structures their billing based on a number of active projects.
Novell Vibe connects GroupWise mail with Vibe natively which means you can access Vibe from within the mail product.
Once forms and workflows are set up, the access structure on who sees what or not is very effective.
You can use Novell Vibe as your main intranet with everything from wiki's, blogging and more fully automated and still in synch with your internal organisational structure.
After playing with it for a while i found that through jsp it is highly configurable.
The most pressing improvement is in printing. In speaking with Novell techs Vibe was designed as a web tool, no paper necessary. However in the real world our folks love their paper printouts. Vibe utilizes views for various functions. A print view that's easily configured would be an awesome upgrade.
Customized in JSP. Vibe is completely customized using JSP. I don't know it. I'm not a programmer. I can work things out, but programming isn't my forte.
Visualization needs to be improved, charts graphs are limited
Value stream mapping should be available to determine and prioritize the work.
Documentation should be available stepwise with export and printable facility.
It should be configurable like ERP with cross functionalities of different users, where users login, assign and approve the work, job or project details, where it should be collectively effected on a project.
Add many examples, little more AI, Machine learning required for suggestion and recommendation. It would be a plus point
It meets our current business needs and provides the scalability we need for future growth. It can be installed on Windows or Linux (Our alpha install was on Linux. Our beta was on Windows. We went with Windows). There are additional features, and application integrations, that we haven't taken advantage as of yet due to the lack of current business needs.
We are already at an annual contract, and have been for the past 5 years; so far the system has delivered, and our personal is already trained in it. A major overhaul of our entire infrastructure (as in moving everything to a single, unified platform) might change the current continuity of Teamwork Projects on our organization, but that's not feasible in the near future.
At this moment it still looks you need to do a lot to be able to use it and to be honest that time should be used for work not for configuring a communication tool for the business. Yes I understand that it takes time to learn something to use in the organisation , but with this tool I see the help desk having to answer a lot of questions on how to use it or once someone has done something how to undo it.
I give it a 9 out of 10, because there is a bit of a learning curve when you first start using Teamwork Projects because there is a lot to learn & recognize where to find it. They do offer a good range of tools that can be applied to every project - So say you're working on an internal project and don't need Milestones or Billing, you can shut those modules off. This can help simplify the interface for beginners. Once you've had a few days in Teamwork Projects, I think it's a 10/10 usability. It's very easy to accomplish your tasks and keep track of what you're managing.
We've been able to meet with the customer success team on multiple occasions to discuss the roadmap and learn about the company culture. Being based in Ireland, we occasionally have to wait until they wake up to get support requests handled in the states and larger conversations about big enhancement requests were politely collected but not followed up on
The main alternatives were Sharepoint or creating a custom Drupal install. Sharepoint was too expensive and didn't fit into our Novell environment. The Drupal solution we found was beyond our technical ability.
I spoke about this quite a bit before, but as far as usability goes, Microsoft Projects is totally useless for me, so I avoid it at all costs. Basecamp was just a task management app and had very small feature set beyond that. We had to rig it to do other things for us, but it failed at that. Asana was a very nice app to trial, but it lacked many of the features that we were looking for.
Teamwork was a great starter into project management software. We were WAY more organized and efficient than we ever were with Trello boards and the PM software included with our accounting system.
Clients were mostly pleased with interacting with Teamwork, and appreciated the ability to track their comments and requests in one place.
Ultimately, we stopped using Teamwork after about 6 months because we need something more focused on web development projects specifically
