Adobe Campaign vs. Rally Software

Multi-Channel Campaign Management: I have found Adobe Campaign to be excellent for managing campaigns across multiple channels, including email, mobile, social media, and web. Its centralized platform allows me to plan, execute, and track campaigns effectively, making it ideal for organizations with diverse marketing channels. For example, when I was running a campaign to promote a new product launch across email, SMS, and social media channels, Adobe Campaign provided me with the tools to orchestrate and track the campaign seamlessly. I could ensure consistent messaging and a cohesive customer experience across different channels.

Rally Software is well suited for large Agile or scrum teams who do sprints and it helps managing sprints and backlogs. It is well suited for organizations who want visibility into work being done and progress. Suitable for tracking is user stories, defects and release planning. Works well with CI CD too. It would not be suitable for small teams or startups. For teams that don't use agile. Teams who want lightweight tools like Jira. Companies with a limited budget.

Incentivized

• It allows me to capture leads through various sources, such as website forms or landing pages.
• It offers a centralized repository where I can securely store and manage customer data, encompassing contact information, preferences, transaction records, and additional relevant data.
• It provides robust analytics and reporting capabilities.

• There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
• Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
• Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
• Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
• Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
• It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
• CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
• The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
• CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
• Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.

• Adobe Campaign does not have a high enough sales intelligence to let us know which landing page format would be the most optimal for the proper development of our mass marketing operations, which in the long run would also help with customer collection.
• Does not directly track the number of people who enter our website, beyond sending them automated messages depending on whether they entered a certain section of the site. This problem is important, because it does not allow us to get complete tracking results in that area.
• The platform does not do social media marketing extensively enough to let us create dynamic evaluations on the results of interactions that are obtained within social networks, which creates a huge margin of error in our analytical results messages, and so we have stopped applying social marketing.

Incentivized

• User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
• The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.

Incentivized

Once you go for Neolane you are a bit stuck with it, so we will most likely stay with Neolane. Cost of investment and training are the main factors at work here. We havesimply have invested too much in the product to stop using it after 2 years. That said, my score of 8 does not imply that the product is worthy of getting an 8 but reflects our willingness to renew. Given that upgrading to a new version will cost again a substantial sum, we most likely will keep using the current version we are on which is 6X.

• To keep connecting my people, platform, and process for faster, smarter, better results.
• Making the right contribution to the community. Use Agile and Lean processes to manage the work of your team.
• Once you have tasted the positive result with Rally Software, you don't want to give up and come back to the old school of development pain any more.

Incentivized

Thanks to this tool we are taking more internal control of the creation and deployment of campaigns with less dependency on an ESP. We can pre-program marketing publications, being able to concentrate on the target audience. It helps me manage email campaigns with real-time tracking.

Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available

Aside from frequent error prompts, the program is quite dependable

Don’t recall ever being unavailable.

The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.

Although there is a lot of material available on the internet to answer questions, I still feel a lack of commitment and delay in the responses of the support, but as a whole, it leaves nothing to be desired. I believe that, in the great majority, companies sin in the desired support, but we cannot generalize. But this one, in particular, has a wide range of specialists and well-qualified management, but I believe that it is not so bad.

I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.

Incentivized

It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.

They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.

I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial

Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page

Incentivized

As we tried to centralise the marketing automation platform within the enterprise, Adobe Campaign can plug into several instances of Salesforce.com for lead management queues. All other marketing automation platforms can only plug into one instance of Salesforce.com. Adobe Campaign was also able to handle the complexity and challenges of our enterprise data which are a result of years of legacy, mergers and acquisitions and data aggregation.

Incentivized

Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.

Incentivized

Not everything was great at all times. It was handled accordingly, pricing was reasonable for what was purchased. It was the best value on the market at the time of purchase.

Incentivized

• Talking about profits can be subjective if you don't take into account the periodic variations between net and gross profit margins, but fortunately with Adobe Campaign, it is easy to notice these differences quickly.
• Results have always seemed relative to us, as they vary greatly depending on how much is invested.

Incentivized

• it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
• with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
• too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise
• Kanban board support is lacking

Incentivized