AWS CloudFormation vs. Planview Portfolios

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

I work as a Hospital Manager and in our hospital we need various equipment and advanced machines that can diagnose the best and give us the best results so that we can analyse the patient's best possible condition. Getting new machines and types of equipment is not an easy task we need so many planning the funds for the projects and implementation of those machines can become challenging part if we don't have a proper roadmap of resource management, funds, vendors suppliers, etc. Here Planview Portfolio smartly computes the all data counts all the variables and gives us the best roadmap to follow it is very useful to get crucial projects in organizations. If the organization doesn't have multiple projects or they work in a monotonous way then this tool might not be the best option for them.

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• Capture potential opportunities using the Requests Module and analyze and rank these opportunities via lifecycles and promote (dispatch) approved opportunities into Projects. Information captured during the request process automatically get transferred to projects.
• Robust schedule management; time reporting; resource management and financial planning and management
• Risk and Issue management controlled via robust lifecycles.
• Extensive reporting capabilities via SSRS and Power BI Dashboards and delivered to users via tiles in Project and Portfolio views.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• this is the area I can see Planview Portfolios is very much lagging behind. If you see Atlassian, they are having a robust API information and using that we can securely access the necessary information based on the role. I think a similar kind of approach need to done in Planview Portfolios as well.
• User Information and Resource information is separate. Expecting that, during the User creation, when a resource is linked, automatically all the basic fields should be populated with the values, also if a person is having an User account there is no way for that person to know that what User role that he/she is having. Also none of the reports covering that details.
• Automation - It's mentioned using the UiPath some of the Automation has been done in the User creation but don't find any necessary document for better understanding.

Incentivized

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.

I feel it is very difficult to use, and very limiting and of over complicated in it's basic project management basic functions. In my opinion it is over engineered to the point of un-useful

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.

Consultants are knowledgeable and friendly; it is easy to build relationships with the support people you work with and they learn how best to help you. The vendor is continuously looking for honest feedback about their tool and they use that information to design their product roadmaps

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

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

Odoo, like this platform, has allowed us to efficiently organize our projects so that they can be prioritized by importance, to know which is the most urgent, in addition, it has also allowed us to assign work in an organized way among our collaborators, and their reports have allowed us to improve.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized

• It has improved Resource Management. We now consistently represent resource available-to-promise against operational commitments, other projects, q-end commitments, vacations, etc.
• It has improved our quality of forecasting. We now model project changes and future requests against available time and resources ("what-if" scenarios).
• It has improved our strategic focus. We now manage our projects from a program/portfolio point of view to ensure we are resourcing company strategic initiatives.

Incentivized