Planview Viz vs. SAP LeanIX Enterprise Architecture

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

Incentivized

Not a 10, because now SAP is owner, there remains uncertainty on the development and pricing strategy. we struggle a bit with defining thr complex architecture of our non-sap ERP platform, but we learn as we go.

Very interesting also to start up interfaces, seems to work very well and helpfull in maintaining the proper insights

Incentivized

• Visualize via charts and graphs
• Ignore story points
• Allow a great detail of customization

Incentivized

• User friendly
• Configurable
• Relations between fact sheets
• Lifecycle management
• Self build reports

Incentivized

• Better UX and UI
• Better reporting capabilities which are self-service and automated
• Improved administrative capabilities as a Planview Viz user

Incentivized

• More depth in initiatives.
• Pre- fill with complete architecture of major solutions (like M365, infor m3 or other non SAP solutions)

Incentivized

Much more advanced and customizable than iterations of the above tools I've used. But more focused on Flow metrics than others. And more complex, IMO.

Incentivized

We did not do a comparisson

Incentivized

• Expect it to increase speed
• Expect it to increase productivity
• Expect it to improve predictability
• Expect it to improve visibility
• Expect it to improve ROI

Incentivized

• We use it for portfolio management and through its use, are enabled for better prioritization and selection of projects
• We reduced our application portfolio that were overlapping in features
• We identified weak process areas and are now able to challenge business projects in relation to process maturity and user happiness

Incentivized