Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Planview Portfolios
Score 8.5 out of 10
N/A
Planview Portfolios is an end-to-end project portfolio management and enterprise architecture management tool. It includes two components: Portfolio and Resource Management and Capability and Technology Management. The platform is available as a cloud-based or on-premise service.
N/A
Pricing
Azure DevOps
Planview Portfolios
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
I like Epic when I was a scheduler because of it's user-friendliness and eye-catching layout. Planview Portfolios is better suited for the work function that I currently am in.
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.
Planview Portfolios is well suited to provide a single, central, view of the truth. There is clear expansion capabilities to integrate it as a true Enterprise toolset with existing organisation wide (not just delivery) - you can pick and choose what you need to implement and that list gets longer. The ability to quickly gain an understanding of resources within the overall portfolio and some really clever tools regarding capacity and demand modelling. I think the only challenge we have encountered is modelling our Business as Usual activity to a level of detail - this is due to other tools being very embedded not just in the organisation but across a lot of industries.
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.
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.
We have been a Planview customer since 1999 and have seen it grow and mature as a tool. We have looked at other tools and have found that PV continues to meet our needs and is easy for our resources to use. They work to stay up on the project management industry and the direction it is going, keep on on current technology so that we can work more effectively, provide excellent customer support and have great pricing for what they offer. We can purchase only the modules we need versus buying a tool where we would only use a portion of the functionality.
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.).
Perfect tool for planning resource time management. Giving flexibility with ease in uptodate . Team collabration . Team aligment. Top management aligment. Close the project with feed back . Team aligment. Expert contribution in task . Task management easy for project manager . Nice tool to have for project manager. Cost contol & project management is very easy with Planview
We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
There are occasions when the system is a bit sluggish. However, it may not always be on the Planview side. We are investing in better tools to monitor our network performance, which will help us diagnose issues more effectively in the future.
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.
Going through proper channels of support is fine for minor to moderate issues. However, lately the critical issues that arise have been frequent and the standard support cases do not always seem to relay just how critical these issues are and we have to utilize our customer rep to help escalate. Fortunate to have that escalation method.
Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
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.
We are currently using Planview AgilePlace. Also we use Tasktop Hub for integrating with other applications within the organization. We would like to use ProjectPlace which is integrated with Planview Portfolios in the future.
We are constantly growing and expanding. It is challenging to accommodate different user needs, but the system does provide means of doing that as we desire.
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.
The positive impact is the ability to manage our projects enterprise wide.
Managing and reporting on projects and programs via portfolios makes it easy to identify troubled projects/programs that need immediate attention.
The negative is that pushing too much change too quickly is hard for us. We need to get our users focused on the basics of PM before we can adopt everything else. We need to introduce change to different companies based on their maturity level. Too much change too quickly is not always beneficial. We need to focus on core competencies.
