Share your experience using Planview Viz

The solution was useful in monitoring and observing the status of different environments.

We have a dedicated team to monitor the solution and keep everyone updated about the status of our environments, tools, and applications. The tool enabled everyone to see the status of each environment. Based on the availability, they could decide whether to use the environment at a particular time or set up some test sessions for a day and block the environment for themselves or the team for testing or maintenance. The board meetings took much less time to figure out where we would be at a point when we needed to do some activities. Everyone was aware of the status. We could be better prepared for the meeting.

It takes a lot of time to maintain the product. There were a lot of changes in our environments during the day. Using the tool might have been more convenient and productive if we did not have hundreds of different environments. The tool must provide better bulk editing features. It must provide more flexibility to make a wide range of changes to many things at once.

I used the solution for a few months.

The product was pretty stable. I rate the stability a seven or eight out of ten. The solution is not the perfect tool for a complex environment.

The tool’s scalability was good. We have around 250 to 300 users in our organization. The technical team had three members.

The setup was straightforward.

The solution increases the productivity and awareness of the team members. It also saves the management’s time.

The tool is good if we do not have many applications or environments to monitor and handle. It can be really useful when we have to make a roadmap with the management team. Sometimes, it can be too much to maintain and handle if we have too many environments. We will always keep forgetting something. To keep everyone using the product and updating it was challenging. Half of our team used it and performed all the necessary actions. Overall, I rate the product an eight out of ten.

We have a group of several teams, each working within agile teams. These teams are organized into various solution levels, and we also have portfolio-level views that we manage. The product has facilitated alignment between our business strategy and all teams by enabling strategic planning and backlog creation at a high level. We've implemented lean portfolio management, which involves lean budgeting and brainstorming on various epics. These epics are then assigned to the respective value streams. 

Jira is one of the most widely used tools in the market, and it has a vast amount of data already stored in it. Jira Align is crucial in orchestrating this data and providing valuable views and insights. However, it's essential for tools like Jira Align to offer configurable features. While complete customization might not always be feasible for enterprise-level tools, configurable features allow organizations to drive transformation accordingly. 

The feature I've found most valuable for improving my team's productivity is the Gantt chart view. It helps organize our backlog and track our progress toward achieving our goals. Additionally, the ability to connect dependencies within the tool has been very beneficial for us.

Jira Align offers a one-stop solution for managing projects and platforms. However, its biggest competitor could arguably be considered an Excel sheet.

I've encountered limitations in using Jira Align for certain aspects, particularly in implementing OKRs. Jira Align's highest hierarchy is Epic, which may not always align perfectly for specific initiatives. Additionally, while Jira Align offers functionality for tracking OKRs and generating dashboards, I've found that it lacks in some areas. As a result, we've explored alternative solutions that better meet our needs in these areas. Its Kanban feature is also limited. 

I have been using the product for two years. 

The tool has been stable since we moved to the cloud. 

Jira Align is highly scalable. The number of licenses purchased primarily determines its scalability. As you buy more licenses, the scalability of the tool increases accordingly. 

The number of users using the product varies depending on the organization. For example, at one client, there are approximately 250 users, while at another organization, there are around 550 users.  I haven't had the opportunity to work with organizations with thousands of users.

The tool's setup depends on the user's familiarity with the tool. It may seem intuitive for individuals with extensive experience using Jira, like myself, after sixteen years of usage. However, Jira can appear daunting for newcomers, akin to navigating an ocean. Deploying Jira effectively requires expertise and support, ideally from external consultants who can guide the implementation process. 

While external consultants can provide expertise, having knowledgeable individuals within the company who can guide its use is also beneficial. Companies often rely on employees with experience to make changes and manage Jira Align. Many companies have complex workflows that may not be optimized, leading to challenges in effectively utilizing Jira Align's capabilities. I name this scenario growth pain. 

Our customers buy licenses. We are not involved in its purchase. 

The reporting analytics feature in Jira Align provides valuable insights into our job processes. However, it's important to note that while analytics can offer perspectives based on the data we input into Jira Align, it's just one aspect of how organizations evaluate success.

Organizations also require insights into revenue realization, overall throughput, customer satisfaction (NPS), and other metrics that may not be directly captured in Jira Align. Therefore, while Jira Align's analytics tools work well within their scope, a broader perspective necessitates integration with business intelligence tools to gather insights comprehensively across the organization.

I rate the overall product a seven out of ten. I would recommend Jira Align to others, and I have some advice for those who want to start using it. My advice is directed more towards Atlassian. They should focus on being more empathetic and creating awareness about Jira Align. It would benefit them to allow people to use Jira Align for longer to experience its full potential. Understanding the diverse perspectives of different user groups, such as business, product, engineering, and infrastructure teams, is crucial. Atlassian should consider a wider range of personas and conduct deeper inquiries to address the various needs effectively. This approach would help establish Jira Align as a trusted partner for users. If I were to rate Jira Align as a trusted partner on a scale of one to five, I would give it above three.