Anaplan vs. Azure DevOps

I've implemented a number of projects for Anaplan for Sales Performance Management use cases. It is obviously built for financial planning, but it allows for a lot of flexibility for territory and quota, ICM, sales forecasting, and other important use cases. Territory and Quota is very powerful in the tool as it organize complex assignment structures into hierarchies for easier analysis and reporting.

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.

Incentivized

• Anaplan removes the time consuming process of integrating the results of individual spreadsheets.
• Anaplan facilitates the standardization of assumptions across all sub-processes
• Anaplan provides full transparency of the calculations and source inputs
• Anaplan allows us to automate certain planning processes that would have been impossible when relying on the computational capabilities of an individual computer.

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

Incentivized

• Some end users don't spend the required amount of time to familiar themselves with Anaplan.
• Auditability, while good in theory, can be lacking and clunky when needed.
• Model building can become convoluted over time, leading to confusion over the specific use of line items.

• 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.
• It could improve the search slightly better.

Anaplan is a very strong multi-dimensional modeling tool that provides a calculation engine to empower a complex planning process. It is fairly easy to learn for those with experience in similar tools, or excel. It forces structure and auditability that spread sheets do not have, along with extensive security capabilities

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.

Incentivized

As a user it is a very simple tool, but at the same time with a very mature and powerful calculation engine. It is very easy to switch from excel or traditional tools with added capabilities of multi dimensionality and real time calculation engine to see quick insights needed to create plans and scenarios

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.).

Incentivized

There are very few outages. Maintenance is scheduled on two or three Saturdays per month, so as not to affect businesses. When there is an outage, users are kept informed of progress to restore the platform and typically this takes no more than an hour. Anaplan customer support is very responsive if we ever have questions about platform issues

Everything is calculated in memory in the cloud. It's nearly instantaneous updates when you make changes. The only time things get a little slow is when you have a massive model with very intricate calculations...but "slow" for Anaplan is not what I would call "slow" for something like Hyperion. We used to have Hyperion calcs that ran for 60 mins before you could use data. The equivalent would be 60 seconds in Anaplan.

Incentivized

Support quality has dropped since Thoma Bravo has taken over. I think some serious re-focus needs to happen here -- part of the beauty of being in the Anaplan community was how involved you felt in it before. Before I didn't dread sending a support ticket, now I am starting to.

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.

Incentivized

In my opinion, in-person training is always the best if you have the option to do so. This allows real-time interactions with the instructions, whereas the online training I took required me to write-down questions, email them, and wait for responses. This slows down the process, as you can imagine. That said, in-person training is an extra cost and it likely isn't needed for everyone. I would suggest selecting a small number of people to take in-person training and then having them act as mentors to the rest of your team. That way, as the rest of the team takes the online training, they have a resource to help them in real time.

Anaplan training materials are clear, simple, easy to understand and to follow. Visuals are excellent. The vendor is good at updating training materials in a timely manner and encouraging users and administrators to keep coming back to Academy site for refresher courses or new feature courses. I really like their interactive diagrams

One key insight from implementing Anaplan is that success comes from focusing on designing the process, not just building the model. Anaplan is extremely flexible—there are very few planning scenarios it cannot support—but that flexibility means the project needs strong governance, clear ownership of requirements, and a well-defined data model. When those foundations are in place, implementations are fast, iterations are easy, and users can quickly see value.
In our projects, both Financial Planning and Integrated Business Planning models were adopted smoothly because we involved business users early, kept the model design intuitive, and leveraged Anaplan’s Excel-like syntax and user-friendly dashboards. The result was more efficient day-to-day work, reduced manual tasks, and increased collaboration across teams. In short: when you combine Anaplan’s flexibility with a structured implementation approach, adoption and value realization happen quickly.

Was not part of the process.

Incentivized

Anaplan is more powerful than Pigment considering that it is an Enterprise class system and is able to manage bigger data sets. Anaplan allows for advanced scenario modeling and formula capabilities along with custom reporting functionalities. Anaplan has proven its capabilities and stability across various use cases and across bigger enterprises when compared to Pigment which is still in earlier phases of its development

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.

Incentivized

We have managed to leverage Anaplan for financial planning and forecasting across the business. It is now used by almost every department, with more than 50 users (but I know of companies that have hundreds of users) and still the platform is quick and reliable. It is easy to make changes to divisions and departments or add users and apply different user settings - the core part of the model is not affected and end users can continue their work without any disruption

• Anaplan's implementation led to a significant reduction in planning cycle errors and bugs, streamlining processes and improving overall accuracy in data inputs
• Standardizing the planning process and enabling cross-functional collaboration through Anaplan enhanced our ability to adapt swiftly to changing business needs, resulting in improved agility in decision-making
• The platform's capabilities, especially in Demand Planning and Supply Chain, positively impacted our ROI by optimizing resource allocation and solving complex business problems efficiently across multiple functions

• 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.

Incentivized