Share your experience using Plutora

I primarily use Digital.ai Agility for Agile project management, sprint planning, backlog management, and tracking team progress and deliveries. We use Digital.ai Agility for Agile project and portfolio management, including backlog management and sprint planning. It helps us monitor team progress in sprints and the capacity and release timelines. We also use dashboards to identify blockers and track delivery status. It provides better visibility and helps the team stay aligned with the Agile processes.

We also use Digital.ai Agility to track dependencies, manage defects, and coordinate work across teams. It helps us maintain clear ownership of tasks and provides full visibility into sprint progress and upcoming releases. Overall, it keeps our daily planning and delivery process more organized.

The best features offered by Digital.ai Agility are backlog and sprint planning, dependency management, and customizable dashboards. The dashboard provides strong visibility into velocity and delivery progress, defects, and team performance. I also appreciate the portfolio planning and roadmap because they help connect team-level work with a larger business scope. The integration capabilities make it easier to connect Digital.ai Agility with other tools in the development ecosystem.

Digital.ai Agility has improved our project visibility, sprint planning, and team coordination. It has helped us organize backlogs and priorities. We can track progress, dependencies, and delivery risk in one place. It has also reduced manual status reporting and improved communication. Overall, it has made our Agile delivery process more structured and predictable.

I would like to see more advanced reporting and analytics customization. The existing dashboards are useful for tracking velocity, backlog, and delivery, but deeper real-time insights would improve decision-making. I would also like simpler integrations and more flexibility, especially across large teams and complex projects.

Another improvement I would like is more flexible reporting and dashboard customization, especially for creating organization-specific metrics. More intuitive visualizations would also help.

Digital.ai Agility can be improved mainly by making reporting and dashboard customization more flexible and intuitive. I would also like simpler integrations with third-party tools and easier configurations of automated workflows. Better dependency visualizations and real-time alerts for delivery risk would help large teams identify blockers earlier. The user interface could also be simplified to make it easier for new users. Overall, these improvements would make day-to-day planning, reporting, and cross-team coordination more efficient.

There are a few areas where improvements are needed. I would like to see further improvements in user experience and navigation, especially making commonly used features easier to access for new users. More intuitive dashboard customization, better dependency visualization, and simpler third-party integrations would also help.

I have been working more than three years in my current organization using Digital.ai Agility.

In my experience, Digital.ai Agility is stable for day-to-day Agile project management. We have used it consistently for blocking, sprint, and release tracking without major stability issues. It also supports regular releases and ongoing maintenance. The main areas I would watch for performance are at very large scale and occasional UI navigation issues, which some users have also reported.

Digital.ai Agility scalability is effective for managing multiple team portfolios. It supports scaling Agile practices from individual teams to programs and the overall portfolio. The customer support is good and responsive, although there are sometimes delays that may take some time.

I rate customer support as eight out of ten.

Before Digital.ai Agility, we used Azure DevOps for development tracking, but it was less suitable for enterprise-level Agile planning and portfolio visibility. We switched to Digital.ai Agility because it provides better support for scaled Agile processes, dependency management, and organization.

The overall experience with pricing and licensing was fairly straightforward, although it required some planning around the number of users and the edition we needed. Since we used the on-premises version, the initial setup involved infrastructure, database configuration, authentication, and user provisioning. The license is user-based, and different editions provide different layers of integrations, analytics, and AI capabilities. Overall, the cost is reasonable for the enterprise Agile platform, particularly when you consider the visibility and planning capabilities it provides.

We have seen positive return on investment mainly through time-saving and improved productivity. We estimated Digital.ai Agility saves around five to ten hours per week, sometimes fifteen, by reducing manual status reporting and blocking and coordination. It also helped reduce unnecessary meetings by approximately fifteen to twenty percent since teams have better visibility into progress and blockers. We have not reduced headcount, but the same team can spend more time on developing and higher-value activities. Overall, the biggest benefits have been better delivery visibility, improved planning, faster decision-making, and reduced administrative effort. Digital.ai also cites an independent Forrester TEI study reporting one to two percent ROI for a composite organization, although that figure is not our own measured result.

We evaluated other options before choosing Digital.ai Agility. We compared Jira, Azure DevOps, and Rally mainly on enterprise planning, dependency management, reporting, integrations, and scalability.

