Planview Viz

Planview Viz is helping [...] shift from a project to product mentality by shifting from projects into product value streams, as well as embedment of the flow methodology across the Enterprise. We want a standardised and consistent way to measuring teams around velocity and performance, and Planview Viz is the chosen strategic tool for gathering flow metrics and insights which will help teams move faster through identification of bottlenecks and areas of improvement.

It is ideal for value stream mapping in:-
- Software development ie agile and devops, and CI/CD pipelines
- Portfolio management
- Process improvement and workflow automation
- scaling agile
- creating alignment with business objectives and IT goals
It is less appropriate for:-
- Technical analysis and product design

The company had challenges in delivering new features quickly - or at all. Product Managers could not gain visibility to what work was in progress and what potential bottlenecks were causing delays or fallout. Tasktop Viz allowed us to address the problem of making work visible and identifying the work states that were causing the bottlenecks in the flow.

Viz is very well suited to organizations that have a level of commitment to a product mindset. It will be less effective in situations where big silos exist between business and technology.

I have been working with Viz since the beginning. I love how the breakout of work can give you indications on what is happening within a team. The ability to dive into the work and help the teams come up with improvements and then be able to measure them is essential to the company deliverying value to our customers. I am ready for all the improvements that are coming!

The ability to view Portfolios via Insights is very helpful for the leaders looking to measure improvements. Like the breakout of Flow Item Types as well, matches up to the strategic goals.

Work flow tool to build on an enhance the data gleaned from Rally.
As a Scrum Master, I seek to maximize the flow per iteration and PI, minimize carryover, maximize throughput and minimize team burnout.

I believe it might be better for teams, trains and organizations that have a lot of data (i.e. established rather than new). Also may be better the higher up you go in an organization, as long as their practices (i.e. SAFe) are reasonably consistent.