SAP Build vs. Teams Manager for Microsoft Teams

The SAP Build Process product is best suited for managing pipelines and scrum boards without limitations. Implementation of the software is also simple, and unlimited users can connect the software with third-party systems to push codes. The software integrates well with other products, making it easy to build and deploy pipelines. The only issue with the SAP Build Process is the cost of implementation, which is far higher than that of other similar products.

Incentivized

It's well suited if you or your organization performs tasks incorporating other Microsoft programs such as OneNote or Planner. Teams Manager allows for easy management of that software usage; if you do not use any of those, I'm not sure if there is much advantage in using it to manage workflow.

Incentivized

• Its drag and drop editor is even simpler than the very popular WordPress
• No code feature to build any type of website
• Not a lot of technical expertise is required to use this tool
• The client loves it as they can themselves use it for quick tweaks

Incentivized

• Handles different teams and teams members
• Giving them permissions as per their job profile and necessity
• Seeing the projects' progress through one platform

Incentivized

• The only one I can think of that has made me not continuously use SAP Build is the cost of this tool. I see it a bit higher compared to other tools that provide the same functionality for cheaper or free plans.

Incentivized

• user interface can be enhanced to seperate the color coding for different channels
• It would be great to receive notifications in Outlook for Shifts and be able to approve/deny requests and schedule changes there while it's synced with the Outlook calendar.

Incentivized

Although coding would be helpful for improved automation and debugging, it is not a problem for any user to create a workflow and automate things as they wish. We spend way less time on training and developing workflows ourselves. There are also features such as a screen recorder. We have guides internally to teach how to automate better.

Incentivized

It is a well-designed and polished application on Teams. Most of its issues stem from Teams UI and UX, which could be improved further. However, if you can fit the team manager to your needs, it can become a very powerful tool to manage data flow.

Incentivized

There are, for example, great blog writings about automation cases and examples. The studio version is updated often. There are also useful OpenSAP online courses.

Incentivized

Compared to Mendix, we decided not to go for low code application building and in the other parts of Build, Build is stronger and better integrated with SAP. On the hand of Coding, using Build Code, gives us Joule, which understands SAP better and also have a tighter and more secure coupling with SAP services.

Incentivized

We still use it for our one-off situations, but mostly stick to Teams as it is much more user-friendly and allows better sharing capabilities through virtual meetings. Skype is not as easily customized, so it's a no-brainer to use Microsoft Teams and Team Manager for all of our instant messaging and virtual meeting needs.

Incentivized

• It has reduced the time to develop an app since it has an intuitive interface and allows peer collaboration.
• Produces quality apps through the integration of different plugins, hence improving quality.
• Has made it easy to developer to design apps in their own design.

Incentivized

• Positive in regards to easy access to quick answers through instant messaging
• Positive in that the Managers have a secure place to go to retrieve sensitive information.
• Negative in that we do not fully utilize the tool.

Incentivized