I can advise others to use Digital.ai Agility for organizations. It is good for enterprise-level Agile planning across multiple teams and portfolios. Before implementing it, I would suggest starting with a few key use cases, such as backlog management, sprint planning, dependency tracking, and reporting. Make sure the team gets proper onboarding because some features can take time to learn. I would also recommend evaluating all required integrations and the deployment model early, especially for on-premises environments. Overall, it is a good choice if you need scaled Agile practices across multiple teams rather than just managing individual projects. I would rate this solution as seven out of ten.

My main use case for Microsoft Azure DevOps is for a dedicated team that is building Copilot Studio agentic AI use cases. I assign tasks to my team members, such as creating Azure Boards, Azure Repositories, and Azure Pipelines, and assigning individual tasks to each team member while monitoring their progress through Microsoft Azure DevOps. My primary objective is to manage Copilot agent applications for our team members. I am also involved in website designing and development, so I coordinate with the design and development teams to maintain their tasks in Azure Boards.

Based on my experience with Microsoft Azure DevOps, I believe everything is good, but I occasionally experience some slowness. This does not occur on a daily basis, but there are times when it takes longer to load in a browser.

I maintain our daily basis tasks on Microsoft Azure DevOps using the main key features of the platform, including the end-to-end DevOps platform, monitoring of each individual's tasks on Azure Boards. It is a faster delivery method that improves collaboration and code quality while automating consistency. It supports main Agile development practices. Microsoft Azure DevOps offers multi-platform and multi-cloud support, though we primarily use Microsoft Azure due to our Microsoft partnership.

The best features Microsoft Azure DevOps offers include the ability to create Azure Boards where I can enter project planning and requirements. Microsoft Azure Repos allows me to manage source code, and Microsoft Azure Pipelines enable me to easily build and create CI/CD pipelines. I can define and write Microsoft Azure Test Plans and create Microsoft Azure Pipelines, also known as CI/CD deployment. Additionally, I can use Microsoft Azure Monitor and Application Insights to easily track resource utilization, time, and resource consumption, showing which resources have been utilized and for how many hours on a daily basis. In simple terms, Microsoft Azure DevOps helps any organization move ideas from development to production faster with greater automation, improved collaboration, quality governance, and a secure environment.

I find myself relying on Microsoft Azure Boards the most. Creating Azure Boards and user stories while managing and dividing tasks into different slots is something I use on a daily basis more than all other capabilities.

Regarding the features of Microsoft Azure DevOps, the team's performance and spending on particular tasks are mentioned in a storyboard, which is a great feature for reporting purposes. If I have 10 team members, Microsoft Azure DevOps shows a bar chart or pie chart, or I can view the report with Excel where I can trigger SQL queries and add conditions, such as how many tasks we have completed on a daily, weekly, or monthly basis, and whether each task is completed, done, to-do listed, or in progress. These features are ones I appreciate and use on a daily basis. Another feature I use is based on licensing plans, which can sometimes be costlier for small and medium organizations from my perspective. However, major enterprise-level organizations use Microsoft Azure DevOps.

Microsoft Azure DevOps saves a lot of time while monitoring tasks and assigning them to team members. I can easily monitor how many tasks take what amount of time. This would be helpful for internal organization teams and for working with customers or clients, as it easily helps manage how many resources and money we have spent on a dedicated project. It is really helpful for any organization adopting DevOps culture.

Since using Microsoft Azure DevOps, I can say that initially, we were managing tasks on Excel and sharing weekly plans with team members, maintaining hours manually. When we started using Microsoft Azure DevOps, it saved considerable time and showed every team member's productivity very transparently. Tasks have been divided on an hourly or two-hour basis, showing how long each task takes. It totally saved a lot more time. I cannot define an exact timeframe, but it definitely helped with assigning tasks compared to doing it manually on Excel. The storyboard provides a graphical representation that is very helpful when summarizing information for executive leadership teams or stakeholders.

I reduced my rating from a perfect score because of one concern. Microsoft Azure DevOps is very easy to use. If any person is new to the platform while creating user stories or repositories, it is a very efficient way for people to work. The platform does not require in-depth training. If someone provides a one to two hour description, people with some technical knowledge would understand it greatly. The platform is interesting for both fully technical and non-technical persons. People can use it easily and it is understandable. Anyone can create a user story or Microsoft Azure Board, generate reports using SQL queries while adding conditions, or monitor tasks. Any person with admin rights can see graphs showing which resources have spent how many hours on a daily, weekly, or monthly basis. Based on that information, we can measure resource performance, which would be really helpful for management or HR departments when increasing employee salaries, offering appreciation, or providing bonus activities in an organization.

