Plutora, the leader in enterprise release management software, today announced the availability of Plutora Enterprise Release Manager version 2.0, a cloud based on demand application that provides organizations with transparency and control of their software releases. The latest version of Plutora Enterprise Release Manager implements new features, largely inspired by customer feedback.
With software increasingly ubiquitous throughout all industries, on-time software release and delivery is critical for businesses to realize the efficiencies gained with software adoption. Plutora Enterprise Release Manager 2.0 provides organizations with the collaboration and communication tool that integrates all parties involved in software releases across multiple applications. The updates will allow customers to easily see the timing, composition, status, and stakeholders for all releases across the enterprise.
“We’ve learned from our customers that fragmented processes and tools heightened by geographically dispersed teams have created a wall of confusion between business stakeholders and IT teams,” said Dalibor Siroky, co-founder and Director at Plutora. “With Enterprise Release Manager version 2.0, we are incorporating their feedback to provide increased productivity and collaboration, mitigate software release failure, and accelerate time-to-value for software projects by eliminating this wall of confusion and making it easy for teams to work together.”
Benefits specific to Plutora Enterprise Release Manager version 2.0 include:
· System Impact Matrix: System impact assessment matrices that show a heat map of the systems impacted by a release, the nature of that impact (direct code impact or downstream regression impact) and the size of that impact based on the number of changes.
· Release System Dependencies: When a project or release is running late, customers can quickly identify and manage the downstream impacts and take corrective action to keep the enterprise release on track.
· Stage Gate Approvals: Customers can now track stage gate, enabling them to easily define entry criteria, exit criteria and approvers at key stages of the release. Entry and exit criteria can be assigned to internal stakeholders or external suppliers for completion.
· Visual Environment Allocation: All teams operate with a consistent up to date view of the environment demand function and the test environments that have been assigned to project phases.