Regarding governance and security within Microsoft Azure DevOps, there is strong security because Microsoft provides a secure and productive environment that follows all compliances. Everyone can trust Microsoft because it is a reputable brand in the market. People can rely on and trust any Microsoft product. I am not talking about Microsoft Azure DevOps only, but also CRM, Windows, security, and Entra ID. With any Microsoft product, there is no need to worry about security or compliance concerns. From a security and governance point of view, Microsoft Azure DevOps provides very strong capabilities.

I have been using Microsoft Azure DevOps for the last eight years to manage tasks, create user stories, and manage teams through graphical representations inside the DevOps platform. These features are what I use on Microsoft Azure DevOps.

I occasionally experience slowness with Microsoft Azure DevOps, though not very slow. The speed could be faster, which has been my main concern throughout my eight years of using the platform.

Regarding Microsoft Azure DevOps's scalability, it depends on your usage and the number of team members you have. You can scale according to your needs. From a scalability point of view, it is really helpful, and I can say it is a scalable platform.

We have communicated with the Microsoft Azure DevOps team, but we rarely need to contact the support team. When I have raised tickets, they have been resolved within 24 hours SLA, mainly. Sometimes I reside in India and the ticket assignee is in the United States, so they schedule collaboration or contact requirements according to the appropriate time zone. The support process is smooth with no issues.

I would rate customer support for Microsoft Azure DevOps at 8 or 8.5 out of 10 because we cannot connect directly with Microsoft Azure DevOps or the support team on the spot. There is a process that anyone needs to follow: drop an email to the support team and they will reply. Suppose I am in a hurry and stuck somewhere, then a phone call would be helpful. However, I do not have a direct number to call and connect to the support team immediately, which is not possible. Microsoft does not provide that kind of immediate support.

I have not used any DevOps platform before using Microsoft Azure DevOps. I have some knowledge of Jira, which also follows Agile terminologies, but I am not much more familiar with it.

I did not evaluate other options for Microsoft Azure DevOps. There are many tools in the market used for project management such as Trello and Jira, but Microsoft Azure DevOps has a standard, and we are in the Microsoft ecosystem. That is why I prefer to use Microsoft Azure DevOps because on a single platform, there is a complete cycle starting from Microsoft Azure DevOps to Microsoft Azure Artifacts, Microsoft Azure testing, creating CI/CD pipelines, and Microsoft Azure Test Plans. Everything is on a single platform. That is why Microsoft Azure DevOps is a complete solution for any organization dealing in software development or IT solutions. From my experience, it would be really helpful for anyone as a complete platform, and there is no need to go to any other solution.

Microsoft Azure DevOps is very easy to use. If any person is new to the platform while creating user stories or repositories, it is a very efficient way for people to use it without needing in-depth training. If someone provides a one to two hour overview, people with some technical knowledge would understand it greatly. The platform is interesting and suitable for both fully technical and non-technical persons. People can use it easily and it is understandable. Anyone can create a user story or Microsoft Azure Board, generate reports using SQL queries while adding conditions, or monitor tasks. Any person with admin rights can see graphs showing which resources have spent how many hours on a daily, weekly, or monthly basis, allowing us to measure resource performance. This information would be really helpful for management or HR departments when increasing employee salaries, offering appreciation, or providing bonus activities in an organization.

It is a difficult question for me because I cannot state the exact amount of time and money saved for us. However, Microsoft Azure DevOps definitely saves a lot of time and resources as well as money for any company, including mine. It is helpful while using Microsoft Azure DevOps for my company. Additionally, it is reputable if we are maintaining projects on Microsoft Azure DevOps. If a reputed company approaches us for their services or product requirements and they learn that we are maintaining Microsoft Azure DevOps, it would be very helpful to convert our customers into real revenue generation and business growth.

I am not much involved in the pricing, licensing, or costing aspects. However, one of my colleagues is involved in the licensing and pricing part, and it is very efficient. We are Microsoft Gold Partners, so we directly reach out to Microsoft resellers or partners to enhance our licenses if required.

I would definitely suggest using Microsoft Azure DevOps. Microsoft Azure DevOps is a scalable platform and a complete solution for any IT or software development company. People can rely on Microsoft Azure DevOps as a platform or tool that every company should follow. I cannot commit that every company follows Microsoft Azure DevOps, but definitely if a company has any reputation, they can use Microsoft Azure DevOps and maintain their code as well as maintain their storyboard, create sprints, easily monitor tasks, resource utilization, and reporting and analytics features. My overall rating for Microsoft Azure DevOps is 9 out of 10.